16 Things that make a Developer scream, "NO!"

Do not comment or indent the code

Self-explanatory.

Do not write documentation or see it as useless

See #1, as also self-explanatory.

Without using any library, write all the code from scratch

Implementing some optimization or search algorithms and then banging your head on many missing edge cases and optimizations.

Reinventing the wheel

I see this A LOT and all too often!  There are solutions and best practices, but still, try to find a way by spending hours on a very complex solution or something already existing they don't know.

Self-esteem at the highest levels

The absolute beginner does not know what they don’t know, so as soon as they pick up a new technology and begin to get comfortable believing they know everything.

Write for yourself

Without worrying or not knowing the code must be for others or that you will forget the reasoning in a few months.

Working in a team is considered "taboo"

(The Rockstar complex) There are strong people working in a team that is beneficial, but the technical leader is "marching to their" own beat, and the rest of the team's agenda does not match.

Take code reviews personally

Angry and inability to accept development advice during the code review.

Do not communicate delays in the project to disfigure, except when it is too late

It cannot do without it.

Highly interconnected and not very modular code

DRY (don’t repeat yourself) is generally ignored. The modules (if any) are highly interlinked and not interchangeable.

Lack of logic in the development

How many "if/else" states, global variables, monolithic classes, constructors, and the code executes after you had lunch and a nap.

Variable names

Yes, the inexperienced programmer uses insignificant names for variables rather than self-documenting the code with meaningful names.

Unreadable and unmaintainable, uncommented, undocumented code, files, functions, etc

Just because you say "Eureka! It works!" doesn't mean it needs to live on.

Write in 10+ languages what can be done in one

Albeit, if you claim to be proficient in 10+ development languages, a life you need!

It shouldn't take you more than a day to do this

If it were that simple, many developers and programmers would be out of a job.  An amateur or fuzzy developer will claim the "salesperson" approach to the answer or the solution.

A conversation feels like a technical interview

Coding is an important part of your job but there has to be more than that.  What kind of coffee do you drink?  Did you see the Falcons lose yesterday?  How about that traffic?