4 ms·
If I came into work today and brought up the idea of doing a complete code rewrite, I'd either get laughed out of the room, or even worse, threatened with being
by MartinCron 13y ago
If I came into work today and brought up the idea of doing a complete code rewrite, I'd either get laughed out of the room, or even worse, threatened with being fired
If that's really the case, then you're working with a bunch of abusive, pedantic, and narrow-sighted assholes. I will generally say "no" to the idea of a complete code rewrite of any meaningful and currently useful system (based on my own experience as much as Joel's article), but I won't laugh at people or threaten to fire them over it.
- umsm 13y agoOr they may have experience with people that walk in and declare all code as "insecure" and "dangerous" or "unusable". They usually promise the world and deliver a small fraction, if even that. Then, for the next 9 months delay the "1 month" project week after week. The product owners love this one. It cost them hundreds of thousands of dollars to get to square one again. And all of this happening to a product that wasn't released yet. At the end, the developer quit and everyone in the company agreed that it was good to see them leave.
- MartinCron 13y agoGood to see you're not bitter about that.
- umsm 13y agoWell, I am young, so I may go through something like this again. But at the moment, I was totally against it. Now, when something like this comes up again, I learned enough to PLAN through it better. Realistic deadlines will make any work place a better place to be.
- MartinCron 13y agoOf course, and it is easier to plan for incremental replacement and refactoring than for a wholesale re-write.