DEV Community

JordanDickow
JordanDickow

Posted on

Failure is not Optional

I've been hard at work in my job search for almost 3 months now. As I said in my Job Search article, I've had more rejections throughout the process and it's come in different stages of the application process. It's been discouraging knowing what position I'm applying for and it feels like I'm being put through the wringer for the entry-level/junior developer position that I'm applying for. My job search for my first tech job has made me realize how much failure comes with getting what you want.

As this is a tech blog, I can't help but point out the truth that comes before any technical skill you learn being a software engineer, which is how much we depend and thrive off of failure. As software engineers, we depend on error-driven development. We fix error after error until we get a functional application, and then we refactor our code to optimize our app and make it run more smoothly. Which leads to even more errors.

I wear my heart on my sleeve, which makes me a very open and honest person. When I fail my colleagues know it and when I succeed I like to share it with my colleagues as well. What you see is what you get with me but that doesn't mean I don't change. The pain that I worked through at my boot camp in the General Assembly was getting used to failure itself. Failure early on to becoming a Software Engineer was getting used to errors. I had to work through was I felt I was the only one open to talking about my failures. Everyone was better at hiding their struggles, where I was open about it.

My point of this article is to start talking about failure in a more positive light. More importantly, it needs to be talked about in a more positive light because you have no choice in any career, especially the tech field, but to fail if you want to get better. Failure is mandatory in order to get better and I want more people to be open about there failures.

Top comments (0)