Reputation
Next privilege 125 Rep.
Vote down
Badges
1
Newest
 Supporter
Impact
0 people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
Dec
8
awarded  Supporter
Aug
6
comment Unwritten rules of rewriting another team member's code
I don't think this is specifically mentioned in any of the [excellent] answers: even if existing code deserves a rewrite, if it works now, it is very likely a waste of time [money] to rewrite. I have learned that in many scenarios quick 'n dirty is the way to go. You're paid to write code, so you should be as efficient as possible. You don't need a well-designed framework for something that will only be run a few times. You don't want to take a week to do something that could have been done in a day using poor design practices. Many times managers prefer this approach.