- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- 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
Carl Ichan, anyone?
Admin
Management is wrong here because we all know that the real problem will never be addressed after the temporary fix is slapped together. However, I have worked with way too many developers who were terrified of making any change for any reason. They don't know what to do so nobody else is allowed to either. Therefore, a system that has to go through a ridiculous testing script on every single change is already fucked.
In my experience, it usually seems that one bad developer is allowed to run wild without any interaction and is untouchable until the crisis hits. Afterward, the company does a complete 180, where nobody, least of all a good developer, is allowed to do anything because they're so frightened. So you end up with systems that just waste a ton of resources (time and money) making life miserable for everybody involved and they stay that way forever.
Admin
I often copy, paste and edit, then refactor when I can see which parts are in common.
Admin
I make it a personal rule never to copy-paste my own code. Any time I reach for Ctrl-C, I mentally assess whether I want the whole lot, and usually break the code block out into a generic function. Having read enough TDWTF, I'm eager for my code not to end up here one day (my exploits with sysadmin'ing are another story...)