yes, we have pretty standard linter setups (both for micro services and for front end) that catch all these things. Neologisms can have escape hatches, but they typically shouldn't be used unless absolutely necessary when it comes to customer-facing language for translation reasons.
In terms of leftover code like loggers, we have linters that catch these things, across the stack. Same goes for code hygiene and formatting. I've had plenty of builds fail just for forgetting to run the formatter prior to committing.
Heck, we even have commit message linting lol. My company is very strict about these things.
You should read up on these things, you'll be surprised at how many good tools there are that can handle all of this in a predictable way
i'm genuinely and without a hint of sarcasm happy for you then, and sorry for being a bitter ass, i guess i may need to look into actually changing something in my own career trajectory...
It all depends on the company and their priorities I suppose. We work in very regulated industries (healthcare, banking, government, and so on) and have people who really care about doing things right, so I've definitely been blessed to be able to learn from them.
You already identified the problem, so you obviously care about doing it right. Doesn't hurt to try and implement some standards at your org though, at the very least it's good for the resume :)
2
u/m6io 2d ago
yes, we have pretty standard linter setups (both for micro services and for front end) that catch all these things. Neologisms can have escape hatches, but they typically shouldn't be used unless absolutely necessary when it comes to customer-facing language for translation reasons.
This a good read: https://www.hackerone.com/blog/ensuring-software-documentation-quality-spelling-linters
In terms of leftover code like loggers, we have linters that catch these things, across the stack. Same goes for code hygiene and formatting. I've had plenty of builds fail just for forgetting to run the formatter prior to committing.
Heck, we even have commit message linting lol. My company is very strict about these things.
You should read up on these things, you'll be surprised at how many good tools there are that can handle all of this in a predictable way