Partager via


SYSK 363: ‘Software is not made of bricks’ by Ragan Wald

I recently came across this gem http://weblog.raganwald.com/2007/08/bricks.html -- strongly recommended!

 

Here are the section titles to whet your appetite:

 

· Software is not made of bricks

· Assumption: it’s all about moving bricks

· Software is more complicated than bricks

· Determine the baseline competence required for a project and don’t violate it

· Software development is difficult to parallelize

· How to make the team twice as productive without parallelizing everything

· Software is transfinite

· How to measure progress on software development projects with estimated work remaining

· How to measure progress on software development projects with customer satisfaction

· Building software without treating it like a pile of bricks

I recently came across this gem http://weblog.raganwald.com/2007/08/bricks.html -- strongly recommended!

 

Here are the section titles to whet your appetite:

 

· Software is not made of bricks

· Assumption: it’s all about moving bricks

· Software is more complicated than bricks

· Determine the baseline competence required for a project and don’t violate it

· Software development is difficult to parallelize

· How to make the team twice as productive without parallelizing everything

· Software is transfinite

· How to measure progress on software development projects with estimated work remaining

· How to measure progress on software development projects with customer satisfaction

· Building software without treating it like a pile of bricks

Comments

  • Anonymous
    October 16, 2007
    PingBack from http://www.artofbam.com/wordpress/?p=9151

  • Anonymous
    November 16, 2007
    Hi! Just wanted to mention that the name of the author of weblog.raganwald.com is named Reginald Braithwaite. raganwald is simply his stage name, I guess ;-)

  • Anonymous
    September 28, 2010
    Thank you for posting this link!  Coming from the legal side of things, I find this article to be right on point.  Most unhappy campers I have represented over the years lost their way because their focus was on quantifying the work ("look how many lines of code I wrote for them") rather than on producing results.  More developers should take this to heart.