Comment by barbazoo

10 hours ago

> Everyone in SWE is experiencing this.

Obviously this is not true for every SWE. A lot of people feel liberated now that the burden of actually writing the code is being replaced by molding it through the interaction with AI. I see people that struggle because they've identified with the writing code part a lot and that's gone now that the machine is doing it, I bet that's hard.

Yes. The people that didn't enjoy coding say that.

AI is great enabler for stuff that you don't want to be good at, it cut a ton of chore type jobs out of my workflow, but for stuff you do want to get better and care for, it's both joy killer, and if you're not careful you will only learn how to prompt, not how the stuff works.

  • I enjoy coding deeply, and my feelings are not that simple.

    I love code as a craft. I love spending time designing the perfect abstraction. I love seeing it come together in the implementation stage. I love the troubleshooting process and the understanding that comes when you finally engage with the root cause of the issue. I love all of this so much that I ship little, all my time is spent in process.

    I also love code as a tool. I love working tirelessly towards describing a goal and then watching it come to completion. I love knowing my projects consume terabytes of data and spit out useful results. I love seeing my assumptions on the outcome proved right or wrong.

    Now I can do the latter without the former, and it leaves me deeply conflicted. A large part of me is more excited than I've ever been. Another part of me is quite sad, and this is unfortunately the part where my ego lives. For now, I keep it in check by asking the LLM to describe the pros/cons of alternative architectures. That way I stay learning about the products I create.

    • As I like to tell others: before my job was 70% architecture & patterns and 30% coding & algorithms. Now my job is 100% architecture & patterns. While I still spend the majority of my time on architecture & patterns, and while I enjoy this aspect more than coding and algorithms, I am still working a "different job" than I was when my hands steered the code completely.

      9 replies →

    • Username checks out and thank you for writing out my own feelings better than I ever could have, even with AI.

  • People are really not as black and white as you are making them out to be. Most coders cared both about writing the code and the end result.

  • > and if you're not careful you will only learn how to prompt, not how the stuff works.

    I’ve been coding over four decades and it is clear to me that most programmers don’t know how the stuff works, and not just script kiddies but some PhDs I worked with.

    For those who want to know how it works, LLMs are massive enablers. I’ve written so many debugging and inspection tools with an LLM; had a model explain the assembly language produced; had rubber duck conversations with it. I’m having such fun tbh.

  • That's a very simplistic view. I'm very good at writing tests and I'm happy to offload writing tests to LLMs, as long as they follow the structure I've provided.

    You're saying that I must not be good in writing tests, irregardless on how I feel about test writing.

People who hated coding, technology, problem solving and only were in it for the money love managing a bunch of agents. Unfortunately, it seems like a lot of them were in technology. I hope agents quickly become good enough to completely commoditize any supposed function they perform, and forces them to leave this industry.

  • This is an extremely “all or nothing” take. I love computers and started programming in elementary school. I am having more fun now building software than I can remember.

    I happen to love the process of building software by coordinating agents. It’s an addictive form of flow state that I enjoy a great deal - similar to the flow state I get playing real time strategy games like Age of Empires. It’s a different kind of flow state than writing code, for sure.

    But to say that the only people who enjoy building software in this new way are those who hated coding, technology, or problem solving is simply untrue.

    • I’m glad you mentioned flow state because that’s exactly the high I’m trying to chase with AI and why I like it despite programming since elementary school as well.

      I realized I most enjoy higher level problem solving but don’t really enjoy implementation. Like I enjoy algorithms, data structures, memory allocation strategies, SIMD optimization, etc. But writing the code, and debugging it is tedious and takes me out of flow.

      And if I’m really interested in the project itself then the algorithms take a back seat and I enjoy the even higher level problem solving of building a cool project.

      I don’t think it makes you lesser to enjoy these things more than literally banging out code, and hunting down bugs. Perhaps I’ve written enough code that I don’t find the same joy in that. Who knows.

  • You can love technology and still have thought that coding was a required path to get to technology and not the ends unto itself.

    If someone loves building technology products that doesn't mean they were "only in it for the money". Beyond just being disparaging for no reason, you're missing the path out of the depression-pit here.

    • It’s not the act of coding, you have to really hate problem solving, to love managing agents. Such people are only in it for the money, it may sound disparaging but it’s just true.

      If tech paid less, say minimum wage, they would all leave and none of them would ever tinker around anything in their free time. I’m not depressed, I’m just disappointed by how many folks are like that in this industry I loved.

      11 replies →

  • That's reductive.

    I love writing code, but I don't love every single part of writing code. In particular, I really disliked getting stuck on some irrelevant detail, some mysterious error that had nothing to do with my code (dep issues, OS quirks, silent changes, auth failures, researching alternatives), and spinning my tires, unable to work on what I wanted to accomplish. Often I never made it through the far side; I've got a project directory littered with half-finished projects.

    Having an AI to figure all that junk out for me so I can focus on the thing I want to build is fantastic. I worry about losing the grip I still have, but for now I've lost some things I loved (a lot of actual code-writing, solving nice straightforward problems), but gained what might as well be superpowers to help with some real shortcomings I had. It's been a net-positive trade for me so far.

    And none of my personal projects have made me rich yet...

  • > People who hated coding, technology, problem solving and only were in it for the money love managing a bunch of agents

    In other words, people who just wanted to become managers.

  • Why did you expand it from what he said? I love technology, I enjoy being able to solve problems with technology and coding. I've always felt neutral about the actual act of coding, it was always just a means to the end and now I love that I can do more problem solving in less time and with less toil (from my view). But I guess I was just in it for the money.

  • I got into software later in life because I wanted to be able to send my kids to college, have healthcare and not destroy my body by 50. Up until my 40s I was a landscaper who had been an amateur programmer and technologist since my teens. I worked really, really hard to get where I am. I went to a bootcamp 5 nights a week for a year after breaking my back all day at my “real job”, while also taking care of a wife and two kids.

    I enjoy what I do but I confess to being “in technology” because I need to earn a living not because it’s some sort of passion project. I think it’s pretty horrible to wish us all out of job so you can feel superior again.

    • It says a lot that you felt the need to recite an emotional sob story to try and attack my comment.

      Regardless, I wish you all lose your jobs to AI and be forced to leave technology and earn money elsewhere. I think it’s been a disaster to the quality of the technology surrounding us and the community that creates technology to have so many opportunists just in it for the money.

  • > People who hated coding, technology, problem solving and only were in it for the money love managing a bunch of agents.

    Why do they have to hate coding, technology and problem solving, that makes no sense. They just use coding agents to write the code for them to use technology and solve problem.

  • FWIW I hate huge chunks of the industry + its inhabitants and am somewhat happy that my GPU can replace a significant amount of interactions with it and them.

    Let's not forget that there is this silver lining of the tech. We can be free[1].

    __

    [1] Requiring a one-time payment of about $200000 + a small gas turbine

  • I love all those things, started coding as a 10 year old(30 years ago).

    The stuff I’m building is things I could only dream of before. With LLMs, I can build things in a year that would have taken me a lifetime before.

> A lot of people feel liberated now that the burden of actually writing the code is being replaced by molding it through the interaction with AI.

I venture to say that this number is small. Most SWEs get into it because they don't view writing code as a "burden".

