|
|
|
|
|
by tunesmith
4567 days ago
|
|
We had a "hero" on one of my teams that was strong conceptually but made poor implementation choices. Hacks with poor design that invariably didn't integrate well. High energy, always jumped right in - when others wanted to slow down and consider stuff, it looked bad by comparison. Deadlines became more stressful with more last minute bugs (that he would special-case "fix" - hero!!), and it was impossible to complain about him because our manager wasn't deep into the code. |
|
You needed code reviews and design documents. If your group was too busy for this, then it needed this "hero" to keep pushing code out the door instead of dwelling on design choices.