Saturday, February 8, 2014

Software Craftsmanship

I have often found myself thinking about the ideas of Software Craftsmanship, well before 460. The news outlets theses days are overrun with stories of poor software causing tremendous amounts of damage, both financial and otherwise. As someone studying computer science, I know all too well that we in the field are to blame for this current climate of dangerous programs.

There have been many many studies on proper coding practices, as well as proper project management. The strong consensus of these studies has shown that taking time to write quality (maybe not perfect) software is not only more secure and stable, but it also costs less money and time to create. It is better on all fronts, there is no downside. Of course one can not go overboard in this process, and spend weeks upon weeks writing ten lines of code, but simply writing code with reckless abandon is a known recipe for destruction.

Despite it being well known that there are practically no disadvantages to writing high quality code, people continue to hack things together in unmaintainable, unexpandable, insecure ways. I can't understand why we as humans do this. What is wrong with us? Are we so naive that we believe that we as programmers don't need to follow proper practices, because we think we are above these practices?

No comments:

Post a Comment