I liked programming a lot, but with AI and how my company is basically requiring us to use it for AI-first development I’m not enjoying my job anymore…

It feels like forced effort on my part to write design documentation and refine it so the LLM does it the way I want and having to review the prompt continuously opposed to actually solving problems the way I would. Plus things aren’t even supposed to be reviewed until an AI review of the AI code is done… I just feel like I’m supposed to be a rubber stamp on the output. They say that dev/review skills won’t atrophy because you’re always reviewing the code, but I can’t accept that conclusion. I became a better developer by actually problem solving, not reading code to see if it makes sense. It’s all about getting more done and trusting it at a conceptual level now, but not really understanding what’s really going on underneath the AI-gen docs because it’s “so much better than human-generated code”.

I don’t understand or really handle that approach well. I don’t really program outside of work because I want to just hang out with my family after it and it feels like a chore to do my job anymore. I just don’t know how to make myself enjoy that type of workflow they are trying to force onto everyone. Any ideas on how to find something to enjoy with that?

  • TrumpetX@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    28 seconds ago

    Don’t use AI sometimes, code it all from scratch like the good old days. You’ll be surprised how your AI usage gets better, and your skills and the “itch” get fed.

    That, or make plans to start raising alpacas in Montana.

  • GreenKnight23@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    43 minutes ago

    after shift hours have ended for me I walk away from most tech.

    I don’t want anything to do with it anymore.

    IDGAF if my skills atrophy. one side is telling me my job will be replaced while the other is telling me my job is going to change. either way I really don’t fucking care anymore.

    let it all rot.

  • Taleya@aussie.zone
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 hour ago

    Yeah hubs has found he misses the problem /planning shower thinking habits he developed over the years.

    He’s decided to learn welding to fill the gap

  • Hetare King@piefed.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 hours ago

    Do you have any hobbies? I get that after work you’d rather spend time with your family than do more work, but if there’s anything else you’re already spending your free time on, it might be possible to combine it with programming in some way. If it’s in service of a hobby and more light and casual than full-on software development, it may not feel like work. And depending on what it is, it could even be part of something you do with your family.

    For example, if you’re into making things with 3D printing or laser cutting, you could make designs in something like OpenSCAD. Or if you like making music digitally, there are DAW plugins that allow you to do digital signal processing with code and synthesise unique sounds that way.

  • Supercrunchy@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    13 hours ago

    Personally, I took some additional unemployment insurance and I’m waiting to be fired when the whole economy will crash (stocks are too high IMHO). I’m only hoping it’s not going to happen for a few months because I’m still in the waiting for the insurance to kick in.

    When everything falls down I’ll go back to study, and hopefully it’s going to be a bit clearer what jobs are more AI-safe and what are not. I’m counting on some specialized and highly skilled but manual work being still there, otherwise I’ll move to a cheaper country and try to live cheaply on my savings for a bit, while the situation settles more.

    Skill atrophy is real. I struggled more than I thought when I tired to code again for fun after a few months of using only AI. Turns out that reading code is very different than writing it, and you don’t excercise your coding muscles if you only read.

    If you think you can slow down a little bit on the job, try coding by hand the hard part of the problem, then when you reach the boring part, delegate everything to the AI and tell it to rewrite and sloppify it up, fix any bug, hiding the fact that you actually coded it by hand. If you have an AI-pilled boss like me you can’t do that in the office though (IMHO it’s pretty visible that you are writing code instead of prompts).

  • Lettuce eat lettuce@lemmy.ml
    link
    fedilink
    arrow-up
    15
    ·
    17 hours ago

    Now that you don’t get to write code by hand in your day job, doing that might become novel again.

    I’ve been considering getting an Arduino and building a little outdoor solar weather station or something. All handcrafted, Amish code.

  • melfie@lemmy.zip
    link
    fedilink
    arrow-up
    27
    ·
    1 day ago

    I’ve been a software engineer for a couple decades and was largely disillusioned before AI, but interestingly enough, LLMs pushed me towards what I consider a healthier relationship with work where I can more easily disconnect my emotions and pump out whatever is required to earn a paycheck.

    After previously pouring my heart and soul into my work and then seeing my company get acquired by big tech, my team’s creations get enshittified, and most of my previous co-workers get laid off, this craving for “ownership” in my work I once had is gone. It has been replaced with an understanding that when you’re working for a company, you don’t own or ultimately control anything there, and you can and will be laid off at any time if it will make number go up. You are simply exchanging time for money. If companies want to pay good money for people to use LLMs to pump out drivel, then fine. Personally, I’ll reserve my best, most inspired work for my own time, thank you very much.

      • 123@programming.dev
        link
        fedilink
        arrow-up
        3
        ·
        14 hours ago

        True, but there is some enjoyment to be had if done correctly.

        I wouldn’t do the things I do at work on my free time, but funding the root cause of some issue or a way to optimize code can sometimes trigger the same parts of the brain that are used when solving puzzles or solving a mystery.

  • one_old_coder@piefed.social
    link
    fedilink
    English
    arrow-up
    56
    ·
    1 day ago

    dev/review skills won’t atrophy because you’re always reviewing the code

    That’s bullshit and the biggest lie.

    When I read my first programming book (I was 15 or something), I was too anxious to compile the code and see the results (lots of psychological reasons for that). I read the whole book and in the end I said to myself “wow, I read and understood everything, I know how to program.” Well, I learned absolutely nothing because you only learn from doing the stuff and making mistakes. There is no shortcut.

    What I do now is learn the weirdest technologies, it’s fun like it was in the good old days. For example: https://100r.co/site/uxn.html

    As long as you know object-oriented programming, you can be an expert in C++, C#, and Java at the same time. It can become pretty boring, even more if they force you to use LLMs.

  • lntl@lemmy.sdf.org
    link
    fedilink
    arrow-up
    52
    arrow-down
    3
    ·
    1 day ago

    when the US outsourced manufacturing, its domestic technical skill base (machinists, welders, etc) atrophied. Today, some are attempting to redevelop these skills and it may take a decade minimum.

    Its a cautionary tale. I would say try to hang on until the AI bubble bursts and then advocate for keeping a healthy domestic skillbase

    • iamtherealwalrus@lemmy.world
      link
      fedilink
      arrow-up
      18
      arrow-down
      5
      ·
      1 day ago

      I used to say that for a long time. But I am starting to doubt it’s gonna burst. I mean the valuations are probably way too high, but we’re never going to put the cat back in the bag. Programming is changed forever with AI. I’ve been a programmer for 25 years professionally and I am working on integrating AI in my daily work routine. I see it this way: We’ve had tools for decades that helped us write code. When ReSharper was introduced many years ago it was able to speed up writing code for all .NET programmers by suggesting snippets of code or performing large refactoring for you. Obviously AI is a whole other level, but it’s still just a tool.

      • Serinus@lemmy.world
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        1 day ago

        I was never particularly proud of how much Stack Overflow I had memorized anyway. That wasn’t the fun part of my job.

        Most of these companies pushing AI so they can show half their devs the door are insane. You can’t just vibe code shit and expect results other than a full airline ground stop and Microslop Office being down worldwide.

        The AI is pretty worthless without me. I have zero concerns about being replaced by a project manager. Companies are being sold something else, but they’re gonna figure it out pretty quickly. (Though not quickly enough for some of us. Negotiate to keep your tenure and severance when they bring you back .)

        But AI as a tool is here to stay, and it’s better to build those skills earlier than later. The Riemann hypothesis shows a bit of a model for future work, both good and bad. You can’t just tell AI “solve the Riemann hypothesis”. It would have gotten nowhere without the expert guiding it and using it as a tool. Fortunately most of the stuff we’re doing isn’t cutting edge research, so hopefully we don’t have to deal with a pile of slop that we can prove is correct, but nobody understands how.

          • rwdf@lemmy.world
            link
            fedilink
            arrow-up
            3
            ·
            11 hours ago

            Use it to fill in the blanks or draw by numbers. Set up your own scaffolding or better yet, a model implementation. Have the model define skills and guidelines based on what you have already programmed. Then use the AI to write new implementations of similar things. See what it can and can’t do. See where it goes off the rails and watch it introduce unnecessary complexity every time the instructions are ambiguous/imprecise.

            Using AI with carte blanche on a greenfield project without any preexisting docs, architecture definitions, established code quality and style guides, etc is a recipe for disaster.

          • Beej Jorgensen@lemmy.sdf.org
            link
            fedilink
            arrow-up
            5
            ·
            1 day ago

            A couple ideas here:

            • Keep coding your own stuff on the side.
            • Don’t let the AI give you code that you don’t understand.
            • Understand the greater architecture of what it’s building.
            • Be specific in your instructions.

            Yesterday I was using Copilot and Claude to write a clone of the old trn Usenet newsreader in Rust. Got pretty far in about 7 hours. 8300 lines of code and 8300 words of design docs in Markdown. The architecture is pretty good, and the thing works. (Still missing is the thread graph display and posting, but I know those can be added without breaking anything.)

            Don’t get me wrong: if there were a button that destroyed LLMs forever, I’d have already pressed it. I have other projects that I write by hand even though LLMs could definitely do it because I like the challenge and I want to stay sharp. Reading code doesn’t do it.

          • Serinus@lemmy.world
            link
            fedilink
            arrow-up
            5
            ·
            1 day ago

            Yeah, I don’t have a good answer for that. I’ve seen how easy it is to get lazy and just vibe with whatever it’s putting out, in others and myself (sometimes).

            The worst is when it’s clearly not working and the person just spins the AI in circles with “well, fix it” over and over again.

            I do think we have a history of looking for black and white answers that has bitten us in the ass. “Not invented here syndrome” led to the npm dependency hell, for example. There’s a middle ground. log4net and whatnot are great third party tools that should absolutely not be reinvented yourself. But maybe you should have handled Leftpad on your own.

            • Supercrunchy@programming.dev
              link
              fedilink
              arrow-up
              1
              ·
              12 hours ago

              The worst is when someone hands you some code or some document or reccomendation and they can’t answer any question about it, because they haven’t even read what they sent you. It just infuriates me beyond anything.

              I fully lost confidence in some of my colleagues that way. I feel they can’t think by themselves anymore. Like why do they think someone would pay them to just fully delegate the tasks to claude? Do I look so stupid that I can’t ask claude for the same thing? At least I can ask claude why it did some of the choices and get an half-correct answer back, unlike them.

              Why am I doing a code review if you didn’t bother even reading your own fucking PR???

              </rant>

    • chonglibloodsport@lemmy.world
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      1 day ago

      A lot of those skills won’t come back or they’ll be more specialized.

      My friend works in auto manufacturing. He welds truck frames. Except he doesn’t weld by hand at all, he uses robots to do all the welding. He can supervise a whole team of robots and adjust them to deal with flaws as well as set them up for new jobs. As one person he replaces a whole team of welders.

      Now don’t get me wrong, there still are lots of manual welding jobs out there, but a lot of them are specialized into custom work or in complicated scenarios (underwater dive welding on oil rigs). The standard manufacturing line job where you perform the same welds over and over again is a thing of the past.

      • rogerdodger@lemmy.world
        link
        fedilink
        arrow-up
        11
        arrow-down
        1
        ·
        1 day ago

        Welding a frame is a repetitive task, and the robots are deterministic. Programing is not repetitive, every problem is different and takes creativity, and LLMs are not deterministic.

  • MercuryGenisus@lemmy.world
    link
    fedilink
    arrow-up
    28
    ·
    1 day ago

    I just let the AI do the work code while I fiddle around with personal or vanity projects. You doing actually need to sit there and watch it work. Just baby sit it as needed and understand that your labor and your passion will never be the same thing, and that’s okay. We used to sell one for the other. Now you can just do both.

    • plant@lemmy.stinky.rip
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 day ago

      This is where I’ve settled too. Now I just hack on my homelab and largely don’t use any LLMs when doing so to prevent the brain atrophy from setting in and accept that (for now) it’s pretty cool I’m getting paid to basically read the output of an agent’s plan and execution.

  • it_depends_man@lemmy.world
    link
    fedilink
    arrow-up
    30
    arrow-down
    1
    ·
    1 day ago

    I don’t really program outside of work

    Until that changes, there is nothing you can do and I have no advice.

    Your problem is with your company, company culture and your boss. Not that much with coding.

    • prettybunnys@piefed.social
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 day ago

      The biggest issue is that the people in a position to influence hiring are also the people who are having AI touted as a way to lower their hiring costs.

      So it’s rare you have people with enough power to push back AND care or want to.

      I hates it.

  • entwine@programming.dev
    link
    fedilink
    arrow-up
    25
    ·
    1 day ago

    Unrealistic but fun ideas:

    • unionize
    • Collect/learn as much as possible about your employer’s/customer’s industries, client relationships, etc and start your own business stealing their customers
    • Outsource your own job to some contractor for a fraction of the pay, so you don’t actually need to work
    • Sabotage by using as many tokens as possible to burn through budgets, massage prompts/agents to be as verbose as possible, poison long prompts, etc
    • Find a new job

    Whatever you do, don’t let the cognitive decline set in.

  • 4am@lemmy.zip
    link
    fedilink
    arrow-up
    15
    arrow-down
    3
    ·
    1 day ago

    We should be writing the code and the AI should be writing the tests and documentation.

    If I wanted to be a technical writer or a tester; I would have been.

    Sorry to all the technical writers and testers out there. AI sucks.

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        12 hours ago

        Yeah 6 months ago maybe. It can write perfectly good tests now.

        I actually find the more common failure mode is it finds something that doesn’t quite work right (like a bug in a third party component) and it just silently works around it rather than telling you so you can get it fixed. My suspicion is they benchmaxxing makes them try to make as much progress as possible so they’ll do lots of workarounds rather than asking you.

        Another example is when it’s building Rust code for me, it will use a crate that is pulled in as a transitive dependency even if it actually wanted a different one, because it’s sandboxed and doesn’t want to bother me by asking me to run cargo fetch. Quite annoying.

        It doesn’t write vacuous tests though.

        • wewbull@feddit.uk
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          Yeah 6 months ago maybe. It can write perfectly good tests now

          How are you measuring how good the test is? How do you know it’s a good test?

          I actually find the more common failure mode is it finds something that doesn’t quite work right (like a bug in a third party component) and it just silently works around it rather than telling you so you can get it fixed.

          Why do you think the tests aren’t doing the same thing?

          • FizzyOrange@programming.dev
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            4 hours ago

            How are you measuring how good the test is? How do you know it’s a good test?

            I skim them.

            Why do you think the tests aren’t doing the same thing?

            What you mean like it find a bug and it just writes the test to confirm that the bug exists? In my experience Opus 5.5 will do that but only in an “expect failure” kind of way, to confirm the bug is really there, and it tells you about it.

            Opus 5.5 employs much more rigorous development practices than most humans developers. It isn’t lazy so it will do things like confirming that regression tests detect the bug before it is fixed.

            It’s a huge step up from earlier models, where I would have agreed with all your concerns. Honestly the downvotes and questions along these lines feel a little like someone seeing a train for the first time and asking “but how does it know which way to go?”. Just try vibe coding some Rust with Opus 5.5. It literally costs £18. You can see for yourself.

            • wewbull@feddit.uk
              link
              fedilink
              English
              arrow-up
              1
              ·
              4 hours ago

              No, I’m suggesting it can write a test that avoids the bug because it’s seen the bug. It’s a goal orientated system where the goal is making the tests go green. Sometimes the shortest path is the deceptive one.

              I’ve seen people do it because they didn’t know how to fix a problem. Why should I trust Claude?

    • Jo Miran@lemmy.ml
      link
      fedilink
      arrow-up
      6
      ·
      1 day ago

      This is exactly how I use it. It does all the code comments, and documentation. I built it a lab on three old laptops (linux, mac and win), and one “powerful” (retired gaming pc) linux system. It builds the environments and tests the living shit out of everything, documenting everything along the way.

      Unfortunately, most people and companies aren’t trying to use it to better the quality of their output, they are trying to increase the speed and quantity of their output.