4 ms·
I remember my first programming job straight out of school, where a full clean build of our project emitted 10K+ warnings, and I thought to myself, "Is this rea
by ryandrake 9y ago
I remember my first programming job straight out of school, where a full clean build of our project emitted 10K+ warnings, and I thought to myself, "Is this really how professional programming is?" Asked a co-worker why on Earth we don't fix them, as there may be serious bugs hiding in there, and the response was "We're too busy fixing bugs!"
- Pxtl 9y agoHonestly, if there's a warning you've accepted as a known issue or inapplicable to your code, just suppress it. Maybe document it as a low priority bug in the tracker so it has a place on the to-do list, but get it out of the compiler results.
- munificent 9y agoRelated: "We're going to rush through implementation so that we have lots of time left at the end to fix all the bugs caused by rushing through implementation."
- draw_down 9y agoAlso we will never actually do that last part.
- frozenport 9y agoRelated: "We're not sure if this product has a market, and the company that will acquire our tech will integrate it with their stack."