Linked by Yamin on Wed 9th Sep 2009 16:17 UTC
General Development I've been developing software for quite a few years. One of the issues that seems to come up again and again in my work is this concept of design and implementation. I recall it being a significant part of my education at the University of Waterloo's Computer Engineering program as well. The message was always the same. Never write code first. First you must design software by writing a design document, flow charts, pseudo-code, timing charts... then it's merely a trivial matter of implementing it. Make note of the attitude here given towards implementing. The real work is in the design, and it's just a trivial matter of implementing it. It sounds so simple doesn't it? Now, how often does this work out in real life?
Permalink for comment 383088
To read all comments associated with this story, please click here.
that methodology, as a rule, sucks
by goffster on Wed 9th Sep 2009 19:33 UTC
Member since:

It assumes that people know, ahead of time, what they want, (i.e. a bridge, or a rocket, or a computer switch).

It is rarely applicable to anything that requires flexibility.

i.e. It is rare that someone says (late in the cycle), "you know, I think we really need to send 20 people to the moon in that thar spacecraft, instead of just 3".

Reply Score: 1