Coding Agents killed my identity. How do you feel?
Programming is like a game of chess for me: winning (i.e. delivering a product) is important, but only if I played this game myself. I don't enjoy winning if my opponent disconnected. I don't enjoy beating people who don't know how to move pieces. I don't enjoy winning with an engine, and coding agents are basically "winning with a chess engine".
I started to use AI for coding a long time ago, when copilot was first introduced. At first, I was happy: "wow, this can write boring boilerplate and unit tests". Time went by, agents got better, time spent writing code myself went down. Half a year ago I suddenly realized I hadn't written any code for over a month, and I am a full-time software dev without any managing work. Not only did I stop writing code, but agents also became pretty good at proposing plans and architectures, and I was mostly providing missing context and technical details of our infrastructure.
One day the realization hit hard. Coding agents removed everything I loved, and - mostly - amplified everything I hated. My role is to gather context from other humans and provide a detailed explanation (similar to a well-written jira ticket) to some super intelligent engineer, then review the result and provide more context/explanation if needed. So, basically, a manager.
A couple of years ago I could work on a single coding task for weeks. I knew all classes, all functions, I was slowly building up information at a comfortable tempo. Now I am forced to increase my mental throughput multiple times. What took a couple of weeks now takes a couple of hours, and I still need to comprehend that. I always feel tired, I don't have enough mental capacity to hold that many abstractions and technical details. So you either autoaccept or get burned out reviewing tens of thousands of lines.
One more downside is that code has 0 value. You can code your own OS from scratch, and people will think "ye, I can vibe code that in a weekend". I don't even know what is valuable nowadays.
Maybe I am a bad employee. Increasing employer profits was never my goal. I always loved to solve puzzles, and for the last 10 years this was well aligned with my employer's desire to increase profits. I never was good as a manager, or brilliant at generating ideas. My power - and passion - was solving complex technical problems with my hands, fast and with good quality. Now it is gone forever. I feel completely lost and unmotivated. I don't see any value in learning anything related to computer science, reading papers, contributing to open source. I hate my new "AI delegator" role and I hate my work. I loved coding so much (I use neovim btw) that I was sure I would do this until I die, and now I don't know what to do with my life. This is the only thing I know, and, most importantly, the only thing I am/was passionate about. Anyone else feeling the same?
36 comments
[ 3.4 ms ] story [ 61.7 ms ] threadYou are not wrong to have your feelings or to strongly identify your sense of self with your work; that is what we used to call a vocation.
I share your feelings and have been focusing my energy on learning local AI because it seems to be impossible to avoid AI entirely.
But focusing on how you feel first, and then hopefully thinking about other ways you can feel valuable is not wrong. You are not alone.
I'm always curious, what are those "great things" requiring deep technical knowledge and years of expertise that these visionaries can finally provide with the help of LLMs?
I almost feel ashamed/mentally ill when i am reading how everyone is happy that their true visionnaire potential is finally unlocked while i just like to solve my silly puzzles.
Everything has, in fact, changed, and it is a task for those of us who cared about what was, to try to work out what is worth caring about.
As Annie Savoy says in Bull Durham, “the world is made for those who aren’t cursed with self-awareness”. You’re going to have to figure out new things to care about, but you can do it, because you found it the first time!
In reality, it’s probably closer to 1/100 of the people who claim they do. If genuinely love the craft, LLMs should be exciting. Imagine having an LLM to discuss ideas with, learn from, and use to expand your skills when we were learning stuff. Nothing stops anyone from coding for fun, learning new languages or frameworks, or exploring new design approaches.
The uncomfortable truth is that many who say they “love the craft”, loved probably more what came with mastering it... The salary, status, career prospects, and identity of being “the smart guy” with a rare and valuable skill. When that identity feels threatened, the reaction is understandable. But you know who really loves the craft? Amateurs. In the original sense of the word. People who pursue something simply because they love doing it.
ps. I believe companies will need knowledgeable engineers to drive the machine. LLMs are right most of the time, but not always, and someone still needs to know enough to catch the mistakes and, more importantly, specify what should be built in the first place. You can’t write a good spec without understanding the language of the system you’re specifying, the system itself, etc.
And there’s an entire ecosystem emerging around LLM engineering growing fast: infrastructure, inference optimization, model evaluation, token efficiency proxies, tooling, and more. Even setting up a solid development environment has become quite complex (tmux, agents, editor, etc). So I don’t think this a black and white situation where “LLMs will replace engineers”.
I think the architecture around systems is un-replaceable like what I do now, is I create specs and then asks the agents to cook exactly as the spec.
What's your AI workflow btw?
>architecture Give me a reason why agent can't create great architecture when enough context is provided?
For example If I ask LLM to build an analytics system where, there is soooo much data to ingest and LLM uses postgresql for the DB but we know ClickHouse is the great fit here, given the analytics queries we need. So, then you are right LLM can definitly figure out ClickHouse or something better, If we provide full context of what we want, but getting to know the full system and feeding LLM with the right context is something where we need understanding of the tech-stack atleast in general (might not be specific to the underline language).
I don't believe LLM can ever build a system from end-to-end reliably.
Yes, but i am ~10 years beyond that point. I have solid computer science background, and i feel like anything above that now waste of my time, because i can just ask LLM and apply my fundamental cs knowledge. It might sounds fun for someone, but for me it is not challenging
We used to be obsessed with elegant design and would lose sleep over an optimization. Since vibe coding came along, those days are gone for good. As technologists, we typically feel anxious about losing control over our code. The speed of AI makes it nearly impossible for us to carefully review the code.
We know AI makes mistakes all the time, and our job has become that of an AI corrector.
One outlet in all this AI craze is finding creative use of it in mundane work. For example, recently I made SIMD-level optimizations for XLS parser that is used maybe 2 times per day. Before AI I could never waste a week or two on doing something silly like that.
I'm sure the "price reckoning" will come to us when VC will find out they didn't have infinite money, but for now we can have some level of fun even with AI.
I wish I had better news, but really just want you to know you are not alone and I empathize with you. I do think there is a cost to pay when using AI to output all of the code. A deep mental model is impossible and this will have downstream impacts. I am hopeful this will settle into a happy middle ground where AI is used but not relied upon.
Wow. This phrasing hits home so hard.
I came to this realization after I used Cursor to rewrite a 10-year old codebase (I knew every bit of the details.) and it was done in 2 days. Better, fewer technical debt and I was happy to archive the old repo.
1. Embrace the AI and continue working and earning for as long as you can. Bank as much savings as possible. Lower your cost of living. Hopefully you've already been doing this over the past decade plus, when times were good. FIRE.
2. Don't use AI to write code. Write code yourself, as you've always done. Then, just see how long you last at work. If AI truly progresses, then long term most programmer jobs as we know them today are going to disappear. So worst case you will be let go a little earlier than your peers.
The devs using AI to write all their code are going to suffer major or complete atrophy of their coding skills. It's only been about a year of this and we're already seeing it occur. Maybe this doesn't matter long term and manual coding is truly dead, or maybe it comes full circle and we get back to programmers programming, in which case you will have a massive leg up on the NPC "programmers" who haven't written code in years because they surrendered their craft -and brain- to AI agents.
Went through this identity crisis super strong about a year and a half ago.
I feel like I'm mostly over it now. The surface area of interesting things to learn seems ever expansive. It's fun to find the frontier and the spaces where the models still struggle, and then work together to overcome a hurdle and achieve something neither of us could have achieved individually.
I suppose that frontier too will thin and eventually vanish.
For now though I think it's best to take whatever time you need to be nostalgic, but then realize how awesome it is to get to be a programmer at this inflection point.
Therefore it’s not AI fault that you built your identity on sand.
The goal had always been - delivering value, solving problems.
How about building your identity around that and see what happens?
In this context AI is nothing but good news, with proper attitude and skill it helps achieving the goal better, faster.
> Therefore it’s not AI fault that you built your identity on sand.
I mean it is a pretty disappointing comment, so you're absolutely not wrong on one axis at least.
But you might consider reading the submission well enough to manage something a bit less thoughtless and belittling.
>In this context AI is nothing but good news, with proper attitude and skill it helps achieving the goal better, faster.
It is good news if you are in a lower spectrum of technical literacy. What AI did is significantly lower requirement for hard skills for problem solving. Before AI gap between smart and experienced dev and smart junior was gigantic, not it is almost non-existing. If you consider yourself good programmer, you are now way less valuable
Who do you think created the discipline? Why? Who invested their resources and capital in its development? Why?
You can downvote me ad much as you can, but it doesn’t make you a special techincally enlightened cookie.
And this wouldn’t magically make programming an art form (ad many of people like you mistakenly think). It was always a trade, not designed to be enjoyed or have fun about (that happens accidentally every now and then).
But even if you consider it an art form, form of expressing identity, individuality - you are free to do that as much as you like. And I would be truly happy for you.
But don’t be naive and arrogant to consider yourself smart vs them dumb juniors. And to be resentful about genuine technological progress in the field.
That computer is where I downloaded my first porn and where I met my first girlfriend on IRC. We would role play almost every night about a cyberpunk future where we both became sexualized variants of the characters in Snowcrash. I never talked to her in real life or on the phone, but it felt like we were physically dating.
Eventually, we saw the advent of MySpace, Facebook, and all this other fucking bullshit that nobody should give a fuck about. I don’t post pictures of myself anymore because I was bullied on these platforms for my appearance. I’m a 400-pound man that is five feet tall. One of my hands also stopped growing when I was three years old. They would call me “that fat midget with the small hand.” Very clever. Fuck these stupid ass websites and the people on them.
Fast forward to 2022. I’m a lead software engineer at a mom-and-pop shop that grew rapidly. I have six software engineers under me. Teaching them things about programming annd exploring the wonders of logic and reason. Telling them to rid themselves of superstition and religion. They saw me as a god, and I felt like one, too. I had honed my skills at typing code into my computer and making it run. Every day I felt like John Wick.
Fast forward to four months ago. I’m reading trash 1,000-line pull requests and pulling my hair out by how awful my engineers have become. I tell them I don’t care how efficient AI is. They don’t understand and appreciate the craft. They all look at me like I’m crazy. I tell them that we are going to stop using AI and going back to the old ways. The sloppification of my profession will no longer be allowed.
Fast forward to a month later. I’ve grown to be 450 pounds. The mom and pop of the shop tell me that people have been complaining that they can’t use AI to code, and two people complained about how I smell. (I remember the days where this was a sign of genius and something that was occasionally understood. Sometimes I have better things to do than shower.) I tell the mom and pop to shove their AI in their ass. They fire me.
Fast-forward to today. I’m writing my own operating system from scratch to compete with Apple and Windows. It is called WindmillOS, and it can only be used by people who care about hand-crafted software. I have a contact at Acer who says there is a chance it will be used as the OS on all systems moving forward because they agree it is the right thing to do. I have also exchanged emails with RMS, and he agrees the OS may be groundbreaking.
The moral of this is that everyone else is delusional about AI. Software is an expression of my soul and is an art. It is not something that can be generated by a computer. The world will soon see that human-made code is the only code that will work in the long run. Keep the faith.
If you think about it, a lawyer is an ideal profession to replace with AI. To a large extend doctors diagnosing based on inputs is the same. But they have the keys in form of their diplomas.
Overall, I am not concerned about the slopification beyond the fact that cybersecurity is dead. Your only way out of it is to do what I've been doing and cut all ropes to cloud providers and and self-host everything, but that's a different topic.
I've had to scroll through tons of slop and the harsh truth that sloppers/clankers/ai evangelists cry over is the fact that you end up with a ton of unmanageable, over-engineered spaghetti soup that is held together by hope and dreams.
The constant data leaks, security incidents, downtime are not becoming more frequent by pure coincidence. The endless todo apps are not gaining traction because there is no demand for them at all and is the only reason why security incidents are not more frequent.
The real hard to swallow pill is that most people in software engineering were not in software engineering because of their passion or desire to be there: it was the relatively-higher pay and nothing more. AI didn't destroy that - the masks are finally down. What is sad is that more often than not, businesses are obsessed with delivering features as if there's an infinite number of clients that require them and an infinite amount of clients that would jump on board the second you release them. Sooooo. Throw a plane full of cash at anthropic/google/openai/etc. And hope for the best with a pinky-promise IOU. For those that are/were passionate about software and are not as fortunate as me and forced to slop their way though the work day, this is no doubt heartbreaking. Software is a lot like Lego - you have some basic tools, you know what you are trying to achieve and you have to fight limitations. Putting the pieces together is the most rewarding part of the process. For those people, slop machines took the most rewarding part of the job.
There's also the fact that slop is currently heavily subsidized by investors so most people are paying a symbolic fee. The real question I have is what would happen when the real prices hit? I suspect a lot of companies dying if they don't have a financial backup strategy/enough cash to invest in people figuring out what the endless slop does or simply having to shut down operations. Only time will tell.
The goal was being able to make things and I've judged my abilities on how much faster I can do things year after year. This speeds things up on one side but creates this backlog of things that need testing.
I still love programming but I always preferred the language and style I used 30 years ago. I've been forced to adapt to newer ways, frameworks and different methods to keep up with the times. Using AI is the new react/angularjs frontend pattern of 2015. All of these new patterns were less satisfying then what we had before.
For me I'm doing things I couldn't find time before and polishing areas I could but weren't high quality enough.
Paying for AI is a struggle mentally and trying to find a good balance is part of the newer challenge. A codex subscription gets used up too quickly or I can't find enough tasks to use up my subscription and both states cause mental burden. At work trying to maximum output while keeping within a reasonable token usage level is a struggle. Local models using cpu can do a lot for free but need to be carefully planned to limit scope. Using free opencode models works but code quality can fall apart so carefully balancing that can be hard. The code quality of top end models looks awful but can be better if you want to spend time on that aspect and trying to balance that with token usage is hard.
My biggest wonder is if job interviews are testing that you can hand code still but forcing you to use llms when hired.
It’s a new and different challenge.
This is the core reason. It hit me hard too. What worked is accepting the change, and then tuning to the new world, new challenges, and new identity. It's the only option.
My experience is all encompassing. AI has attacked and destroyed almost every aspect of my previous identity over the last 2 years, as well as all of my achievements. My life today as a result is very different. Almost all of the things I used to do for fun or to pass time I no longer do.
I documented this in another comment recently so won't rehash but if you're interested, https://news.ycombinator.com/item?id=49334614
For me it's all of the writing and little projects I created which are now basically useless that hurts the most. I can try to find other ways to be useful going forward but I'll never get back decades of lost time. I have so much pointless knowledge polluting my head.
I'm a massive AI doomer though and fairly sure RSI is nearing or maybe here. Given this the next few years are likely to make any current concerns about identity seem so small and silly that I'm trying to focus on the things that matter and trying to live in the moment.
I'm basically living like I've been diagnosed with terminal cancer – just trying to absorb as much of life as I can and not worrying too much about the future which has been taken from me.
First, it's good to know I am not alone in feeling that a certain world, no longer exists. This is the world where when given a problem, you would spend maybe 3-4 hours scoping it out, doing some research, maybe drawing up some diagrams and then jumping into the code. Coding itself was a necessary part of this process, where it was meditative. You were in this zone between deep and shallow work. It's odd to "reminisce" about coding as if it was such a beautiful thing, in reality it was hard. Required a lot of elbow grease, but it was fulfilling (I wrote 10k LoC over 2 weeks, it isn't about LoC as a metric of good code, it was more about the effort put in felt really tangible)
The world today, is fundamentally different. Today coding is really cheap, even disregarding the best SOTA models, OSS models are catching up in how consistent of an output they produce. Note the word "consistent", I won't say the code wirten by Opus or Sol is "good", but it's consistent enough to where with the right infrastructure around it (aka harnesses) you can get it to work really well.
2 years back, saying "LLMs don't produce good code" was objectively true. They were good for maybe a function, heck I remember AI straight up producing incorrect logic. Today with the right context, the "code quality" (interestignly, quality is a human metric, maintainability would be more apt, and the cost of building a change) is upto par or even better than what I would write on the first iteration.
Given that the cost of coding is now 0, my job becomes to solve problems, in the best way possible, WHILE directing the HLD/LLD of the system to understand the limitations of what I have built. The latter, I only do because it's much faster knwoing a limitation in a codebase than having an agent "recongize" it through a bunch of tests, and loops (it's cheaper too) -- THAT is where my experience really shines, knowing which patterns to apply to what problem and expect what results. Heck, we live in a time, where I can trivially have an LLM run experiments to quantify 3 other approaches at the same time.
Fundamentally what I do, is managing context, scoping problems & requirements, understanding limitations and directing the codebase (again, also drawing from experience, since an LLM may arbitiarily do something which leads to increasing entropy in the codebase)
Think of it like this; If software engineer, was like maintaing a garden, then 5 years back the process was -- think about how you want your garden to look, with this in mind begin planting the right seeds, pruning the bushes, weeding the overgrowth. Today, I have robot to do all that stuff for me, that leaves me a WHOLE lot of time to plan out my garden, thus, today, I can maintain an entire ecosystem instead of a garden. Not the best analogy, but it models my fear of the LLM not "pruning it right" when in the grand scheme of things, it may not matter at all.
Whew, that was long. I just wanted to get my thoughts out haha