Linked by Thom Holwerda on Mon 17th Oct 2005 20:27 UTC
Features, Office "No one makes bad software on purpose. No benevolent programmer has ever sat down, planning out weeks of work, with the intention of frustrating people and making them cry. Bad software, or bad anything, happens because making things is hard, making good things doubly so."
Permalink for comment 46674
To read all comments associated with this story, please click here.
Tuishimi
Member since:
2005-07-06

...and I will tell you that the best code I ever wrote was for DEC because we had rules to follow. Coding standards, review processes in place, documentation throughout the life cycle, etc.

Every where else I have been they have tried to do it. Not with a ton of success. But these new trends... I just don't know. I guess I am old fashioned where I believe 90% of the code is written in the requirements and the functional specification before the actual coding ever begins. By that, I mean the requirements have to be good, the functional design has to be good, THEN the basic functional test plan should be in place and THEN begin with the design specifications.

But these days it goes like this: You have 2 months to do X Y Z. Now get to it and DO IT RIGHT! Well, the battle is already lost at this point. Software engineers are no longer allowed to "engineer". That's why we are all becoming "programmers" and "developers".

:(

Reply Score: 5