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 383080
To read all comments associated with this story, please click here.
RE: Must be nice...
by SamAskani on Wed 9th Sep 2009 18:27 UTC in reply to "Must be nice..."
SamAskani
Member since:
2006-01-03

I'd inclined in option 2. In function of the decision done in your organization/company, you can easily spend some years before hitting that head-scratching compiler bug (I'm pointing to you! first releases of GCC 4.X series, GCC 4.3.2 and VC ++ 6 before first SP).

If you are lucky enough of using a subversion of GCC quite stabilized or a "semi-old" version of VS with all the service packs, you have one of the first conditions to be in coders' paradise: You can really trust your compiler.

And coming back to the point of design, 10 years ago I remember that UML tried (and was successful at some point) to simplify design and coding by bringing them together as much as possible. I remember it was quite cool to export/import in Rational Rose all the definitions of our classes. No idea how much it is still in use.

Reply Parent Score: 1