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 383094
To read all comments associated with this story, please click here.
RE[2]: Must be nice...
by cjcoats on Wed 9th Sep 2009 20:10 UTC in reply to "RE: Must be nice..."
Member since:

A developer who imagines he has found a compiler bug is wrong, in 99.999% of the cases.

In every one of the two-dozen-or-so cases that I've
been trying to build an executable and the compiler
message was "ERROR: Internal compiler error in phase..." what I have found is certainly a compiler bug.

In every one of the similar number of cases where the compiler seg-faulted, it was also a compiler bug.

I think your "99.999%" is a WAG.

Reply Parent Score: 1