3 ms·
You have no idea how much I hate the people who are paid for 8 hours of 'butt in the chair' but they only show up for 6 and of course it's their code that break
by Kenji 9y ago
You have no idea how much I hate the people who are paid for 8 hours of 'butt in the chair' but they only show up for 6 and of course it's their code that breaks first and of course they've already gone home when the bug report comes in and of course the code is so obscure that one would have to ask them or else spend 5 additional hours on it.
- z1mm32m4n 9y agoEveryone's code breaks eventually. Even the people who spend 8, 10, or 12 hours in the chair. The solution is not to require that everyone spend 8 hours at work. Rather, it's to require that the code be explained and discussed in code review. After that, there's an on-call team (which may or may not include the original developers of the code!) who handles the system in case of a breakage. Butt in the chair time is completely irrelevant to this process.
- majewsky 9y agoSounds like you need unit tests. Or at least a rollback button, so the bug doesn't cause harm until you can dump the problem on that person's desk again next day.
- owenmarshall 9y agoFlip your premise around a bit: what kind of world do you live in where "obscure code" makes it to a production environment after hours? Do you not do code reviews to ensure good quality? Do you not test your releases before launch? Do you not have a release strategy that allows you to launch code when people are in the office? Why aren't you fixing that rather than blaming your coworkers?