13 Undesirable Behaviors in Software Engineers: Are You Guilty?

The post says technical skill is not enough to shape a software engineer’s career. Behavior affects how people work together, and traits like condescension, defensiveness, and poor communication can limit trust and progress.

It also points to habits that make teamwork harder, including interrupting others, asking for help too early or too vaguely, staying silent in disagreement, rejecting feedback, deciding too fast, avoiding conflict, overestimating timelines, ignoring customer needs, and running meetings without a clear purpose.

Reading notes

#

• Engineers can be strong technically and still hurt their careers through behavior.
• Getting annoyed at naive questions, being dismissive, and being overly pedantic make others less willing to work with you.
• Saying “I don’t know” can keep a discussion going, and repeated gaps are worth studying later.
• Cutting people off during conversation shuts down collaboration.
• It helps to try solving a problem, document what you tried, and then ask for help with context.
• If you disagree in a meeting, bring it up respectfully there or follow up offline.
• Feedback should be checked for possible truth, reflected on, and followed up with specific examples.
• Strong opinions are fine, but listening fully and asking questions matters more than proving yourself right.
• Quick decisions without enough context can damage trust.
• Trying to please everyone can lead to vague recommendations and indecision.
• Struggling alone is presented as inefficient; sharing the blockage and what was already considered helps others help you.
• Overly optimistic estimates can miss deadlines, so past data, buffer time, and risk awareness matter.
• Engineers should focus on the right solution for customers and business goals, not only the most technical solution.
• Meetings work better when they have a clear purpose, pre-read material, and attention to staying on topic.