6 Answers
6

IMO, somebody's first few years in an industry set an internal standard for what is acceptable and what isn't. I seriously question if working somewhere who a) doesn't know better and/or b) doesn't care, is good for your long term career.

I'd suggest alerting them to the problem (in a non-condescending manner) and if they don't make it a priority to fix it, start looking for a new job.

As long as it's identified as a debug version (beta release, for example), then it's "ok". But I would think that after 4 years they would have figured it out. I don't think it's a good sign that this has been going on for so long.

If they don't care about any of the reasons NOT to release debug code, why waste resource getting release to build? If you work for a profitable company, instead of an organization with zero profit motive, there needs to be some benefit to an action which will cost resources.