As a software developer, I know firsthand the allure of diving deep into the technicalities of creating complex applications. But it’s important not to get lost in the code. Some of the best career advice I can give other developers is that they should learn to look beyond the code they’re writing.

Getting Lost in Code

I still remember my early days of programming, when I was so excited to learn about all the latest tools and techniques. I spent hours studying code and trying out new frameworks. That was an incredibly valuable learning experience for me.

However, as I gained more experience and my projects became more complex, like creating big .NET backends and sophisticated React front-ends, I found that getting caught up in the technical details wasn’t always helpful.

It wasn’t that technical details weren’t interesting. They were! Maybe too interesting.

But getting getting caught up in technical details meant I didn’t always keep the end goal in sight. I would get lost in the code and lose track of what I was trying to accomplish.

Remember Your Users

This same dynamic can play out in development teams, whether at startups or larger companies. Developers often get caught up in debates about the minute differences between frameworks or the latest and greatest tools, rather than focusing on the needs of their users.

It’s important we ensure our work is technically sound, but it’s also crucial to remember we’re creating products and services for real people.

Coding for its own sake can get boring after a while. The real joy comes from making things that other people use and love. That’s why it’s so important for developers to keep their eye on the prize and think about the bigger picture.

Solving problems in a performant, scalable, and maintainable way is still important, but it’s also crucial to consider the needs of our users and how our work fits into the overall goals of our team, our company, and our users.

Why I Like DevRel

Focusing on awesome user outcomes and not just code is why I’ve gravitated toward DevRel and DevEx engineering over the past few years. In these roles, I still get to write as much code as I want to, and I still get to work on product features.

But I also spend a lot of time connecting with the developers who use the product. It’s incredibly rewarding to see how my work helps to create tools that developers love, and then helps the developer community discover and learn how to use those tools.

The post Don’t Get Lost in the Code appeared first on Ryan Peden.

A new soon-to-be Computer Science grad mentioned that the found the thread depressing. They seemed to feel like they’d made a mistake and had a bleak future ahead of them.

What should you do?

To anyone feeling the same way, here’s what I’d advise:

Keep in mind that no matter what career you’re in, there are both good workplaces and terrible ones. Before becoming a developer 10 years ago, I worked in corporate accounting and it was the same there.

The best advice I’ve ever been given was to scrimp and save and set aside 6 months of living expenses if you can. That gives you the ability to play a bit of hardball when it comes to asking for improvements to bad work environments because it’s easier for you to walk if you don’t get what you’re asking for.

I’m fortunate to work at a place now where playing hardball like that isn’t necessary. People are nice. The work is interesting. The schedules are reasonable. And I’m pretty sure I’m not the only one who has ended up in a great workplace.

So as a new grad, try not to feel depressed. Just remember that there are good workplaces and bad ones. Sure, software development can be stressful at times. But I’d be worried if I were in a career where I never feel stressed at all, because that would mean I’m probably not being pushed or challenged professionally. And lack of challenge quickly leads to boredom.

The post Is Software Development a Stressful Career? appeared first on Ryan Peden.