News for hackers. Stuff that matters.
Re:Dad and the ten commandments of egoless programming (2012) by epolanski on Sunday January 16, 2022 @09:34PM (#29962742)
The overwhelming majority of comments I read, and I wish that was true just for my company, it applies to majority of OSS as well rarely if ever catch a bug.

I see most of the discussion involve preferences, practices and names, rarely api and architecture, even less bugs.

Re:Dad and the ten commandments of egoless programming (2012) by ScottBurson on Sunday January 16, 2022 @11:18PM (#29963265)
It's very hard to catch bugs in a code review. I manage it occasionally, but it's much more common that I'll be working on something else that touches on some piece of code that already passed review, and then I'll notice a bug, because I'm already thinking about how that module should work -- I have already loaded the relevant context into my head. Loading that context just to do a code review takes too long.
Re:Dad and the ten commandments of egoless programming (2012) by not2b on Sunday January 16, 2022 @11:33PM (#29963341)
I very commonly catch inadvertent quadratic or even exponential algorithms in code reviews. The code normally will produce the right answer ... eventually.