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

Even then, mix in people switching jobs, losing the knowledge of where or what all these landmines are, and add similar but unrelated issues across your entire codebase. This stuff adds up. I like to at least add stern log messages when we are at 10%-50% of the limitation. It's saved my ass before, especially when your base assumption can be faulty.

In one of those scenarios, where we expected the growth of an integer to last at least 100 years, due to certain unaccounted for pathological behaviors, a user burned through 20% of that in a single day. But we had heavy warnings around this, so we were able to address the problem before it escalated.



I'm assuming this is C/C++ so I'm wondering if there isn't some compiler pragma to have it warn people still building the code in 2025 or so?


Ha! Rebuilding the code. The source will be lost and the binary will be irreplaceable in many circumstances.


Embed the source code in the binary.


Wow, these libraries are way too large

strip a.out




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

Search: