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

Old person programmer checking in.

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.

Don’t sweat it. No one knows how the fuck computers work.

Anyone who thinks they actually know, isnt educated enough to understand about the bits they don’t understand.

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.

Nice. You’ve got the important part. Ride that until the end.

I don’t think I have imposter syndrome, I think I really might have let any skill I had atrophy.

It’s not impostor syndrome when you’re only 2 years into your career.

If you feel like you don’t know jack shit compared to what I know, after decades… that’s because you don’t know jack shit compared to what I know. There’s nothing wrong with that. Someday I’ll be pissing myself in a nursing home run by automation you maintain. We all get our turn.

I’m the meantime, lucky for you, I can’t be arsed to work more than 40 hours in a week, so there’s plenty of work left to do while you learn.

And I’ll retire soon, and I’l promise I’ll do you a solid and leave decades of my own mistakes and missteps out there for you to earn $$$$ cleaning up after. You’re welcome… I guess.

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.

This is very normal. Welcome to the big leagues. If you do something you love for your job, eventually it’s still just a job.

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.

This is very normal for your current stage of your career.

If you stick with it, it gets better when you get to someday become a self-important slob like me who only works on really interesting problems.

And how do I only work on really interesting problems? I make my boss hire a few junior developers and I delegate all the boring stuff to them.

It’s a pretty sweet deal for at least one of us. (Who for, varies by the day, really.)

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.

I guarantee that you’ve learned way more than you think. If you stick with it, you’ll have a random moment sometime soon when someone else just can’t wrap their head around a concept you take for granted.

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.

That sucks, sorry. There are more shitty developer teams than good ones. If you stick with it, and do some strategic job hopping, you can find the good ones.

This is a tough time to switch jobs in tech, I wouldn’t blame you for not wanting to mess with it.

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.

Hell yes! Fuck your current employer for underpaying you!

And you already admitted your current team is shit.

Go take that money!

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.

Your developer skills won’t vanish. Trust your future self.

If someone asks why you spent time as a non-developer “those assholes weren’t paying a fair wage” is a fine answer.

It might sound defeatist but I don’t think I’ll ever be a top 5% or even 25% engineer.

As a top 5% engineer (with a trophy for humility), it’s not all they promised.

It turns out there’s still plenty I don’t know, and I spend much more of my time confused and frustrated than I did before. The cool part is that I’m now confused and frustrated by really interesting problems.

I could be average with a lot of work, but not great.

I pay top dollar for average programmers. I’m not hiring right now, but let’s stay in touch.

There’s a lot of coders out there without the self awareness to realize what they don’t know. Those programmers never get any better, and never reach average.

(Contrasted with myself, who, as I said, have several awards for excessive humility in spite of my undeniable genius. /s)

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.

Go find out!

Beware though, when they find out you can code, they will find a way to add that to your job duties.

I know that some people just aren’t cut out for being engineers.

True. Some people’s ego or laziness blinds them to what they need to learn.

I have a huge ego, and I am deeply lazy, but I occasionally put both in check for just long enough to learn.

Maybe I have the aptitude but not the mentality to do this for 30+ years.

Take it a year at a time. Once in awhile, take out some cash and spread it on the ground and sort of roll in it.

Hopefully you’ve noticed, but while this job is usually a pain in the ass, it also pays really fucking well.

I want to know if that’s what it sounds like to people who’ve seen that before.

I’ve had this conversation with all of my very top people, if that’s any consolation.

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?

If you told my younger self how much money I could make as a mediocre engineer, I would be all over that deal.

I would’ve agonized about the trade-off if I knew I would stop loving my hobby, but taken comfort that I would later love it again.

Everything happens in seasons. Some seasons I code for fun. Some I don’t.

A cool side effect of being paid to code is that when I do find the mind space to hobby code, I am a fucking badass hobby coder.

I think you should take this job because your current employer is running a shitty team, and underpaying you. Then take another programming job later when the next opportunity arrives (and it will…it really will.)

Gonna be the 100th person to chime in:

Hobby dev with a different main profession for 20 yrs here. Its the same everywhere, in any profession. I know, I‘ve had a couple.

In a bad environment, you‘ll never flourish. You wont even know your actual strengths. Please quit, try something else. Not necessarily a different profession but definitely a different team/company.

Most of what you mentioned tells me that you‘re currently in a bad place. If the team is bad, everything else gets spoiled. Sadly, you need experience to tell the difference. It might be great for someone else even, just not for you.

What you could use is some hard evidence to your strengths, your passions and your specific personality. Most likely this is achieved by taking a break. Either a long nice vacation or moving on. But time off is very important. Reflection is the key and it needs time and space.

All the best and dont worry about not being enough or doing badly. You‘re doing allright.

You have imposter syndrome so bad you don’t even think you’re a real imposter!

I’ve been a developer for about 15 years.

Nothing you’ve said makes me feel like you should quit.
Wanting more money is a perfectly respectable reason to want to quit, and if you think it would make you happier, go for it. Get paid.

It’s not better to be an engineer or anything. No one will mind or hold it against you if you come back and say that you were a jr dev, took a position as otherntech job, but it wasn’t for you so now your back with a new perspective and set of experiences.

Programming was once my passion. I got a lot of joy from it. I still do, and I would say that it still is a passion. But I’ve stopped really doing side projects unless it’s particularly interesting. There’s more to life than career development, and that’s okay.

Without seeing your code, I can’t know how good you actually are. Like most people, you’re probably average. Don’t beat yourself up over not knowing algorithms. No one knows those, they know the keywords and how to describe a problem and then how to pick the right one or tweak something to make it right.

The road from jr to senior is also less about technical proficiency than you would expect.
Technical competency is a must, but you’ll go further as a competent technical leader who can breakdown work, describe it, and help their teammates than as a lone high performer.

Knowing nothing else about you or the new job offer, it makes sense to take the offer. But I’d rather know more than the information you’ve presented. The good news is that you do know more and can better determine if there are mitigating circumstances that make turning down the offer make more sense.

In my opinion you should take the opportunity and check if you will like this new job. And mind you in a lot of jobs there is room for some programming to automate some processes internally in the company if you feel like it.

But it is great that you acknowledge your weaknesses and accept them. I am also leading a team of sw devs and have a couple of juniors in my team and I try to dedicate enough time to them to explain to them more complex topics, give them recommendations on how to write better and more maintainable code, etc. And I have the feeling your lead isn’t doing much or showing interest in your work, which is a pity and very demotivating because I have been in your shoes before and know exactly the feeling.

And a bit of perspective, I have a guy in my team who is pretty smart and overall a great Dev, the problem is that it is extremely difficult to work with him, he doesn’t have a high working culture, thinks that others are stupid and doesn’t do his job well. I know how much he can but it is really a pain to work with him. Believe me I tried a lot of different approaches with him to make it work and so far with mixed results.

On the other hand I have a junior in my team who isn’t the best programmer and I believe he will never be, but he is very positive, works hard, really tries and in general has a very high work culture and it is so much more enjoyable to work with him, so you realise that skills and brain capacity aren’t everything and that sometimes work attitude is way more important.

I wish you all the best in your new endeavour and I hope you feel happier soon.

You honestly sound like your stressed out and in fight/flight mode. The first step is just acknowledging where you are mentally and how it’s going to make everything seem worse than it really is.

Over the 16 years since graduating, I learned that defining yourself by your career is often a trap. At least it doesn’t sound like you’re getting deep satisfaction from your work.

I burnt myself pretty bad going into the field thinking I was perusing a passion career and just kept getting kicked down for 5 years chasing a passion career until I found a work environment that paid decent and valued work/home life balance. In school I thought I’d never sell my soul, but now I’ve been working with the same people for a decade now and pretty happy about it, even with if the actual work is utterly boring.

Unless you’re a fortunate few that are truly passionate, driven, and lucky enough to land a career that fills your entire bucket, look for a job you can tolerate BUT with group of people that support you and your growth. In the end 2 years in is a drop in the bucket and you’ll see your career change directions over and over. You can always learn new skills or relearn them, so if this new job is something different to get you out of a slump, I say go for it. No one can answer for yourself but you.

I haven’t used big 0 or algorithms in my 15 years of professional coding. It’s just not important unless you work for a Google and even then you’d have support.

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.

I am called a srnior developer and I haven’t done a project in my spare time in many years. Not because I don’t want to, but because I do enough of that at work and I lack the energy. Most people I know are in the same boat.

A couple of questions that may help you better understand your own potential;

• Do you have any fun at work? And if so, is it due to the work or your colleagues?
• Does your job keep you up at night? And if so, in a good or bad way (e.g. stressful)
• Do you still have the feeling you could program as a hobby if you weren’t stressed as balls?
• Do you have any mentors/coaches/seniors that help you overcome times when you’re stuck/don’t know where to move?

Most engineers are in the bottom 80% btw, and a lot do valuable work (albeit slow, and not ‘bugfree’). These people are generally most effective when supporting a senior that is in the top 10%.

Also the engineering market is currently pretty shit, and it’s not looking to get better any time soon.

What ever choice you make, try to do something that ‘energizes’ you.

I also think it’s probably a good idea to try out the new career path. Doing software dev as a job, and doing it as a hobby because you like to, are very different when it comes to motivations and goals. Don’t think of it as walking away and just being a lowly hobby dev though, you can build your skills and work on what you want to as a hobby, for the problems you are trying to solve and things you like to work on, and that’s totally ok.

Not everyone wants to put in the effort to play guitar for a living, but you can definitely still enjoy guitar.

As someone who switched from another domain to tech, I suggest trying to reason through your hesitation to switch away. Do you want to stay in tech because you like tech or because you’re afraid of “giving up”?

In my other domain, I worked hard and did OK, but not stellar. In tech however, it’s a completely different story. The other domain was “cool”, and I don’t regret what I learned along the way, but tech clearly comes easier to me compared to someone doing well in the other domain.

You need to be honest with yourself before you make the decision to switch. Are you running away from tech or towards something else?

Having done this for about 25 years, I’ve noticed that conceptual knowledge and getting work done are very different things. Everyone, and I mean everyone, gets stuck when they’re developing. The people who become best at it are the ones that don’t get discouraged about getting stuck, and just keep banging away. Everything is getting more complex all the time. The people who claim to know it all are full of shit.

The real question is this: Do you wake up in the morning energized about solving that problem you went to bed stuck on? Or does it fill you with dread? If it’s the former, keep banging away. If it’s the latter, no job is worth sacrificing your health.