4 ms·
Building software is often compared to building houses. If civil engineers can design and create a very complex bridge or dam or whatever, and it keeps working
by Swizec 15y ago
Building software is often compared to building houses. If civil engineers can design and create a very complex bridge or dam or whatever, and it keeps working for 150 years without breaking. Why can't us software engineers make software that will work without bugs for more than 10 minutes?
Problem is, the two aren't really comparable.
A while ago someone wrote an article that we are Software Gardeners not engineers[1]. And I think that comparison is much more apt.
Software is maleable, it can change, the layers of complexity build up so high it's impossible for any one person, or team of persons, to fully understand. Even the mathematical theory of software isn't fully understood yet, and yet we are piling those little lacks of understanding on every layer of the architecture ... they add up and things become monstrous.
BUT! This is a good thing. Software isn't a physical object. I want to be able to change the specs half way through a project rather than having to wait another 50 years to design a better bridge. This makes progress quicker.
As always, when progress is quick (and easy), it is also messy.
For example: it took builders thousands of years to invent The Arch and trully revolutionize the industry. It took software only a couple of decades to go from machine code to python.
Oh and never forget, the Turing Machine was "invented" in 1948. Our lives revolve around an industry the theoretic principles of which were first defined less than 70 years ago.
[1] http://chrisaitchison.com/2011/05/03/you-are-not-a-software-engineer http://chrisaitchison.com/2011/05/03/you-are-not-a-software-...
- ExpiredLink 15y agoWriting software is like writing books: http://www.artima.com/weblogs/viewpost.jsp?thread=255898 http://www.artima.com/weblogs/viewpost.jsp?thread=255898