4 ms·

Isn't that answered in your quote: "I’ve heard people complain about the prospect of being on-call, so I’ll just ask this: if you’re not on-call for your code,

Isn't that answered in your quote: "I’ve heard people complain about the prospect of being on-call, so I’ll just ask this: if you’re not on-call for your code, who is?" To me this implies an on-call rotation where you know your expectations. Not "we need to be on call continuously, 24/7, meaning we can't ever be off the grid or unavailable". Many other industries have the idea of being on-call, and they are "expected to give up our personal lives at a moment's notice" when they know they are on-call. (For example, my brother in law is a surgery tech; he's had to take off during family outings more than once) Also, if this happens often enough that it's a serious problem, this says a lot about the quality of the code you own.

yawaramin 6y ago
Code quality is a result of many factors, but the single biggest factor is whether Management treats developers as a profit centre or as a cost centre. That makes the difference in: - Developer compensation - Training and career development - Staffing properly i.e. not under-staffing - Giving devs proper slack time between tasks and not over-burdening them with projects - Letting developers own the stack not just in name only but truly own the technical decisions made in the stack without micro-management, including choice of language, platform, etc. Without all those factors, it's a red herring to point to the code quality. The code quality is just the final output of all of the above decisions.