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?

  • MajorHavoc@programming.dev
    link
    fedilink
    arrow-up
    10
    ·
    edit-2
    7 months ago

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

    Old man 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.)

    • tkohldesac@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      10 months ago

      Not to hijack from the OP, but would you change your reply if someone was feeling similarly but wasn’t yet in their first role yet? I’m coming out of 2 years of private mentorship and have spent the last almost 3 months applying with barely a whisper of a reply from a fraction of these jobs so I’m a bit down on myself. I felt confident a month ago but now I’m slinking back applying to jobs in my old industry.

      • Odelay42@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        it’s a bad time to be looking for work in tech.

        Be patient, keep your head up. Keep applying. You’ll get something soon.

        Sorry you’re seeking in a down market. It happens every now and again in this industry. You’ll get through the eventually.

  • muhanga@programming.dev
    link
    fedilink
    arrow-up
    6
    ·
    10 months ago

    Tldr; take offer, don’t quit engineering yet, you are fine

    Don’t quit engineering if you enjoy it. If you have better offer and the current ship is leaky as fuck => jump the ship. Saving the leaky ships should be very profitable if it is not => you are being heavily exploited.

    I jumped the ship thrice. And one time accepted a lower payed position, just because I was quite burnout.

    On the topic not using the progress and not understanding the Intenals. Understanding internal will not make you senior. Understanding what you can apply that you already know can make you senior. I remember being in a situation like yours. I thought I didn’t know Jack, but then on a newplace I seen people who were running around like a headless chickens on crack. This has given me a good understanding about what knowledge is and that applicable knowledge is the key.

  • friend_of_satan@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    10 months ago

    I say take the job that pays more and rediscovery your joy. The world needs more people who understand how to code but do something other than code as their full time job.

    • jkrtn@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      Simply being aware they’re not in the top 5% probably places them well within the top 25%.

  • helpImTrappedOnline@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    10 months ago

    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.

    Solving problems and getting a result that someone else is happy with is 90% of engineering. No one knows everything, your job is to use what you DO know to figure something new out.

    The last 10% is what you need to work on - being able to confidently explain to a boss what you do in way that they understand while sounding complex enough to justify your pay and subsequent raises.

    In time you will learn whatever system your using.

    However, on the flip side, if the current job isn’t getting you anywhere and everyone there sucks. Leave, take the better paying job for a little while, continue working on your skills and look for a engineering job elsewhere.

  • iawia@feddit.nl
    link
    fedilink
    arrow-up
    3
    ·
    10 months ago

    Don’t confuse a bad work environment with not liking or being suitable for your job.

    If you liked programming, do your work in the way that made you originally liked programming. People will put pressure on you to just “do things”. Don’t. Ensure you start understanding, slowly get more insight into what’s going on. Ask the people around you any and all questions you need to get more understanding. Allow yourself to learn. That is the only way to start feeling in control, and the only way to become ‘more senior’.

    That being said. If you want to move on, there’s no harm, and no shame. Just do it because you’ll be doing something you know you will like better.

  • haui@lemmy.giftedmc.com
    link
    fedilink
    arrow-up
    2
    ·
    10 months ago

    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.

  • trolololol@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    10 months ago

    Mate Im writing this after reading the top half of your comment.

    This is a normal path, and the insecurities are going to stay with you for a long time even after growing into sr

    If you’re not passionate that could be either in you or on your job, and the best way to see is if you search for other jobs and that excites you. So give yourself a chance and look what companies around you or far from you are doing.

  • IGuessThisIsMyName@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    10 months ago

    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.

  • 0485@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    10 months ago

    I’m sort of the same as you.

    I took a 6 bootcamp, got a job straight away after as a full stack junior web developer.

    Programming as a job was the single worst decision I make. I was working with languages and frameworks I don’t enjoy, I was building a product I don’t care about in the slightest.

    It took me 1 year of full time web dev before I quit and went back to regular IT which isn’t the most fun thing, but it works for me. I’ve been doing it for over a decade so I can do it in my sleep, it’s easy money tbh. Programming for me is definitely more of a hobby than a job. Having it as a job really killed my love for it

    Nowadays I only code in Python which I LOVE. I use my programming skills to automate work tasks, and I make small scripts here and there and it’s so much fun.

    Solving small problems with scripts is just what I enjoy doing. I get to work on a project for a day or two. I can complete it fast then move on to something else.

    Now I’m about transitioning into Data Engineering instead of Software Development.

  • nhu@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    I personally work for more than 20 years as dev and really hate to see myself as senior. I think I am more of a Veteran. I only have more practice and survived more projects. What I am trying to say is, give yourself time. Nobody starts out and knows everything. And even if you have experience, there is always a bigger fish. Simply because the topics are too complex to know them all.

  • ursakhiin@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    As a senior engineer recently turned manager I hear this type of mentality from most of my junior all the way up to senior devs.

    The only thing I’d suggest to you is spend some time digging into the tools you’re building outside of the project you’re working on. Just to get a general understanding of how the pieces fit together. Definitely do it during work hours, though. I’m in no way suggesting outside of work, here. Once you’ve spent enough time digging, you’ll surprise yourself in how effective you get at answering questions.

  • monkeyman512@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    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.