These Mistakes Almost Got Me Fired as a Web Developer

All of us make mistakes from time to time, whether it’s at home or work. There is no avoiding it because we are all human, and humans make mistakes a lot.

As a developer, I want to talk about something important for all developers. Whether you’re a software engineer or an aspiring developer, this is something that all of us need to know.

It was almost career-ending for me.

There were a handful of mistakes that I’ve made, and these mistakes almost got me fired. I was confused, and I didn’t know what to do at the time, and that is why I need to let all of you know how to avoid these mistakes.

Pride

Developers should have pride in their work and passion. However, it’s better to leave pride at the door when it comes to actual coding than to bring it to work.

I’ve been struggling with this mistake for a long time, and it’s not just months but years. You have to ask yourself if it’s worth it to hold on to that pride. Otherwise, it’s only going to hinder you in your career as a developer.

Imagine you’re a beginner at the gym, and you’re carrying all of this pride with you. In the end, you’ve got an injury for straining yourself with the equipment you shouldn’t be using.

What I’m trying to say is arrogance and showing off will be a developer’s downfall. Humble yourself to the point where you’re willing to listen to your seniors and learn more code to get things done.

Never Asking Questions

This mistake is closely related to the first one, where we’re too afraid or too prideful to ask questions. However, companies with senior developers or managers hate it when you ask too many questions.

Asking questions shows that you want to learn more and you want to stay in the know. I was fortunate enough to stay at a company where questions were always welcome.

Yet, because of my pride, I wasn’t willing to ask for help.

I started learning that asking questions not only gives you information or lets other people help you. It also helps improve your relationships with your friends, family, and even your colleagues.

It’s important to remember that not asking questions will leave you behind and set you up for failure. Don’t be afraid to ask for help when you’re unsure of things or if you need an extra pair of hands.

Getting Too Comfortable

The third mistake is getting too comfortable with where you’re at right now. It’s extremely dangerous for developers because it means you’re no longer interested in trying new things.

It means that you’re satisfied with where you’re at right now, so you stop trying to learn more.

You stop trying to get better, and you stop aspiring to become a developer.

The industry that we work in is highly competitive and fast-paced, where we encounter new technologies and languages. I’ve seen friends and colleagues get laid off and start a recent job weeks after because they weren’t comfortable.

Getting comfortable is dangerous for people who want to learn new things and improve aspects of themselves. I was affected by this, and that’s why I took a two-month break to focus and find my rhythm because I didn’t want to get comfortable.

I want to work hard because I love what I’m doing.

Not Making an Effort to Improve

Much like the last mistake, the fourth mistake is about not making a conscious effort to improve. As developers, we have to become consciously trying to improve whether we’re at home or work.

You need to stay invested in what you’re doing, and you need to stay interested in it too. The more you invest and stay interested, the more you’re retaining what you’re typing and what codes you made.

When you invest yourself into your work, you know more than the average casual worker. And if you know more than the average casual worker, you can fix whatever problem you have in the future.

Not Having Confidence

All four mistakes connect to the biggest mistake that any developer can make: lack of confidence. There is a difference between pride and confidence.

One time, my boss saw my Youtube videos and told me that I was brimming with confidence. However, when I got to the office, it was the complete opposite. My boss and my colleagues would often say that “Chris, you’re better than you realize.”

That is something that all of us as developers need to remember. We are better than we realize because you’re making a conscious effort to get better if you’re reading right now.

Overcoming the lack of confidence problem is easy when you know what to do, and that’s doing the opposite of everything I talked about.

Leave your pride, always ask questions, don’t get too comfortable being in the same place, and make an effort to improve.

That’s what I believe every developer should do because we are better than we think.