The people who are "liberated" aren't the SWEs, it's the people higher up the ladder than the SWEs, who can't or don't want to be bothered with coding anymore. For them, managing a fleet of agents is easier than managing a group of SWEs.

  • Most of the code I was paid to write is a burden. I've spent far more hours writing generic CRUD apps, debugging overly complex javascript tooling (almost always out of date) and other tedious grunt work.

    I don't think it's fair to say that all SWEs swing one way or the other. I absolutely love the fact that I will never have to waste time debugging cargo culted, trendy libraries ever again while I am also sad I'll also never to get hand write elegant implementations of interesting problems ever again either (unless for fun).

    I would be happy to keep writing code but I'm also happy to be liberated from the type of code I was often paid to write.

  • For me typing out code was always the annoying part. The fun comes from fixing problems, optimizing for speed, making the UX flow better and visuals look nice, all things that are on the level of software not code.

    Agents help you bang out good code faster if you know how to use them. My relationship to Claude and DeepSeek is somewhere between an IDE, a coworker and a friend (I still have real friends don't worry).

    I don't treat it as a world changing magic wand that fundamentally changes the way everything works. It's more like a fast forward button that lets me skip the boring part in exchange for some hand holding. No more dealing with syntax errors or finding trivial bugs.

    • > For me typing out code was always the annoying part. The fun comes from fixing problems, optimizing for speed, making the UX flow better and visuals look nice, all things that are on the level of software not code.

      This always read like

        Writing sentences was the annoying part. The fun come from sharing ideas, optimizing for brevity, making the rhythm flow better and words more impactful, all things that are on the level of communication, and not grammar.
      

      Then you start wondering about the actual level of education of the person and their claims about writing a nice novel.

      Code is formal writing. Expressing an idea in such formal forms means you have thought exhaustively about the evolution of the algorithm/process. If you’ve not done that, you can’t guarantee the correctness of that algorithm/process. Is it just toying around with an idea of software?

    • sure, it works like that if you're still the one doing the thinking and figuring out how to do things, and just using agents for the boring templating and to translate your pseudocode into syntax-free real code, without you having to look up the arguments for every call that you haven't used recently, etc.

      but most SWEs are being pushed to delegate the _thinking_ to agents.

      so instead of "here's a solution to load this page faster that I came up with: X. Implement this in JS", which is along the lines of what you describe, most people are doing "this page needs to load faster, what's the best way to do that?" claude: "X". "OK, implement X." What fun is that? What's the point of developing skills and acquiring knowledge if you can't use them anymore. that's the loss.

      If all you care about is having pages that load fast, then yeah, agents are great. If you care about being the architect who figured out how to load pages faster, then agents take the wind out of your sails.

Soon enough the clankers will automate that part too. I'm eager to see how "liberated" those people are going to feel then.

  • Totally, I can't quite imagine an AI automating my use of AI tough, how it would infer what prompt I would use at any given time, the problem space is infinite. Am I adding another *arr app to my stack, are we building a SPA, a home automation plugin, whatever. These are things that I want to do and AI helps with that.

    In the corporate setting I think though it won't take a lot of time to reduce the layers and number of people that are required to run a software company. Either one becomes a more general work manager or obsolete I guess.

  • It is remarkable to me how few people seem to understand it is a much smaller step for AI-generated software to kill the need for companies of idea men than it was for them to kill the need for people writing code.

    All of your potential customers are just going to vibecode their own software. In many cases they won't even realize that the software they vibecoded even exists as it will just be an invisible tool the LLM built for itself to reproduce a similar solution to a similar prompt over and over.

    Once AI flattens out any company enough, the company itself no longer needs to exist, it can trivially be replaced by the model providers. Companies exist to be collections of skilled people with a common goal. When you don't need that, you don't need companies. The agents can work for your customer instead of you and nothing changes except who gets paid (not you).

    There's a ton of magical thinking out there where people seem to assume AI will progress right up to the point where it is maximally beneficial to their job without replacing them. Keep huffing that copium, folks.

    • > There's a ton of magical thinking out there where people seem to assume AI will progress right up to the point where it is maximally beneficial to their job without replacing them.

      I've commented previously that there will be much more political interest in AI causing unemployment when the first CEOs are replaced.

      That's going to happen. It's part of the "creative destruction" of capitalism. If AIs maximize shareholder value better than some CEOs, those CEOs are toast. They either get replaced in the same organization, or a new company arises and crushes them.

      2 replies →

    • > There's a ton of magical thinking out there where people seem to assume AI will progress right up to the point where it is maximally beneficial to their job without replacing them. Keep huffing that copium, folks.

      Because you are singularly right about the issue? Have some intellectual modesty, brother.

      1 reply →