How do you deal with arrogant developer?

If you know or work with programmers who have come down with a severe case of arrogance, don’t avoid them, try to help them. Ask them to explain what their code does; this forces them to either prove they know what they are talking about or make up excuses (“I dunno why it works, it just works! Stop bugging me.”).

What are the characteristics of good and bad software design?

Difference between Good Design and Bad Design in Software Engineering

Characteristics	Good Design	Bad Design
Logic	Every piece of logic has one and one home.	Logic has to be duplicated.
Nature	Simple	Complex
Cost	Small	Very high
Link	The logic link can easily be found.	The logic link cannot be remembered.

What is the worst trait of a software engineer?

Good programmers will write bad code if they have to work to deadline. Now, I think the worst trait of a software engineer is arrogance, but there are three kinds of it, all toxic in different ways. For lack of a better metaphor, I’ll call them cold, tepid, and hot arrogance.

Why do software engineers write so much bad code?

Also, most bad code isn’t the result of terrible software engineers but of aggressive deadlines, poor management, and inattention to technical debt. Of course, that can create an environment in which potentially capable programmers will atrophy and become terrible over the years, and that can happen, but it’s not my focus here.

What is cutting-in-line arrogance?

This is cutting-in-line arrogance more than it is inflated-self-opinion arrogance: the arrogance of doing something unremarkable but transgressive under the assumption that they’ll get away with it.

What is hot arrogance?

Hot arrogance is that of the “rock star” who can’t work well with others, leaves scathing code reviews, and who changes APIs by the hour and doesn’t bother to tell anyone because everyone else should consider themselves privileged to work with his hot-stuff code.