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

I'm thinking less in "way the code is written" and more "the way the code works".

That is things like cases it doesn't support, or weird results in some cases.

One example is a shop I worked many years ago that had a function which did time conversion on date times without adjusting the date portion. Obviously, objectively, wrong.

However the callers to this function expected this errant behavior. Actually changing it to behave correctly would require a coordinated change. Putting that comment in place prevents a new hire from going "oh this is obviously wrong!" and fixing it, causing an outage.



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

Search: