Timeline for What to do with developers who don't follow requirements?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2019 at 17:28 | comment | added | WGroleau | “Make absolutely clear … If it doesn’t sink in” refers to those steps. | |
| Oct 22, 2019 at 7:35 | comment | added | Graham | Sure, but there are steps before that. Maybe they'd correct him - or at least prove he's incorrigible. | |
| Oct 22, 2019 at 0:22 | comment | added | WGroleau | I saw that remark. But "averse" doesn't mean we never dismiss the incorrigible. | |
| Oct 21, 2019 at 21:06 | comment | added | Graham | The OP has said that the company is averse to firing developers. But there are steps before that. The first step is an informal warning; and the steps after that are formal warnings, delivered together with your boss, which go on his records and will prevent him even getting a pay rise at his next review, never mind promotion. | |
| Oct 21, 2019 at 18:40 | review | First posts | |||
| Oct 21, 2019 at 19:26 | |||||
| Oct 21, 2019 at 18:39 | comment | added | WGroleau | Also, anyone who consistently delivers incomplete and/or buggy code should not be called an experienced developer. “Experience is what enables you to recognize your mistakes when you repeat them.” Apparently he has not even reached this tongue-in-cheek definition of experience. | |
| Oct 21, 2019 at 18:36 | history | answered | WGroleau | CC BY-SA 4.0 |