DEV Community

Cover image for My Most Embarrassing Mistakes as a Programmer
David Neal
David Neal

Posted on

My Most Embarrassing Mistakes as a Programmer

My most embarrassing mistakes as a programmer, in no particular order:

  • I didn't ask for help
  • I was afraid of what others would think
  • I didn't follow through on a promise
  • I didn't step up and take responsibility
  • I avoided conflict
  • I didn't encourage others
  • I didn't publicly celebrate the success of others

My biggest mistakes had nothing to do with programming.

The most difficult parts of any job, and the most valuable activities of any job, have nothing at all to do with technology.

It's people. How we value ourselves. How we value others.

"Soft skills" is an awful term. The things we call "soft skills," such as listening, communication, team dynamics, empathy, ought to be given so much more priority in our workplaces. These are core skills that apply to anyone in any profession.

Here's the mindset I want.

To be the most effective member of any team, I must first strive to model integrity and work ethic. I need to be respectful, helpful, patient, gracious, trustworthy, and hardworking. I need to be transparent, such as asking for help, owning mistakes, and asking forgiveness, regardless of my fear of the outcome, because it's the right thing to do. When I see a failure in our system, not just in the work we create but also our system of work and treatment of people, I need to take responsibility, speak up, and see it through correction. I need to give people the benefit of the doubt, try to understand their perspective and circumstance, be slow to anger, and be quick to forgive. I need to encourage and lift others up and help them to see their career and life through a bigger lens.

I am a work in progress. I may not achieve these things every day, but that's my goal.

I hope this post gets you thinking of ways you can have a positive impact on the people you work with.

Remember, every day is a fresh start to be more awesome!

Top comments (11)

Collapse
 
murrayvarey profile image
MurrayVarey

Same, it's always a failure to communicate. I've had projects that were unused, unwanted, and unloved ... all because I failed to ask the right questions. I try not to be embarrassed about these though -- it's hard to learn if I'm busy cursing myself.

Collapse
 
peledzohar profile image
Zohar Peled

"I am a work in progress." That's true for everyone. Remember that the next time you disappoint yourself.

Collapse
 
jasonspd profile image
Jason Luu

Well said, Google has written about "psychological safety" as one of the qualities in a great team. google.com/amp/s/www.forbes.com/si...

Collapse
 
mikaoelitiana profile image
Mika Andrianarijaona

I didn't read very well the documentation (I was too fast)

Collapse
 
pernambucano profile image
Paulo Fernandes

Dude, Thanks. I really needed to read that.

Collapse
 
andyoverlord profile image
Andy Zhu

Very inspiring, thank you for sharing.

Collapse
 
vjnvisakh profile image
Visakh Vijayan

Good read

Collapse
 
messerli90 profile image
Michael Messerli

Words to live by. Thanks for sharing

Collapse
 
attkinsonjakob profile image
Jakob Attkinson

Thanks for sharing

Collapse
 
chpecson profile image
Christian Pecson

Indeed, sometimes falling short on soft skills but still a work in progress. A good read.

Collapse
 
grsahil20 profile image
Sahil

After 8 years of experience, I feel this is what i have been missing a lot on.