Comments on: Increasing Complexity Over Time http://theta.codesimplicity.com/archives/9 Scientology and Computer Programming Thu, 04 Dec 2008 21:39:53 +0000 http://wordpress.org/?v=2.6.2 By: Max Kanat-Alexander http://theta.codesimplicity.com/archives/9#comment-13 Max Kanat-Alexander Mon, 28 Jan 2008 23:40:11 +0000 http://theta.codesimplicity.com/archives/9#comment-13 Hahahaha. Wow, that is so interesting! Yeah, sometimes I think that us people who understand these things are constantly being put into that sort of position, where we have to use our knowledge to fix the complexities of people who didn't know! :-) I've been doing that with <a href="http://www.bugzilla.org/" rel="nofollow">Bugzilla</a> for about three years now. It finally does all come out the other end being a beauty queen who can sing and dance and do backflips, but it really does take some work that all could have been avoided in the first place if the original authors just fully understood what they were doing and stuck to their guns on having actual good requirements! -Max Hahahaha. Wow, that is so interesting! Yeah, sometimes I think that us people who understand these things are constantly being put into that sort of position, where we have to use our knowledge to fix the complexities of people who didn’t know! :-) I’ve been doing that with Bugzilla for about three years now. It finally does all come out the other end being a beauty queen who can sing and dance and do backflips, but it really does take some work that all could have been avoided in the first place if the original authors just fully understood what they were doing and stuck to their guns on having actual good requirements!

-Max

]]> By: Grahame http://theta.codesimplicity.com/archives/9#comment-12 Grahame Mon, 28 Jan 2008 14:41:48 +0000 http://theta.codesimplicity.com/archives/9#comment-12 That quote is so right. Last year I took over the development of a system that has been "evolving" over a ten year period. You look at the code and your head spins! It is so darn complex. Then you talk to the people in the company who set the requirements and you see why. They don't really know what they want. The way the application "evolved" was: they came up with a "requirement" but it wasn't quite right or not fully defined, so once it was built it had to have changes made. The earlier programmers were not very skilled themselves (the tools and language they used were "poorly known" to them) so they didn't code in a way that was easy to refactor or modify. The result is that today we have a monster. And now I have the joy of gradually upgrading this monstrosity bit-by-bit because they can't afford a complete re-write. Oh well, I guess it keeps me on my toe trying to figure out how to turn the Bride of Frankenstein into a beauty queen :) That quote is so right. Last year I took over the development of a system that has been “evolving” over a ten year period. You look at the code and your head spins! It is so darn complex. Then you talk to the people in the company who set the requirements and you see why. They don’t really know what they want.

The way the application “evolved” was: they came up with a “requirement” but it wasn’t quite right or not fully defined, so once it was built it had to have changes made. The earlier programmers were not very skilled themselves (the tools and language they used were “poorly known” to them) so they didn’t code in a way that was easy to refactor or modify. The result is that today we have a monster.

And now I have the joy of gradually upgrading this monstrosity bit-by-bit because they can’t afford a complete re-write. Oh well, I guess it keeps me on my toe trying to figure out how to turn the Bride of Frankenstein into a beauty queen :)

]]>