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

I'd love to see an actual bug-free codebase. People who state the codebase in bug-free probably just lack awareness. Even stating we 'have only x bugs' is likely not true.


Top commenter's "AFAYK" acronym is covering that.

The type that claims they're going to achieve zero known and unknown bugs is also going to be the type to get mad at people for finding bugs.


> The type that claims they're going to achieve zero known and unknown bugs is also going to be the type to get mad at people for finding bugs.

This is usually EMs in my experience.

At my last job, I remember reading a codebase that was recently written by another developer to implement something in another project, and found a thread safety issue. When I brought this up and how we’ll push this fix as part of the next release, he went on a little tirade about how proper processes weren’t being followed, etc. although it was a mistake anyone could have made.



We kinda always leave documentation and test bugs in. Documentation teams have different scheduling, and tests are nice TODO's.

There are also always bugs detected after shipping (usually in beta), which need to be accounted for.


>I'd love to see an actual bug-free codebase.

cat /dev/null .


A specific individual execution is not a codebase.




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

Search: