Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

indeed, being on-call cleanses many developers of slopulist habits


That depends on how quick the feedback loop is for your decisions. If it takes weeks or months to find the impact of your changes, or worse, if you're insulated somehow from those changes, you may not be pushed toward improving the quality of your code.


A company where it takes weeks and months to deploy a code change is not a company with a long term success horizon.


Lolololol, sorry, I can't help but laugh a bit because some of the most entrenched companies are also the slowest moving.


It depends on their sleep habit, work-life requirements and compensation when they need to be on-call.

When you get a fatter check because your code break, the incentives are not in favor of good code.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: