this post was submitted on 24 Feb 2024
130 points (95.1% liked)

Programming

17313 readers
383 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
 

I could use some honest advice from experienced programmers and engineers.

I'm almost at the two year mark as a developer. On paper I might look like a passable Junior Dev, but if you sat me down and asked me about algorithms or anything else I did to get my job in the first place I would be clueless. I can solve problems and always get my work done, but I don't even know the language/framework I use daily well enough to explain what's going on, I can just do things. I don't think I have imposter syndrome, I think I really might have let any skill I had atrophy.

I used to enjoy programming as a hobby in my spare time, but in two years I've opened the IDE on my personal machine no more than twice. People talk about all the side projects they have, but I have none. I feel too stressed out from the job to do any programming outside of work, even though I love it. I feel like I can't level up from a Junior to Senior because I either don't have the headspace or the will to do so. It doesn't help that the job I've had has taught me very little and my dev team has been a shitshow from the beginning.

At the moment I have an offer on the table to do a job that isn't engineering (but still tech) and it surprisingly pays more. Part of me thinks I should take that job, rediscover my passion in my spare time and build my skills, but I fear I might go down this route and never be able to come back to engineering. Not that I'm sure I want to.

It might sound defeatist but I don't think I'll ever be a top 5% or even 25% engineer. I could be average with a lot of work, but not great. I could potentially be great in the new field I'm being recruited for, but that's also hard to say without being in the job.

I know that some people just aren't cut out for being engineers. Maybe I have the aptitude but not the mentality to do this for 30+ years. I want to know if that's what it sounds like to people who've seen that before. If you were in my position, would you walk away and just be a hobbyist programmer or stick it out and hope to be a mediocre engineer one day?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] IGuessThisIsMyName 21 points 9 months ago (1 children)

Some people are passionate about their jobs and some people just do it as a means to an end. There is nothing wrong with being in the later group and I say that as someone with ~20 years in the software space and never opens an ide at home.

I've always thought the best way to kill a hobby was to turn it into a job. I won't speak to if you should or shouldn't change roles, there are a huge amount of factors to consider there, I'll just say that not everyone who is successful in development is a guru, ninja, in it for the love, kind of person.

[โ€“] [email protected] 2 points 9 months ago

I've always thought the best way to kill a hobby was to turn it into a job.

100%

I tried turning my hobby of programming into my job. On the surface, I was reasonably successful, but the most enjoyable aspects of my hobby had to be set aside in favour of actual productivity.

Worse, the fact that I actually got pleasure from my work left me open to exploitation. When I finally woke up to that, I ditched programming in favour of "just a job" that paid the bills and was about a million times happier as a result. It's only recently, 15 years after leaving the field, that I find myself once again drawn back to programming.