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

Not just the code itself, but the author. I worked with a guy that wrote at least one bug every time he created a PR.


"If debugging is the process of removing software bugs, then programming must be the process of putting them in."


> wrote at least one bug every time he created a PR.

An economic hero. A man of the people. Creating job security for QA departments!


A friend working in office of a big-tech company located in Denmark said "one bad engineer like me working in Copenhagen can put food on the table for 20 Bulgarians working in customer support".

Since that day I always wanted to get into FAANG-type companies, writing buggy code is basically philantropy.


This thread made some people question their no-bugs-allowed ideal, which is apparently a misanthropy…


Facebook release engineering famously kept riskiness scores for each developer and used that as a signal for whether that developer's changes got deployed or instead received extra scrutiny based on a history of broken deployments.




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

Search: