- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
I live in the city with the hoppiest beer in the country, and it's horrible. Can't try most new breweries since all they brew tastes like a pine forest.
Admin
^ This. So much better than the original article. +9000
Admin
Some people suffer from what I call "the myth of the original developer." These people often claim and seem to think that...
The original developer knew all the requirements. (That nothing was written makes no difference. And the question of what the business wants and needs NOW is somehow irrelevant. Some people seem to think that the original requirements are gold.)
The original developer understood the design. Certainly they had a perfect and complete plan for design, architecture, etc. If only we could talk to the original developer, everything would be clear!
I've never been able to figure out why some people have this obsession with "the original developer." My experience has been that original developers were often clueless and did bad work; that's why I was called in to fix it. And even if their knowledge had been perfect, it's always outdated.
Now sometimes previous developers can give you insights as to why things were done the way they were. And sometimes the real reasons can't be discussed openly without risk of termination. ;->
Admin
These stories are almost readable if these events and conversations are all taking place in Sergio's mind. Maybe that's going to be the denouement; I haven't read part 3 yet. Otherwise, this is just way over-the-top embellishment. We're supposed to believe this crap really happened? Puh-lease!