3 ms·
The current system I am working on has a history of developers... How do you know that? Imagine working on a system with no standards, documentation, version
by edw519 18y ago
The current system I am working on has a history of developers...
How do you know that?
Imagine working on a system with no standards, documentation, version control system, or audit trail.
Oh wait, some of us don't have to imagine.
- stcredzero 18y agoI know the history of the system in my current job, because there are people from its inception over 12 years ago. They've told me about how subsystems have been rewritten. I've also witnessed it in my 3 years there. It's not always pretty. I've seen one subsystem rewritten 3 times by 3 different people who each thought they were smarter than the last guy, but then went on to make the same (very subtle, very difficult to understand) mistakes. The 4th time has stuck, however. The resulting code is much cleaner and is finally (relatively) trouble free. Its approach is significantly different from the last 3 attempts. Figure that! I've also seen subsystems evolved in 2 or 3 iterations by the same developer, each iteration involving a rewrite. So, I'd have to say my current shop is pretty good. They really should be doing more refactoring. They could be doing more incremental improvement and avoid the pain of complete rewrites. But at least they are wise enough to avoid pounding their heads against the wall of bad design indefinitely. (Or, to be fair, naive 1st drafts.)