DEV Community

Brian Rinaldi
Brian Rinaldi

Posted on • Originally published at

A Developer Career Doesn't Have to Be Linear

I found myself in a rut about 10 years ago. I'd been working as a developer already for some time and I wanted to move forward in my career. However, the only path that I could see was one from developer to team lead to development manager. There is nothing wrong with this path, but it wasn't an appealing one to me.

The truth is, as I've since learned, that just as there is more than one way to become a developer, there are also multiple career paths open to you as your career develops. The key, for me, was to change my own mindset. In this post, I want to share what worked for me in the hopes that it might help those of you for whom the traditional career path for a developer also isn't appealing.

Don't Rely On Your Job to Teach You What You Want to Learn

There are certainly more engaging jobs out there, but the reality is a lot of us do work on little fragments, work that is often tedious and devoid of any kind of creativity. As a developer I’ve often had trouble figuring out if a job would be Snow Crashy or not, and been seduced by promises of engaging work only to find myself ferreting out bugs on some enterprise CMS.
"I just don’t want to be a software developer anymore by Melissa McEwen

The reality is that, while a career as a developer is a great one and the work can often be exciting and challenging, the day-to-day of a traditional developer role can be tedious. Younger me thought this was a problem that my job should solve by offering me more interesting challenges and pushing me forward, and if it couldn't then I needed to find the next job that could. However, the truth was that it was up to me, and realizing this was the biggest revelation for my career.

For instance, if there was some new tool or framework or type of development that I was interested in learning, I needed to find the time to learn it rather than wait for my employer to come up with a reason for me to do so. If you are learning the things you want to learn at work, all the better! But if you cannot, don't let your job stop you.

If you are thinking, "I want to learn X but work won't let me use it," then find a way to learn it outside of work. This doesn't mean you should live and breath code and spend all your free time on side projects, but it does mean that you shouldn't let the needs of your current job limit you - follow your interests and make it happen!

Find Ways to Explore Your Creativity Beyond Code

While it is important to not let your job limit the skills you want to learn when it comes to coding, if you aren't looking to follow a traditional career path, then it is important to explore your creative skills beyond just code. These can help illuminate a different path for you.

To be a good developer you don’t have to spend 99% of your time writing, reading about coding. Do other activities. it helps to be more creative and to enrich your knowledge.

What other activities do you engage in aside coding πŸ€”πŸ€”

β€” Amycruz πŸ‘©β€πŸ’» πŸ‘©β€πŸ’» πŸ‘©β€πŸ’» (@amarachiamaechi) May 24, 2019

For example, I had always loved writing. My college studies were not even in computer science but in areas that focused heavily on writing skills. So I started writing for journals and blogging. Sure, my writing was about coding, but it was allowing me to explore skills and interests that I'd let atrophy somewhat. As it turned out, my alternative career path would be heavily focused on writing, so exploring this skill was the first step in opening up that path.

Whatever your interests are beyond code, explore them. You may think that they are too far unrelated to your job as a developer to be relevant, but you never know where they may lead. Coding skills are relevant in so many creative fields nowadays that you may be surprised what doors this opens up for you.

Don't Take No For an Answer

This follows on the first two tips - don't let yourself be limited. Some of the best things I have done in my career have been when I was told no. Following the things that I was passionate about was a key to changing my career path - and there was no better way to realize I was passionate about something than when someone told me it couldn't be done.

For example, I really wanted to attend some developer conferences. My employer at the time didn't cover attending conferences and I couldn't afford to attend on my own (especially since I'd have to take vacation days to do so). I decided that, since I couldn't leave to attend a conference, I'd start one! That conference sold out nearly all five years I ran it and, in fact, I eventually had to sell it because it helped lead to that career change that I was looking for all along (it still runs under a slightly different name, in fact).

The biggest motivator for me sometimes is just proving people wrong, makes me want to do it 1000x bigger and better just to prove I can

β€” jessie frazelle πŸ‘©πŸΌβ€πŸš€ (@jessfraz) May 26, 2019

That's just one example, but I could list a number more. The point is to follow your passion and don't let it be dictated by other people.

There Are a Lot of Paths You Can Follow!

What I've learned in the ten or so years since that rut I was in is that there are a ton of paths open beyond the traditional one - I just needed to broaden my horizons a bit. There are some more obvious paths such as developer relations, community management, product management, product marketing and even marketing. Many companies see developer skills as something useful beyond the straightforward developer roles.

There are also less obvious paths that many developers I've met have followed, often through paths involving entrepreneurship or even philanthropy (such as starting a non-profit). Honestly, the more developers I talk with, the more amazing stories I come across, and the more I realize that a developer career isn't really like a path but more like a wide open field with countless destinations...I hope you find yours!

Top comments (4)

xanderyzwich profile image
Corey McCarty

I'm currently working with a small group at my company to help forge a path and work with the system given to us to advance from entry level up into the higher positions. As a part of this exercise there are five people in our center and we were each hired as developers. Two of these people have become managers (due largely to an unfilled need), one is working toward Scrum Master, another toward Project Manager, and I'm working toward being an Architect. It was really helpful when we were able to sit down and discuss what the different directions open to us are and that conversation has actually been a tremendous morale boost for each of us that are in that central group. I would like to urge others to do similar exploration as to what roles exist in your company (and others) above your current position that you might be interested in.

remotesynth profile image
Brian Rinaldi

Great advice! Thanks Corey.

daedtech profile image
Erik Dietrich

I really like the tweet that you cited from Amy and your point around it. I think the software development industry inadvertently encourages tunnel vision around the act of writing code itself, leading you to believe that being "good enough" requires single-minded dedication to the "craft" of coding.

But, in reality, that creates diminishing returns, especially once you've been at it a while and learned different languages and paradigms. At that point, I think it's time to branch out into ways to put those automation skills to use.

I personally had a similar experience to yours. I logged a lot of years as a software engineer, and then a few in management. But I liked to train people, to write, and create content. So I pursued those things as well, and it led me opportunistically to training gigs, management consulting, paid writing, and eventually even into content marketing. My participation in all of those things has oriented around software, but the variety has kept me from getting bored, a fate I probably wouldn't have avoided with a second solid decade of nothing but banging out code.

remotesynth profile image
Brian Rinaldi

Thanks for the thoughtful reply. It is tough in an industry where we often look up to people that, at least based on their public profiles, seem to work long hours and then go home and spend their nights and weekends coding side-projects. However, I do feel that this culture is slowly starting to shift.