overuse

I worry about features like overuse of type inference when it means the types in question aren't explicit from the code that you're reading (agreed, not all type inference involves overuse).

More and more with each passing year, thanks to the overuse of the term and the shifting of its definition.

The gameplay's going to be crap, it's probably going to wildly overuse cutscenes, and the game's message isn't subtle at all.

We don't want the population to overuse antibiotics to avoid building resistance in the population.

However, I buy them when I can primarily because of my concerns with pesticide and fertilizer overuse.

Anyway, I've heard similar recommendations against overuse of shared_ptr for various reasons and I understand them.

Yes it is informal, but the overuse of italics makes it come across as mocking, which is what I was referring to.

But like every other paradigm in programming, don't overuse it.

As to the overuse of acronyms; I think they are overused in this profession.

That seems very low, is the sugar overuse that bad?

It wasn't long before I was constantly fighting overuse injuries, so I quit competing.

I think a lot of the issues involving overuse of state, are primarily related to using OO when a pure function would suffice.

Predictably, just like overuse of antibiotics in confined factory farms has created resistant "supergerms" leading to animals being overdosed with ever more powerful antibiotics, we now have huge swaths of the country infested with "superweeds" and "superbugs" resistant to glyphosate and Bt, meaning more volume of more toxic pesticides are being applied.

Overuse and broad use have made the term useless anyway.