Timeline for Handling low quality work from a senior
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2023 at 15:08 | comment | added | Thorbjørn Ravn Andersen | Tests can be written. The important thing here is that the architecture chosen was not good enough. This should have been caught before any code was written. | |
| Jul 8, 2014 at 15:28 | vote | accept | Andy Hunt | ||
| Jul 7, 2014 at 20:39 | history | edited | Andy Hunt | CC BY-SA 3.0 |
deleted 4 characters in body
|
| Jul 7, 2014 at 20:29 | history | edited | Andy Hunt | CC BY-SA 3.0 |
added 294 characters in body
|
| Jul 7, 2014 at 20:26 | comment | added | Andy Hunt | I've added answers to the comments in the question | |
| Jul 7, 2014 at 19:11 | answer | added | John G | timeline score: 3 | |
| Jul 7, 2014 at 17:35 | history | tweeted | twitter.com/#!/StackWorkplace/status/486201810072662016 | ||
| Jul 7, 2014 at 17:20 | comment | added | Vietnhi Phuvan | 1. What incident was it that triggered your review of the code? For example, something broke down and in the process of investigating why, you checked the code and you collected a whole sackful of worms. 2. From your narrative, it looks like your team leader's coding was slapdash affair. Has anybody besides the two of you reviewed his code? The more senior people you have by your side, the less likely he'll make a fight out of it. | |
| Jul 7, 2014 at 16:37 | answer | added | Telastyn | timeline score: 9 | |
| Jul 7, 2014 at 16:06 | answer | added | Garrison Neely | timeline score: 17 | |
| Jul 7, 2014 at 15:56 | history | asked | Andy Hunt | CC BY-SA 3.0 |