A Little Background
Back when I started my web developer journey, everything was much simpler than it is today.
I started out using Mosaic web browser and then not too long after moved to the beta version of Netscape.
Developers at that time learned things together, as new features were added into the browser, we would share how we used them over a snack at the local bakery.
This lead to a decent amount of shared learning. Back then there was basically two things that were handy to know, HTML and Perl.
HTML for the web design and if there was any web form processing, we would use Perl.
While Perl has other more beneficial uses, Just knowing enough to process a web form was enough for a lot of use cases.
At the time, database administration was a more specialized job, MySQL and Postgres were not yet around, so the job of a web developer was more concentrated on HTML, Perl and Web Design.
Not long after, CSS and JavaScript were introduced, and as the 90s rolled on, Cold Fusion, PHP and others were added in.
PHP was simplistic, and for me , was the next logical choice, as was dipping my toes into databases now that they were more accessible.
The Web Development Shift
During the next few years, there was a large shift in web design and development. PHP and other server side scripting became more polished and accessible.
While Perl was still relevant, other options like Python and Ruby gained popularity.
There was also a shift in front end web design. Faster internet speeds opened up the internet to more graphic heavy design, and web standards were developed and tuned.
While Developers were busy learning new back end technologies, front end development matured into more complex designs requiring better graphic design skills.
This created a split in web development, where web development split into back end and front end specialists.
Burnout In Developers
Fast forward to today, where it's all too common to see posts on social media, especially from junior developers suffering from burnout.
Polls taken have shown that up to 83% of developers have suffered burnout, with high work load the most common reason.
High work load can be a combination of potentially long work hours and pressures to spend time after work learning more just to keep up.
Back when I started, the journey tended to lead itself, where new technologies were introduced at a rate where learning the new technology was just a natural progression, we were eased into learning new things.
I still believe that taking time to introduce yourself to a new technology and concentrate on it has a better outcome than introducing multiple technologies at once, where you have to split your time between them.
In a lot of cases, the pressure to learn multiple technologies to keep up, while balancing workplace expectations, leads to developer burnout and often leads to really good developers leaving the industry for simpler pastures.
New developers are bombarded with a large range of technologies, technologies that are ever changing, as are coding standards around these technologies.
Even within technologies there are multiple frameworks and libraries to learn, while trying to grasp the language itself, best practices, coding styles, and design patterns.
A look on Indeed at jobs listed as junior developer jobs shows jobs with vastly different tech stack requirements, leading to new developers to ask "where should I start?".
Adding to the problem is that the answers they receive can be wildly different, depending on the responders own developer journey.
There is not just one clear path to take, leaving junior developers needing to learn many technologies quickly to be successful.
To progress, they need opportunities to learn on the job but also take the initiative to continue learning outside work hours, stretching them thin.
Even as an experienced developer, the need to continually learn still remains. Those who don't spend time learning new things eventually get left behind.
One developer I recently spoke to, had been working his 8 hour days, then spending 3 - 5 hours a night on learning. This is great ambition to have, to want to learn, but it leads to burnout very quickly. We need time to rest and absorb.
Finding a good balance between learning what we need to learn and our own health and well-being can be hard to find.
Other Burnout factors
Along with burnout from trying to keep up and meet expectations from the work place, burnout comes from other factors also.
Home life can affect your developer life.
When you are dealing with life difficulties, mentally, there is only so much that you can do.
The needs of the home outweigh development (as it should). At some point you just reach a breaking point.
How others talk to you at work or online can lead to burnout. There are only so many negative code reviews that could have been written in a more positive manner, only so many times you can do a good job that goes unnoticed, before it takes its toll.
It's not that developers sit around waiting for appreciation, it's just that hearing it may be the inspiration they needed to keep going.
How can we help?
Developer burnout is multi-faceted but we can all do our bit to help our fellow developers from suffering, and prevent good developers from leaving the industry.
Be willing to share your knowledge
Even as new developers, share what you just learned, your excitement can be contagious.
Have patience with developers
While there might be gaps in their knowledge, there are going to be days where they return the favor and are able to teach you something.
Even experienced developers have gaps, don't look down on them because of their gaps.
Be mindful
While developers may write code that is not always great, they are learning, and I doubt there is a developer out there who hasn't been where they are at, and written code that we are not proud of.
Code Reviews
While at times code reviews need to be negative, there are ways to write them that lessen the blow to the developer.
When writing them, think about who you are reviewing, take the time to get to know the person if you can, it will help connect with them in a code review.
Often in code reviews, we are so fixated on finding what is wrong with the code, we forget to mention what is right with it.
Give praise where praise is due
Praise doesn't need to just be for big wins, praise for small wins may just be what the developer needed to hear that day.
It can be as simple as telling someone they did a really good job with something, even if there are flaws in their code, there are still positives that can be highlighted.
With the challenges new developers face, how we handle our interaction with them can make or break them as a developer.
This still applies to interacting with experienced developers, the challenges they face may be different from the challenges new developers face, but our interaction can just as easily make or break them as a developer.
You don't know what else might be going on in a developers life, and treating people with empathy can help them more than you will ever know.
How can we help ourselves?
We also need to remember to take care of ourselves to avoid burnout.
Take time for yourself
While there may be pressure to learn more and do more, taking time away will rejuvenate yourself.
Switch off for a bit
Do something you like to do that doesn't involve tech.
For me it's turning off the computer, putting my phone on silent and spending time outdoors, the beach if I can, lakes, forests and waterfalls if I can't get to a beach. A place where I can empty my head a bit.
Burnout tends to come from either pressure being put on you, or putting pressure on yourself. Take that load off where you can, so you can rest and reset.
Do something different
Learn something new just for yourself, or work on a new side project, something where you can do what you love doing but without any pressures.
The journey back from burnout is made of small steps. Gaining confidence back in yourself, confidence in your skill set.
Learning to once again love what you do.
Find the right balance
Find the right balance to be able to still learn, but learn at your own pace.
Learning at your own pace creates a more enjoyable and rewarding experience. It can also help prevent burnout while still improving your skillset.
Final Thoughts
Developer burnout is a serious issue, affecting both newcomers and experienced professionals.
The rapidly evolving tech landscape, coupled with high expectations and personal pressure, can be overwhelming.
Creating a supportive environment, using empathy in our feedback to other developers, and prioritizing our own well-being can help with reducing burnout.
It is important to continually learn in this industry, but do what works for you. Learn at a pace that ensures you remain in a good space.
What that pace looks likes will differ from person to person, what's right for someone else doesn't mean its right for you.
You are more beneficial to both your employer and your family if you are mentally and physically feeling 100%.
If you are struggling, talk to someone about it.
A fellow developer who you trust, your manager at work if you have a good rapport with them.
Someone who might have experienced a similar problem and worked through it. They may be able to offer you good advice and insights to help you get back on your feet again.
Top comments (0)