jump to navigation

How to write perfect software October 23, 2006

Posted by Al in : interesting,programming,software , trackback

Ok – this article is 10 years old, but I’m certain that my company could benefit from reading and reviewing the ideas it contains. In particular the bit about careful planning, ironing out all the ideas and requirements, before writing any code would have saved them a lot of time and expense. The processes described in this article could not be applied to all real-world situations, because market and products change at such a fast rate these days. However, if you are not willing to follow these processes and principles then you have to budget and allow for errors, and this is very hard as errors are unpredictable, by their very nature. I trained in Systems Analysis a long time a go and I can see the benefit of breaking problems down into outline, detail, pseudo-code and then real code, but I can also feel the urgency that stirs when the creative juices get going. The discipline these guys have shown is not for everyone, however if you want fault free code you may have to enforce it.


no comments yet - be the first?