Problem is without LLMs I’m making a contact lead form with some basic stuff and calling it good.
With them, I’m making the whole SaaS. I just made the best DM experience last night. I never would have before. Feels and looks just like iMessage, because the users are coming from that, and it’s just for a small biz. It’s been planned for a while because the messages involve so much file sharing, it was time to build a custom solution, but I had been putting it off because there’s a lot of moving parts.
Doing our own in-house e-signing, email marketing, invoicing too. With just me as the dev. Other options from vendors were too expensive and complicated. Built an invoicing product too, it even writes a pretty good note based on all previous notes for that client.
Almost every business integration - outside a few like payments, hosting, email - become code problems.
If you’re doing it right you should be building more than you ever have before.
And btw random non-devs like car rental hosts and barbers are doing the basic site lead form type stuff for their businesses so without LLMs you’re now doing only beginner stuff. You won’t seem like a real dev anymore. Any random can use that vercel product and it even deploys to a URL. That’s the small biz prosumer case.
The real devs should be doing massive projects a rando can’t do. Or one that displaces an expensive or complicated integration.
In general creators must do some honest introspection. Did you enjoy the crafts, or did you enjoy the compliments? Did you enjoy the difficult puzzles or the identity derived from a career that gives you the reputation and perceived value of someone who can do a thing most people can’t? Did you enjoy the code itself or the accomplishment of seeing your ideas brought to life? Who remains when the thing you do no longer is the person you are.
AI is not perfect, I remain convinced that handcrafted will always beat AI generated crafts. The IKEA vs the carpenter analogy fails because a carpenter has to create each piece of furniture from scratch, serving only a single customer, where digital products by definition are near zero marginal cost, so it is worth it to throw large amount of human hours at proper code vs AI generated code if the quality is better.
PS: You have intrinsic value, and your skills will also remain valuable, if even for how it teaches you to approach complex problems and think deeply.
This is eery to read, as I've been thinking something very similar recently whilst discussing gen AI with a close friend who works in tech but isn't a developer, who now uses AI to build everything he wished he could. Meanwhile I've seen other people, colleagues, friends, who are programmers get incredibly frustrated about AI and it's almost entirely that it lets non-developers make things.
The feeling I get is that they haven't earned it, that they've not put in the years to learn it and now they get to make things. I spent 25 years programming, from 2000-2025. I always thought that the number would keep going up, one day I'd say three decades, four decades, but I've stopped counting. I don't program anymore.
I started using GitHub Copilot in the beta in 2021 ish, where we turned comments into lines of code, then functions, was there the night ChatGPT dropped as a free preview in 22, trialed cursor on its first release, all the way up to now using both ChatGPT & Claude CLI & apps daily. My slowing down of writing code happened gradually, but from copilot I was hooked, I could do more, quicker. And now, I don't write any code, I just build the systems around agents & processes.
I'm okay with that because my thought has always been that we bring value. If we don't have to write a single line of code to bring an org value, we're doing a great job. And now that's almost true.
The people who are upset by this change, in my experience, are all the people who would answer that a programmer's job is to write code. The people who are happy about this change, are those who would answer a programmer's job is to produce value.
In a way, I think you're right, was it always just about the power & compliments for some people? The ego of being able to do things they made them seem like magicians? And has AI broken that stranglehold?
My mother plants tomatoes in her garden. She invests a lot of work into them, only to get a few tomatoes a year. Clearly it is not an economic effort; clearly she is doing it out of passion, not for the actual value of the tomatoes.
However, imagine the plants stopped yielding tomatoes, and would never do so again. Would my mother continue working on her tomatoes? I do not believe so.
I believe that even if you are doing a craft purely out of passion, it is still important to gain value out of the fruits of your labor, be it ever so little.
In this analogy, your mother probably gets enjoyment out eating the tomatoes herself, or maybe giving a few to friends. Technology wouldn't cause her plants to stop growing. But she couldn't support herself full-time as a tomato grower competing against large farms with hydroponics.
So maybe the extension is that professional SWEs who work at big corporations will need to use AI to 'keep up', but hobbyists can still get enjoyment out of their own work at hobby scale without using AI (similar to the point in TFA).
"Some people like writing books. Other people wish they had written a book."
People who don't enjoy the craft are not bothered by AI and will replace manual labour with AI.
There's nothing with that, but what I don't enjoy about this recent discussion is the assumption that anyone doing things by hand is wasting their time. "You're gonna be obsolete".
But that was the reality before, with the stream of criticism directed at people writing game engines, of doing new programming languages, new web frameworks, or anything new really.
This is interesting because it mixes the process with the reward in an inverse way to what I see from AI pro/con. Those who like writing code have seemed to me to lose out in status from the introduction of AI, while those such as myself who care little for status have used AI more and gained from it.
Conversely, those who like writing aren't always about the reward (being an author, having a book published) but those who would like to have written a book regardless of the writing, often are.
One of the big points of art is expressing something to other people. Tired of this sort of shallow dismissal where wanting recognition, or for your art to reach people is cast as a kind of vanity that real artists ought to get over.
Yeah, I wanted to say that too. You can't (always) separate enjoying the craft from enjoying the praise. People too often talk about the value of an art object divorced from its provenance, as if you could measure its goodness with a meter, instead of the value of the audience relating to the personality expressed in it, which means it's a communication, and the communication isn't all one-way. When you're crafting something you're initiating that communication. Of course you want praise, or distressed complaints or anyway some reaction.
Exactly. Motivation is rarely a question of either/or (art for art's sake / art for recognition). And for many practitioners, being part of a community of fellow artists who "know the struggle" is also part of the fun.
I don't think that an artist or game developer wanting recognition is the problem here. I think it's the reflection of their intentions on the consumer in an environment where it's increasingly difficult to separate the cash grabs from the craft.
The first paragraph kind of reads like an inverse of Kant's criteria for a moral action: are you sure that there was no enjoyment, no pleasure was involved in this action or resulted from it? At the same time, it kind of establishes the ethics of self-entertainment, and by this, maybe, an imperative of joyless joy? It kind of echos 19th century 'accomplishment', a modest self-entertainment by the fruits of virtuos learning and training, while with kind of a consumerist twist, as this now involves the use and "modest" development of technology, which introduces an external, social dependency, which it at the same time tries to eclipse.
Meaning, I think, besides utilitarian one-time, one-purpose scripts, programming is essentially an at least potentially social activity, there's always a potential social horizon to it.
> Did you enjoy the crafts, or did you enjoy the compliments? Did you enjoy the difficult puzzles or the identity derived from a career that gives you the reputation and perceived value of someone who can do a thing most people can’t?
I think in the end everyone will be happy. Those who just want to ship, make money and attain status and do not care much for the process will embrace whatever capabilities AI affords them and move on.
Those who get satisfaction from the process and prioritize craftsmanship will also do so and form their own subcultures where this is appreciated.
If software is eating the world as some say, then surely, there can't be just one way of doing software.
Maybe I enjoyed the compliments, the stars, the glory, the God status I always imagined will come my way but never did. Except burnout. That did come my way.
Personally, I think a lot of the enjoyment comes from learning to overcome challenges. Jumping in to an unfamiliar problem space, sucking at it, then grinding until it all clicks.
Generative AI takes away the grind, which takes away the learning. How do I master a new language if I'm expected to code via an LLM from day 1?
It's also well understood that the act of writing is when thinking actually happens. You have new ideas, opinions form, and so on. I think it's the same with writing code. But when you're not writing code any more, you don't go through this process.
I wonder if an LLM-authored project would even end up solving the same problems that a human-authored project would? If a human didn't write the code, then a human didn't have the chance to think in the same way. They didn't spend time trying to think of a good variable name, which made them realise the whole premise was wrong...
I'm too young to have known the assembly wizard world, but how is the job market for people of that skill-set and expertise?
My assumption was that being closer to hardware tends to be more resistant to AI hype since they work in environments where just vibe coding some slop carries much higher risk than vibe coding a webpage or mobile app does.
If one works in AI it's quite lucrative because shaving off a couple percent is worth the big bucks. But increasingly, there is enough training data for LLMs to do the same thing because the number of unique computations is fairly small.
As part of learning how to work with coding agents, I had them code up a bunch of games that had been in my head for years. They were never going to see the light of day otherwise because I have too much on my plate, but it was fun to make them come to life. I didn't do it for money and it's not my day job nor will it ever be but it was educational in learning the limits of Codex and Claude.
But the app stores have been hosed for years ever since the Zynga playbook and DLC. And on Android, if you release something honest and original without those things, it will just get copied and re-released filled with malware. So why bother?
I don't really miss the old days because despite all the nostalgia, engineers were really underpaid relative to equally difficult professions and they usually got terrible shares of equity compared to the C-suite. And has everyone forgotten EA spouse?
Not to derail the conversation, but the concept of money itself is on loose screws. One might argue that compute and energy (dare I say expressed in BTC?) is arguably the (world reserve) currency of the future. The current system discounts the value of the hours of the artist based on where that artist was born, rather than on merit, and is the source of a lot of problems including trade wars, extreme globalization, offshoring, mercantilism and the entire industrial stripping of developed nations by those who purposely keep their currencies low and exploit their own population.
Did you enjoy the crafts, or did you enjoy the compliments?
I'm sorry... I'm trying to be respectful, but I find this comment highly combative and disrespectful beneath a professional veneer. Implying that the opposition --people who also use deep neural networks to make games instead of just using the huge set of tools that no one human could ever understand in full but aren't usually called "AI" anymore-- is lacking in intrinsic value, deep thinking, or soul is typical, but the accusation that they're just bad-faith jerks who only care about being complimented is new and frankly absurd.
Did you enjoy the difficult puzzles or the identity derived from a career that gives you the reputation and perceived value of someone who can do a thing most people can’t?
I think it should be obvious in hindsight that this is a false dichotomy, to say the very least.
Did you enjoy the code itself or the accomplishment of seeing your ideas brought to life?
This part is also leaning hard on vague terms, on top of being another false dichotomy. Do I enjoy typing? Not particularly, tho vim is fun. Do I enjoy "coding" in the sense of "I would still love to make software even if I never got to run it"? Probably not, but who does? And finally, do I enjoy "coding" in the sense of engineering software? Yes of course, but isn't engineering intrinsically tied to specifications and their verification, AKA "the accomplishment of seeing your ideas brought to life"?
it is worth it to throw large amount of human hours at proper code vs AI generated code if the quality is better.
This exact same argument applies to writing in assembly; just like in that historical case, the rebuttal is to point out how fleeting this situation is.
That is, how long at the current rate of progress until it's undeniable that properly-engineered agential code is as good or better than hand-written stuff? Is all code made exactly the same because of heavenly decree, or can agents help write unit tests n such? If you insist that regularly writing C++ files directly is something special that can never be effectively automated, isn't it a little weird that you just happened to be born just in time to pick up on the very last iteration of software engineering?
*TL;DR:* you're inventing an imagined enemy who hates thinking and joy, unlike the noble, serene folk who choose the hard, true, right way. And that's a really antisocial and isolating thing to do, when it's based on nothing.
Sorry if it came off as combative. The points I made are not mutually exclusive but they are in some cases. There is a difference between someone that chose computer science because Silicon Valley was the next Wallstreet, or someone who has been tinkering out of sheer curiosity since elementary school.
I am convinced that AI will be the tool that creates abundance, but that doesn’t mean human engineering is automatically irrelevant either. AI has already surpassed what humans were able to do, for instance solving certain math problems. My point was mainly that engineers are forced to introspect, and that includes questions about identity, what it means to be human, and the motivations behind their work/hobby.
I've observed this dichotomy myself. Some people will make things because they enjoy the experience of making. Others make things because they enjoy achieving an outcome- happy client, open source community, a new useful tool for themselves, whatever the case may be.
There's also room in the middle, and people who are nowhere on the scale, that just like getting paid.
This would be the more charitable take than your TL;DR
Yes, I read the 5-7 paragraph article :). I'm not sure what part of it you could possibly consider a rebuttal...? It's just talking about one devs decision to keep working on their purist software despite their anxiety; basically no broader points are made at all, and certainly none are made with any sort of rigor. It didn't seem like that was his goal.
This is more or less precisely how I feel. Other creative fields have already begun to get a handle on how AI is a soul-deadening thief of joy in their fields. I have hope for illustrators and painters and photographers and musicians and makers. With those friends and in those communities I see people who have already done the thinking, can already express their feelings, and are already making commitments to do work in ways that defend them.
The software development industry has still to reckon with the extent to which it is punching itself in the face, and it is precisely because AI does have at least some utility.
I don't know. Maybe it's the people doing software dev that are yet to reckon with it to a degree -- or have found themselves on opposite sides of denial.
I think industry is quite clear that AI is helpful to their bottom line. At the end, that's all that matters to them. That SWEs cannot, say, unionize to prevent this shift in labor-elimination or articulate any other coherent way of countering the industry's desire to push forward with AI-assisted coding, shows me that there's an understandable desire to preserve this golden egg of being a high paying SWE. But that ship is setting sail, and becoming rarefied.
My first thought after reading this was, good for this person to have only been broken, or nearly broken, I guess, by society finally now.
I was broken long before AI. I learned that no one was interested in my doodads even before generative AI. People were interested in all this other stuff, like ROI, how much money things make, how practical something is, etc. "No one cares about the code" was beat into me 10-20 years ago. Big ups to Joel for making it this far.
I liked building apps and helpful tools before AI came around. I've been doing so for 15 years, 10 of them professionally.
Today, I like it even better. It's never been so fun.
What would have taken days of work, if it was feasible at all, I can have implemented in half an hour now and iterate on the result to make it work the way I want.
I stopped reviewing the code at all.
People on here are often saying how that's a disaster, how the result would be unmaintainable, and so on. I think they are clueless.
My app has 200k LOC + 100k in tests, and there is no sign of the AI slowing down or being unable to maintain it.
I've been working on the project for four months now. I invested hundreds of hours, and I expect to publish my paid app in the AppStore this month.
It has been fun. I am using the app every day and I look forward to the features I will add in the future.
>My app has 200k LOC + 100k in tests, and there is no sign of the AI slowing down or being unable to maintain it.
May I ask what does this app do ? 200k is like GTA vice city level, is like sqlite level, If its a financial tracker or a to-do list or an agent coordinator I am going to kill myself
Vice City was released nearly 25 years ago! Also it's a game, so it's not really an apples-to-apples comparison. If you count the unique 'features' (or systems) of Vice City, you might find it's a comparable count to the number of features of a medium-sized mobile app.
I'm not going to share exact details about my paid app, but you could think media management, with a lot of extra features, an in-app browser with custom controls, and multiple AI powered features with on device processing.
Me too I use my apps every day. But the main thing coming out of this is that they are tailored to me. Turning hobbies into hustles is one of the worse things that happened in the post social media days.
>there is no sign of the AI slowing down or being unable to maintain it
This means you designed the system well and made sure the agent implemented it correctly. Even at Big Company the big shot architects don't review every line of code, and nobody seemed to mind that
It’s just a fact that an ai will write and read faster than me. I can’t compete so getting ai to do that has freed up both time and mental capacity to actually think about the implementation details.
I'd like to think it comes down to my expertise, but I don't believe I did a lot of designing.
Sure, I've given a lot of inputs over the time, probably I've steered it to solutions that work.
Maybe it was also helpful that I set up a skill to use a different model to review the code for correctness, technical debt, and whether the location where the code is added is appropriate or warrants a new file or abstraction.
I set this up long before subagents were widely used.
Everyone should do whatever makes them happy. Whether anyone will care much about your hand crafted software ...im leaning mostly no, perhaps very very niche programming communities. How do you even prove to people the software was hand written? And why should they care? Its not like music or art where wondering and caring what Kurt Cobain was thinking when he wrote the song is a big part of the experience. I'm skeptical I'll wonder what went through the head of the guy who wrote Excel or some crud app. I just want the thing to work it is not art for me.
Since I am currently using AI to make a game engine, I feel like I am sort of qualified to say something on the topic, and I don’t think it’s really true that AI’s can just roll one out without a lot of poking. They constantly go off on the wrong track and I have no faith that they’d get anywhere sensible without a human steering the whole thing (for now anyway).
But even if they could the best thing they’re ever going to do is reach the sum total of human knowledge. I can’t ask it to think of a novel algorithm to speed up my flows, and even the places where I feed it a literal paper and ask it to reproduce it in a production ready matter are often exercises in patience.
That said, for me it’s better because I like thinking of ideas far better than typing out code for ideas to become reality.
Yep. AI can probably make your marketing website or REST service on autopilot. Or even small minigame experiences.
But go outside the bounds of median programming and AI becomes increasingly scatterbrained. It requires a lot of guidance to successfully build high performance, novel software. I still find it more productive though - I can work on three tasks simultaneously with AI, and only one if I’m manually working on a single algorithm. It’s very much like running a team of well-read junior developers.
I spend so much more time with generative IA thinking and iterating over design details (or even overall design) than before, when part was consumed by writing the implementation.
Bots are often terrible and/or don’t have all your requirements available on this subject, or even your are discovering them along the way and you don’t all the time want the recommendation of the machine.
From my experience not iterating enough and leaving high level decision to generative IA yield shit. Maybe this is not the case in all projects. But in my work, it would be absurd to complain about not having to know random API details anymore, unless when they actually matter.
The thing is that I’ve been programming for more than 30 years. Maybe I would have another opinion if I was still learning the things I was learning 20 years ago.
For the last couple of years, I've been crafting and shipping a free app that Serves a particular narrow demographic. It works extremely well, but is a native iOS app (I don't write Android). When I first developed it, I worked with a professional graphic designer, and the app has a unique UX. In fact, with the latest release, I had to "walk back" a bit of the stuff the designer did, as I believe it interfered with usability. It's really a pretty intense app. There's a lot of moving parts. It handles user data, so I have to make sure it's secure and high-Quality.
Recently, a couple of very talented engineers vibe-coded a cross-platform app that is nowhere near as nice, but is highly effective at the most important aspects of the one I wrote. They are also very good at promoting, and it will get a lot of press. I have no doubt that many folks that would normally use the app I wrote, will use that.
At first, I was all mopey and emo about it, but I realized that it doesn't matter. Their app is decent. It's fairly ugly (LLM-generated UX is pretty bland), but works very well. The guys behind it, are good engineers, and I know that it will improve (although I doubt their UX will, much). Neither of them is a native iOS or Android developer, though. They are backend folks.
Instead, I'll be doubling down on making my app as good a native experience as possible. There's still a lot of stuff I can add, and Apple keeps adding more capabilities that afford native implementation.
I have also been using an LLM as a "trusted advisor," not as an employee. It's made a huge difference. It may end up eroding my "hands on" skills a bit, but not by that much. I find that I am constantly reviewing the work it does, and my knowledge helps me to really get the most out of it. I managed a software development team for a long time, so I am pretty familiar with delegating work to employees that are actually more capable than I am. I guess that helped me to accept LLMs, as an IC.
I'm basically looking forward to this. One of the reasons that many of my apps don't have a lot of new features, is because I never had the time to study and implement them (I refuse to add bad stuff. It needs to work well, so I am picky about what goes into my work). With an LLM, it looks like that is no longer an issue.
I've only found one answer to the "creative work" struggle now, after code writing as an art seems to have died.
Start to write. Or continue to write. Or consider writing as the place to explore and develop your ideas. They're just words. There is even more freedom there to create. Not restricted by a compiler. Not restricted by the shape of the final product. Words can be written anywhere. Sometimes on a paper, even. On my phone while strolling and ideas pop up.
What people like about code is that you can run it and then it does exactly the things you wrote! And there is a precise, predictable relationship between the code and what it does, which you can fully understand and reason about!
Neither natural-language-writing nor LLM-prompting does give you that.
1. It is great to see an effect of your thoughts, like something happening in the real world.
2. Coding offers a feeling of perfect control due to the deterministic nature of code.
I would argue that 1 is still the case with LLMs, and 2 was always just 95% true, never 100%, because of oversights, bugs in libraries, and what have you.
So what actually decays is maybe not so much the feeling of self-efficacy, but the feeling of control, and even this is a gradual change. Perhaps it would be less unsettling if it didn't happen at the same time as a potential loss of control in other areas: career, salary, mode of working etc.
I think the middle way is best here: use AI so you understand how best to apply it to your work but don't deprive yourself of the joy of doing stuff by hand. And if you so desire: just write by hand.
Very unlikely to apply to any job moving forward (i.e., they've equated AI with a competitive advantage, even if the results are not technically competitive), but a job isn't you and you are not a job. And if you're like me, where building stuff is your business, I highly recommend using your skills to build something that makes money (without freaking out about how the thing is built) and then use that to pay for your life and work on code however you'd like in the off hours.
Frustrating? Absofuckinglutely. But you can either spin out or keep progressing, however slowly. My wife and I have been talking about a growing renaissance movement as people where we live (normal, everyday people) go in on other locals for using AI for stuff. Just saw one on Reddit the other day where a local venue got chewed out for using AI for their event flyer.
That doesn't mean AI goes away or everyone "wakes up," but it does mean that it's not this universally loved thing. I personally think that will be the shape of the future too: some places in the world will be all-in while others will opt-out. If you truly want to be a pure craftsman, it's worth looking for where those places and people are and consider relocating. Environment has a huge impact on your ability to think well and clearly; don't underestimate proximity to AI making it seem more threatening than it actually is (and don't just dismiss that as delusion or wishful thinking).
Also don't forget: the economics of AI are unhealthy and this first wave of AI will likely be washed out, followed by a "plateau of productivity" for a few survivors (think how the internet looked from ~2002-2009). Again, just my opinion but I don't think the overall outlook is terrible if you don't allow yourself to be disconnected from your craft and find others who feel the same.
These articles are frustrating on HN because it's quite common for programmers to tinker on small projects in solitude, so when artists complain about ai you get all these "just make stuff for your own sake, or where you in it for the fame?" reactions.
I can create the programming part of the game. I have done a couple. Where it stops working for me is at the visual assets. And especially sewing the code to the art.
Also tried it with AI generated art. Is not there yet. I can generate a beautiful image but then cut it to pieces so I ca use it in a game breaks apart.
It can be done but it looks obviously underwhelming.
I like the craft but I enjoy making products more. Working for 5 years on some tool chain/libraries has been great in terms of “technical” satisfaction but it would have been even more rewarding to build successful products with all that.
And I think this is really the best of both worlds because AI coding works best when you give it constrains and without my toolchain the AI is generating crap code I wouldn’t ever want to read but using the libs I wrote and know I can constrain it to write decent code that works “at scale” . The more opinionated the tools/libraries the better outcome you can expect.
Another great usage of AI is for refactoring. Before AI you could have a great idea how to make the library better/more ergonomic but the sheer amount of refactoring would make you just eat the debt and basically live with your own “slop”. Now with AI you can produce the reference design for the refactoring (I.e let’s make all these functions actually methods) and the job is done in minutes/hours. This inevitably leads to better designed software.
Yes, AI shines as a hybrid tool for hyper-generalists or multi-domain experts that can leverage their deep knowledge across various fields but lack the raw hours to execute everything themselves. Strong developers who never knew how to manage a team but should have been product owners based on their broad knowledge and vision of the product and industry.
I agree with your point on refactoring / porting. Retro consoles and homebrew will see growth, probably.
> Through chatting to Shad I came to realise there are only really three paths open to me. I can start using generative AI to feel like I’m “keeping up” or “competing”, but then I won’t enjoy the work. I could stop making things entirely, but as any creative person will know that’s never really an option. Or, I can keep making things the way I enjoy, keep learning, keep doing it the hard way, for no real concrete reason other than I want to do it. That’s why we make games. That’s why we make anything.
So, a very long blurb to simply say that you can avoid using genAI and just do things "the hard way". And why? Just because he wants to do it.
Frankly, I was hoping for a deeper, more interesting conclusion.
I see your point but I'm not sure there is much more to say on the matter: apart from having fun, learning stuff and taking pride in your work, what other reasons do you see for "doing things the hard way"? You could argue that it makes you more competitive because you'll be better at babysitting a coding agent, but this feels less and less true with every new model. Unless you're seeing something else to take into account here?
> Frankly, I was hoping for a deeper, more interesting conclusion.
Pretty much this. There was a lot of build up in the first paragraphs, only to conclude something that, at least in my view, is remarkably uninteresting.
I personally went through the authors dilemma but came out different. I personally don’t care for the writing by hand, but absolutely do read every line produced by AI, because I take pride it a well designed and easy to understand system; well designed abstractions. I’m able to build better and easier to understand software (with better tests!) then I ever was before.
AI is a great editor; I can finally do all the refactors that I wanted to do that were much harder before; would have taken a long time.
AI is great at writing tooling, I love a good tool that gets the task at hand done; encodes a task that others will need to do. Couple that with a skill file and now a fuzzy tech debt migration can actually be completed across many teams at there pace.
I focus on the cheapest model/fastest model (been using Luna). I use pi and don’t try to multiplex my time, and stay in flow on a specific task till it is done. And I’m very happy with this, actually enjoy this more. Vim skills stay useful for editing the prompts/module structure/fixing slop code during review/ and review.
The volume of code is high so reading a diff is suboptimal for review; so I tend to review from local checkout using vim (LSP tooling important during review, go to def, etc).
Long before generative AI we all knew one absolute truth: ideas don’t matter, it’s the execution. YC marched to the drum. Execution! Execution! Execution! Do things that don’t scale, do the hard things, build something people want.
And then generative AI arrived and suddenly, unless you’re generating the maximum amount of code in the minimum amount of time, you’re going to fail, you’re going to be left behind, programming is dead, do the easy thing, generate! Generate! Generate!
We are years into generative AI and still there is no fundamental change. The most successful businesses are still the businesses doing something well, not businesses doing things easy. Spending hundreds of hours writing every line of code by hand isn’t a competitive weakness, it isn’t foolish, if it creates a good product.
So, I agree, fuck it, type your code line by line. Users don’t care if you spent 1 hour or 100, they care if your product is good, just as they did in 2025, 2020, 2015…
Maybe you’ll get beaten by someone generating a million lines of code. Just as maybe you would have been beaten by someone who typed faster than you in 2020. Nobody worried about increasing WPM in 2020.
But my purse does, as do my investors. I can no longer justify taking a hundred hours to build a product, even if that makes it materially better than that of my competitor, who spent one hour to build theirs and used the other ninety-nine to sell it.
I don't like that either, but it's the reality we live in now.
> And then generative AI arrived and suddenly, unless you’re generating the maximum amount of code in the minimum amount of time, you’re going to fail, you’re going to be left behind, programming is dead, do the easy thing, generate! Generate! Generate!
This reminds me of a different theme in the programming world.
There was always a feeling that development spends time on meetings long past the point when the app could have been finished. And I remember a comment here on HN (which I can't find now) saying how, if you're on a team at IBM working to develop something for a client, you will feel that you could just go ahead and finish whatever functionality you're supposed to be developing.
And if you sneak in after hours and do that, you'll be met with the message that you aren't being helpful, that you've got to wait for the business to determine that that functionality really is what the client wants, that the app needs to be described a certain way to get signoff from other decision makers, etc. Anything annoying that you can imagine.
But the overall takeaway that I saw was that developers tend to be frustrated that business processes are slower than the act of producing the software, and they feel held back by that.
Given that background, it's not clear why generating more code per unit time is valuable at all. That's something developers wanted to do all along, and they were told they shouldn't. More code per developer would make sense, but why more code per time?
> I’ve spent years learning how to make games, and it’s been hard, and now it feels like that might have been a waste of time?
Generative AI is really awful at building games that are fun to play.
It is a masterclass at reproducing Minecraft clones and shiny HDRP demo scenes in one shot. But, unless you are a total novice at game dev, you should be able to see through these cheap tricks for what they are.
99% of the game dev AI doomer posts seem to spiral out of vacuous demos posted to social media. None of this AI generated slop is actually playable or marketable.
I just got done talking to chatgpt about progression sequence for a horror game and it is beyond hopeless. It would absolutely ace any mono behavior scripting, but it's totally ass at directing anything that would make it to the front page of Steam.
Are you saying Assassin's Creed 87 or Far Cry 32 aren't cheap clones of its own previous incarnations? The gaming industry is, to a huge extent, just an optimisation problem for MBAs running the major publishers. Most gamers don't really value creativity, but easy rewards and familiar tropes in eternal regurgitation. AI is going to be able to pump out a never-ending stream to satisfy that market rather sooner than later.
That obviously still leaves some space for the occasional streak of creativity or very talented game devs, but that is by and large just a tiny sliver of the industry even today.
Yeah those games exist, and most gamers don’t want them. We’ve not been able to convince the industry to stop bothering to make them, so they still do dumb stuff like, making Concorde, then realising nobody wants it.
Indie and non-triple-A studios keep having wind, because they’re the ones producing interesting and fun games which people _actually want to play_.
Still, every day, I say to myself out loud, "this is crazy".
It's one of those platitudes that everyone knows, "the only constant is change", but everything feels like it's going be forever anyways.
Your parents will live forever. Your kids will stay young forever. You'll be at this job forever. You'll keep doing this routine you did this week forever.
Quotes, or advice, or history books are just too abstract until you live though them yourself. Looking back at all the history books I've read, I realize that this kind of magnitude of change is the norm. The Industrial Revolution. Colonialism. North Atlantic slavery. Chinese famines. War. Plague. Economic Depressions. To be honest, this is pretty tame, now that I'm making this list.
Nobody thought that the entire industry would just be totally upended in such a short time, but here we are. A job that came into being just a few decades ago disappears just as fast. It happened to all kinds of jobs over the past few centuries, and it'll keep happening.
Time to get back to typing, "Do my job" over and over in a chat window.
The problem with what you're saying is there has never been a technology that has the potential to disrupt the workforce at this scale. There is also no clear pathway to "this opens up more jobs". This is not a tool the same way an electric saw is a tool. An electric saw replaces a physical thing that we do (manually sawing), but AI replaces our thinking and intelligence.
My friends and I have been asking this exact question lately. I’m sure people are still working on interesting things that AREN’T AI. I too would love a HN-minus-AI.
AI didn’t take initiative, circumspection, effort and thoughtfulness away. At the end of the day, those are the qualities you can rely on. Pats on the head from others come and go.
You can still control the output LLMs produce. Obviously you can one-shot "make me a fun game" but I think there's a whole spectrum from pure vibe coding - you literally never look at the code, through controlling the direction and skimming the code all the way to reviewing every single line and manually editing parts.
Also I think the quality of the models has made a big difference to my attitude. Until Astra they were kind of "meh, a junior engineer could do this but I wouldn't be happy with it" but with Astra I feel like it's reached the point where it's competent and it just lacks taste in some ways. It's even done some clever things that I might not have thought of.
Hobby stuff- I found slowing down works best. Just enjoy spending time in the evening picking the colors for my little project that will never ship. Genuinely relaxing, had some random boomer sitcom as background noise.
Work - max adhd no brakes cat stand dog stand satellites.
Honestly loving software engineering right now. The age of magic incantations and magic meat is over. I’m the wizard now. We all are.
I like the codegen = power tools analogy to writing software.
I didn't go to school for CS or adjacent: I went to art school 20 years ago for 'new media' which feels like a _silly_ thing to have on a diploma in 2026.
My career started in high school and ran this way: print design w/ computer geekery on the side -> classes in all sorts of digital media production methods -> web design -> web development -> full-stack development w/ a UI/UX focus -> engineering manager ? -> engineering director ??
Then Claude comes crashing in a couple years ago and suddenly code I would grid on to get right got easier and easier to ship. I have enough _experience_ to know not to trust it, put in the appropriate guardrails, and now we can deliver work at a velocity that makes more people happy and keeps my team grounded in a reliable 40hr workweek.
Back to power tools: I'm done going to READMEs and docs and learning the order of operations to build with a hammer and nails. Turns out I didn't really _love coding_. The Job To Be Done was to build the app/feature in a way that satisfies business and user requirements, can be reliably maintained over time, and is securely integrated with existing systems. The tools are now fully-automatic instead of semi-automated with IDEs and linters. Turns out I just like delivering product that solves business objectives (working on turning that into a bigger thing).
I'm still functionally the Responsible Party that gets in trouble if things break down, and its been a couple years of codegen entering our repos and things haven't broken down.
I'm using the lightness of mind the above now provides to find space for the things that strike me creatively, like I did when I was younger and more into art and music. I'd rather spend that creative juice elsewhere, not coding.
So I'm sorry to the coders who love the craft and feel like the industry is slipping from them. Like many industries that have started as craft, code has officially entered its mechanization phase. It requires less finish carpenters who know how to work a coping saw and more general contractors with the latest 18v line of tools.
There's a bigger audience of businesses and consumers that want solutions built quickly, reliably, from a trusted party with experience than there is for tailored code.
I don't mean for this to be discouraging. I really like photos OP took in this piece, and that NoAi camera app looks really great! I'm sorry there's no profitable market for it, but I'm glad it exists! I feel like the skills that created that app belong at an Adobe or an Apple working on creative tools where they can afford to hire someone to work on just single feature or idea.
I wish there was more opportunity for everyone to do work that brings them good brain tingles makes you feel the most human you can be. "Fuck it, make it anyway" is exactly the right attitude rn if you can afford to do it.
Pretty unusual to see the /r/aiwars slapfights (here presented without touching on any of the obvious rebuttals) make it HN, but I guess it makes sense. I'm sure a sizeable majority of the US population agrees that visual art that involves neural networks at any point is dogmatically Satanic, so that probably includes at least ~40-60% of this crowd, too.
It's also a little disheartening for me to see people crashing out about philosophy of aesthetics at a time when I'm terrified of grey goo and killer drones, but that's more on me than him. I'm not exactly doing much to prevent it either, so staying on the previous societal crisis seems defensible!
On the (well written!) post's particulars:
I can't help but feel like this attitude is... "myopic" is too far, but perhaps... intensive? Namely, it seems to be treating the contemporary craft of game design as some hallowed pursuit that artificial claws are ripping away from us, when in fact I'd argue it's one of the most recent and most rapidly-changing SWE subfields around. Yes, a lot of the skills he learned will be useless. Yes, that is inherently embarassing and anxiety-inducing and enraging, and no, none of us saw this coming (don't believe the scruffies, their fingers were crossed up till ~2018, too!).
But is a world in which video game designers get to make higher quality games faster really such a bad one? I've felt frustrated with the scope and polish of AAA games for years, and the quintessential indie dev story involves way too many years of toil.
Of course that falls apart if you assume that involving neural networks at any point in the process necessarily leads to worse outcomes, but... well, don't? That's clearly just a dogma, so either open it up to actual scientific experimentation or just adopt a different, more reality-amenable dogma. Living life as an anti-AI purist (or Luddite, I say with the utmost respect for King Ludd) puts you in a cognitive place where the soul of humanity is under seige by shadowy, chrome figures, and the only way to get to a healthier place is to examine that assumption.
Like, clearly, software made with Soul and Taste and Intuition and Experience and Consciousness can still be published -- and I'm glad the author and his friend are doing so! The threat is that they might not perform as well in a marketplace ruled by capital, but, I mean... did they ever? Writing your own game engine in C++ was already the equivelant of going to university for Tuba, or striking out as a full-time landscape painter; it was mostly for the children of the rich.
*TL;DR:* Would a radical shakeup of the video game world really be such a disaster? Assuming we aren't just assuming a disaster, that is.
With AI story telling, lot of people can tell their stories. Democratization of story telling. Earlier we just used words, now people can make others imagine the words with AI art. Honestly I want the best story to win. Anybody can be a storyteller.
With them, I’m making the whole SaaS. I just made the best DM experience last night. I never would have before. Feels and looks just like iMessage, because the users are coming from that, and it’s just for a small biz. It’s been planned for a while because the messages involve so much file sharing, it was time to build a custom solution, but I had been putting it off because there’s a lot of moving parts.
Doing our own in-house e-signing, email marketing, invoicing too. With just me as the dev. Other options from vendors were too expensive and complicated. Built an invoicing product too, it even writes a pretty good note based on all previous notes for that client.
Almost every business integration - outside a few like payments, hosting, email - become code problems.
If you’re doing it right you should be building more than you ever have before.
And btw random non-devs like car rental hosts and barbers are doing the basic site lead form type stuff for their businesses so without LLMs you’re now doing only beginner stuff. You won’t seem like a real dev anymore. Any random can use that vercel product and it even deploys to a URL. That’s the small biz prosumer case.
The real devs should be doing massive projects a rando can’t do. Or one that displaces an expensive or complicated integration.
Tons of opportunity at every corner.
AI is not perfect, I remain convinced that handcrafted will always beat AI generated crafts. The IKEA vs the carpenter analogy fails because a carpenter has to create each piece of furniture from scratch, serving only a single customer, where digital products by definition are near zero marginal cost, so it is worth it to throw large amount of human hours at proper code vs AI generated code if the quality is better.
PS: You have intrinsic value, and your skills will also remain valuable, if even for how it teaches you to approach complex problems and think deeply.
The feeling I get is that they haven't earned it, that they've not put in the years to learn it and now they get to make things. I spent 25 years programming, from 2000-2025. I always thought that the number would keep going up, one day I'd say three decades, four decades, but I've stopped counting. I don't program anymore.
I started using GitHub Copilot in the beta in 2021 ish, where we turned comments into lines of code, then functions, was there the night ChatGPT dropped as a free preview in 22, trialed cursor on its first release, all the way up to now using both ChatGPT & Claude CLI & apps daily. My slowing down of writing code happened gradually, but from copilot I was hooked, I could do more, quicker. And now, I don't write any code, I just build the systems around agents & processes.
I'm okay with that because my thought has always been that we bring value. If we don't have to write a single line of code to bring an org value, we're doing a great job. And now that's almost true.
The people who are upset by this change, in my experience, are all the people who would answer that a programmer's job is to write code. The people who are happy about this change, are those who would answer a programmer's job is to produce value.
In a way, I think you're right, was it always just about the power & compliments for some people? The ego of being able to do things they made them seem like magicians? And has AI broken that stranglehold?
My mother plants tomatoes in her garden. She invests a lot of work into them, only to get a few tomatoes a year. Clearly it is not an economic effort; clearly she is doing it out of passion, not for the actual value of the tomatoes.
However, imagine the plants stopped yielding tomatoes, and would never do so again. Would my mother continue working on her tomatoes? I do not believe so.
I believe that even if you are doing a craft purely out of passion, it is still important to gain value out of the fruits of your labor, be it ever so little.
So maybe the extension is that professional SWEs who work at big corporations will need to use AI to 'keep up', but hobbyists can still get enjoyment out of their own work at hobby scale without using AI (similar to the point in TFA).
"Some people like writing books. Other people wish they had written a book."
People who don't enjoy the craft are not bothered by AI and will replace manual labour with AI.
There's nothing with that, but what I don't enjoy about this recent discussion is the assumption that anyone doing things by hand is wasting their time. "You're gonna be obsolete".
But that was the reality before, with the stream of criticism directed at people writing game engines, of doing new programming languages, new web frameworks, or anything new really.
Conversely, those who like writing aren't always about the reward (being an author, having a book published) but those who would like to have written a book regardless of the writing, often are.
Interesting mix.
Meaning, I think, besides utilitarian one-time, one-purpose scripts, programming is essentially an at least potentially social activity, there's always a potential social horizon to it.
I think in the end everyone will be happy. Those who just want to ship, make money and attain status and do not care much for the process will embrace whatever capabilities AI affords them and move on.
Those who get satisfaction from the process and prioritize craftsmanship will also do so and form their own subcultures where this is appreciated.
If software is eating the world as some say, then surely, there can't be just one way of doing software.
Maybe I enjoyed the compliments, the stars, the glory, the God status I always imagined will come my way but never did. Except burnout. That did come my way.
A good question.
Generative AI takes away the grind, which takes away the learning. How do I master a new language if I'm expected to code via an LLM from day 1?
It's also well understood that the act of writing is when thinking actually happens. You have new ideas, opinions form, and so on. I think it's the same with writing code. But when you're not writing code any more, you don't go through this process.
I wonder if an LLM-authored project would even end up solving the same problems that a human-authored project would? If a human didn't write the code, then a human didn't have the chance to think in the same way. They didn't spend time trying to think of a good variable name, which made them realise the whole premise was wrong...
My assumption was that being closer to hardware tends to be more resistant to AI hype since they work in environments where just vibe coding some slop carries much higher risk than vibe coding a webpage or mobile app does.
As part of learning how to work with coding agents, I had them code up a bunch of games that had been in my head for years. They were never going to see the light of day otherwise because I have too much on my plate, but it was fun to make them come to life. I didn't do it for money and it's not my day job nor will it ever be but it was educational in learning the limits of Codex and Claude.
But the app stores have been hosed for years ever since the Zynga playbook and DLC. And on Android, if you release something honest and original without those things, it will just get copied and re-released filled with malware. So why bother?
I don't really miss the old days because despite all the nostalgia, engineers were really underpaid relative to equally difficult professions and they usually got terrible shares of equity compared to the C-suite. And has everyone forgotten EA spouse?
https://ea-spouse.livejournal.com/274.html
Now I'm not saying AI can't write ASM. I'm saying that compilers have a hard job. They output bad assembly, because the task is difficult.
That is, how long at the current rate of progress until it's undeniable that properly-engineered agential code is as good or better than hand-written stuff? Is all code made exactly the same because of heavenly decree, or can agents help write unit tests n such? If you insist that regularly writing C++ files directly is something special that can never be effectively automated, isn't it a little weird that you just happened to be born just in time to pick up on the very last iteration of software engineering?
*TL;DR:* you're inventing an imagined enemy who hates thinking and joy, unlike the noble, serene folk who choose the hard, true, right way. And that's a really antisocial and isolating thing to do, when it's based on nothing.
I am convinced that AI will be the tool that creates abundance, but that doesn’t mean human engineering is automatically irrelevant either. AI has already surpassed what humans were able to do, for instance solving certain math problems. My point was mainly that engineers are forced to introspect, and that includes questions about identity, what it means to be human, and the motivations behind their work/hobby.
There's also room in the middle, and people who are nowhere on the scale, that just like getting paid.
This would be the more charitable take than your TL;DR
This is more or less precisely how I feel. Other creative fields have already begun to get a handle on how AI is a soul-deadening thief of joy in their fields. I have hope for illustrators and painters and photographers and musicians and makers. With those friends and in those communities I see people who have already done the thinking, can already express their feelings, and are already making commitments to do work in ways that defend them.
The software development industry has still to reckon with the extent to which it is punching itself in the face, and it is precisely because AI does have at least some utility.
I think industry is quite clear that AI is helpful to their bottom line. At the end, that's all that matters to them. That SWEs cannot, say, unionize to prevent this shift in labor-elimination or articulate any other coherent way of countering the industry's desire to push forward with AI-assisted coding, shows me that there's an understandable desire to preserve this golden egg of being a high paying SWE. But that ship is setting sail, and becoming rarefied.
I was broken long before AI. I learned that no one was interested in my doodads even before generative AI. People were interested in all this other stuff, like ROI, how much money things make, how practical something is, etc. "No one cares about the code" was beat into me 10-20 years ago. Big ups to Joel for making it this far.
Today, I like it even better. It's never been so fun.
What would have taken days of work, if it was feasible at all, I can have implemented in half an hour now and iterate on the result to make it work the way I want.
I stopped reviewing the code at all.
People on here are often saying how that's a disaster, how the result would be unmaintainable, and so on. I think they are clueless.
My app has 200k LOC + 100k in tests, and there is no sign of the AI slowing down or being unable to maintain it.
I've been working on the project for four months now. I invested hundreds of hours, and I expect to publish my paid app in the AppStore this month.
It has been fun. I am using the app every day and I look forward to the features I will add in the future.
May I ask what does this app do ? 200k is like GTA vice city level, is like sqlite level, If its a financial tracker or a to-do list or an agent coordinator I am going to kill myself
Call me suspicious.
This means you designed the system well and made sure the agent implemented it correctly. Even at Big Company the big shot architects don't review every line of code, and nobody seemed to mind that
Sure, I've given a lot of inputs over the time, probably I've steered it to solutions that work.
Maybe it was also helpful that I set up a skill to use a different model to review the code for correctness, technical debt, and whether the location where the code is added is appropriate or warrants a new file or abstraction. I set this up long before subagents were widely used.
But even if they could the best thing they’re ever going to do is reach the sum total of human knowledge. I can’t ask it to think of a novel algorithm to speed up my flows, and even the places where I feed it a literal paper and ask it to reproduce it in a production ready matter are often exercises in patience.
That said, for me it’s better because I like thinking of ideas far better than typing out code for ideas to become reality.
From my experience not iterating enough and leaving high level decision to generative IA yield shit. Maybe this is not the case in all projects. But in my work, it would be absurd to complain about not having to know random API details anymore, unless when they actually matter.
The thing is that I’ve been programming for more than 30 years. Maybe I would have another opinion if I was still learning the things I was learning 20 years ago.
So much this.
I don't understand how some people seem to have no self awareness or shame in saying "I build X" where "X" was entirely prompted by an LLM.
It's like ordering a meal from door dash and calling yourself a chef.
What’s intellectually “mine” is the task anyway, not the code.
You should be able to strip all the creative intelligence out of the code and what you’d have there is a prompt.
A related discussion I saw before: https://news.ycombinator.com/item?id=49340013
Recently, a couple of very talented engineers vibe-coded a cross-platform app that is nowhere near as nice, but is highly effective at the most important aspects of the one I wrote. They are also very good at promoting, and it will get a lot of press. I have no doubt that many folks that would normally use the app I wrote, will use that.
At first, I was all mopey and emo about it, but I realized that it doesn't matter. Their app is decent. It's fairly ugly (LLM-generated UX is pretty bland), but works very well. The guys behind it, are good engineers, and I know that it will improve (although I doubt their UX will, much). Neither of them is a native iOS or Android developer, though. They are backend folks.
Instead, I'll be doubling down on making my app as good a native experience as possible. There's still a lot of stuff I can add, and Apple keeps adding more capabilities that afford native implementation.
I have also been using an LLM as a "trusted advisor," not as an employee. It's made a huge difference. It may end up eroding my "hands on" skills a bit, but not by that much. I find that I am constantly reviewing the work it does, and my knowledge helps me to really get the most out of it. I managed a software development team for a long time, so I am pretty familiar with delegating work to employees that are actually more capable than I am. I guess that helped me to accept LLMs, as an IC.
I'm basically looking forward to this. One of the reasons that many of my apps don't have a lot of new features, is because I never had the time to study and implement them (I refuse to add bad stuff. It needs to work well, so I am picky about what goes into my work). With an LLM, it looks like that is no longer an issue.
Start to write. Or continue to write. Or consider writing as the place to explore and develop your ideas. They're just words. There is even more freedom there to create. Not restricted by a compiler. Not restricted by the shape of the final product. Words can be written anywhere. Sometimes on a paper, even. On my phone while strolling and ideas pop up.
Give it a go!
Neither natural-language-writing nor LLM-prompting does give you that.
1. It is great to see an effect of your thoughts, like something happening in the real world. 2. Coding offers a feeling of perfect control due to the deterministic nature of code.
I would argue that 1 is still the case with LLMs, and 2 was always just 95% true, never 100%, because of oversights, bugs in libraries, and what have you.
So what actually decays is maybe not so much the feeling of self-efficacy, but the feeling of control, and even this is a gradual change. Perhaps it would be less unsettling if it didn't happen at the same time as a potential loss of control in other areas: career, salary, mode of working etc.
Very unlikely to apply to any job moving forward (i.e., they've equated AI with a competitive advantage, even if the results are not technically competitive), but a job isn't you and you are not a job. And if you're like me, where building stuff is your business, I highly recommend using your skills to build something that makes money (without freaking out about how the thing is built) and then use that to pay for your life and work on code however you'd like in the off hours.
Frustrating? Absofuckinglutely. But you can either spin out or keep progressing, however slowly. My wife and I have been talking about a growing renaissance movement as people where we live (normal, everyday people) go in on other locals for using AI for stuff. Just saw one on Reddit the other day where a local venue got chewed out for using AI for their event flyer.
That doesn't mean AI goes away or everyone "wakes up," but it does mean that it's not this universally loved thing. I personally think that will be the shape of the future too: some places in the world will be all-in while others will opt-out. If you truly want to be a pure craftsman, it's worth looking for where those places and people are and consider relocating. Environment has a huge impact on your ability to think well and clearly; don't underestimate proximity to AI making it seem more threatening than it actually is (and don't just dismiss that as delusion or wishful thinking).
Also don't forget: the economics of AI are unhealthy and this first wave of AI will likely be washed out, followed by a "plateau of productivity" for a few survivors (think how the internet looked from ~2002-2009). Again, just my opinion but I don't think the overall outlook is terrible if you don't allow yourself to be disconnected from your craft and find others who feel the same.
Also tried it with AI generated art. Is not there yet. I can generate a beautiful image but then cut it to pieces so I ca use it in a game breaks apart.
It can be done but it looks obviously underwhelming.
And I think this is really the best of both worlds because AI coding works best when you give it constrains and without my toolchain the AI is generating crap code I wouldn’t ever want to read but using the libs I wrote and know I can constrain it to write decent code that works “at scale” . The more opinionated the tools/libraries the better outcome you can expect.
Another great usage of AI is for refactoring. Before AI you could have a great idea how to make the library better/more ergonomic but the sheer amount of refactoring would make you just eat the debt and basically live with your own “slop”. Now with AI you can produce the reference design for the refactoring (I.e let’s make all these functions actually methods) and the job is done in minutes/hours. This inevitably leads to better designed software.
I agree with your point on refactoring / porting. Retro consoles and homebrew will see growth, probably.
So, a very long blurb to simply say that you can avoid using genAI and just do things "the hard way". And why? Just because he wants to do it.
Frankly, I was hoping for a deeper, more interesting conclusion.
Pretty much this. There was a lot of build up in the first paragraphs, only to conclude something that, at least in my view, is remarkably uninteresting.
AI is a great editor; I can finally do all the refactors that I wanted to do that were much harder before; would have taken a long time.
AI is great at writing tooling, I love a good tool that gets the task at hand done; encodes a task that others will need to do. Couple that with a skill file and now a fuzzy tech debt migration can actually be completed across many teams at there pace.
I focus on the cheapest model/fastest model (been using Luna). I use pi and don’t try to multiplex my time, and stay in flow on a specific task till it is done. And I’m very happy with this, actually enjoy this more. Vim skills stay useful for editing the prompts/module structure/fixing slop code during review/ and review.
The volume of code is high so reading a diff is suboptimal for review; so I tend to review from local checkout using vim (LSP tooling important during review, go to def, etc).
And then generative AI arrived and suddenly, unless you’re generating the maximum amount of code in the minimum amount of time, you’re going to fail, you’re going to be left behind, programming is dead, do the easy thing, generate! Generate! Generate!
We are years into generative AI and still there is no fundamental change. The most successful businesses are still the businesses doing something well, not businesses doing things easy. Spending hundreds of hours writing every line of code by hand isn’t a competitive weakness, it isn’t foolish, if it creates a good product.
So, I agree, fuck it, type your code line by line. Users don’t care if you spent 1 hour or 100, they care if your product is good, just as they did in 2025, 2020, 2015…
Maybe you’ll get beaten by someone generating a million lines of code. Just as maybe you would have been beaten by someone who typed faster than you in 2020. Nobody worried about increasing WPM in 2020.
But my purse does, as do my investors. I can no longer justify taking a hundred hours to build a product, even if that makes it materially better than that of my competitor, who spent one hour to build theirs and used the other ninety-nine to sell it.
I don't like that either, but it's the reality we live in now.
This reminds me of a different theme in the programming world.
There was always a feeling that development spends time on meetings long past the point when the app could have been finished. And I remember a comment here on HN (which I can't find now) saying how, if you're on a team at IBM working to develop something for a client, you will feel that you could just go ahead and finish whatever functionality you're supposed to be developing.
And if you sneak in after hours and do that, you'll be met with the message that you aren't being helpful, that you've got to wait for the business to determine that that functionality really is what the client wants, that the app needs to be described a certain way to get signoff from other decision makers, etc. Anything annoying that you can imagine.
But the overall takeaway that I saw was that developers tend to be frustrated that business processes are slower than the act of producing the software, and they feel held back by that.
Given that background, it's not clear why generating more code per unit time is valuable at all. That's something developers wanted to do all along, and they were told they shouldn't. More code per developer would make sense, but why more code per time?
This was never true, otherwise "stealth startups" wouldn't have been a thing.
Generative AI is really awful at building games that are fun to play.
It is a masterclass at reproducing Minecraft clones and shiny HDRP demo scenes in one shot. But, unless you are a total novice at game dev, you should be able to see through these cheap tricks for what they are.
99% of the game dev AI doomer posts seem to spiral out of vacuous demos posted to social media. None of this AI generated slop is actually playable or marketable.
I just got done talking to chatgpt about progression sequence for a horror game and it is beyond hopeless. It would absolutely ace any mono behavior scripting, but it's totally ass at directing anything that would make it to the front page of Steam.
That obviously still leaves some space for the occasional streak of creativity or very talented game devs, but that is by and large just a tiny sliver of the industry even today.
Indie and non-triple-A studios keep having wind, because they’re the ones producing interesting and fun games which people _actually want to play_.
It's one of those platitudes that everyone knows, "the only constant is change", but everything feels like it's going be forever anyways.
Your parents will live forever. Your kids will stay young forever. You'll be at this job forever. You'll keep doing this routine you did this week forever.
Quotes, or advice, or history books are just too abstract until you live though them yourself. Looking back at all the history books I've read, I realize that this kind of magnitude of change is the norm. The Industrial Revolution. Colonialism. North Atlantic slavery. Chinese famines. War. Plague. Economic Depressions. To be honest, this is pretty tame, now that I'm making this list.
Nobody thought that the entire industry would just be totally upended in such a short time, but here we are. A job that came into being just a few decades ago disappears just as fast. It happened to all kinds of jobs over the past few centuries, and it'll keep happening.
Time to get back to typing, "Do my job" over and over in a chat window.
Then there was a time when the "workforce" was mostly actual slaves.
There was a time when entire cities all died of sickness, 100% mortality.
Yes, more change has happened. And more is coming. Just how it is. The post WWII era was the exception. Ride the wave.
Also I think the quality of the models has made a big difference to my attitude. Until Astra they were kind of "meh, a junior engineer could do this but I wouldn't be happy with it" but with Astra I feel like it's reached the point where it's competent and it just lacks taste in some ways. It's even done some clever things that I might not have thought of.
Work - max adhd no brakes cat stand dog stand satellites.
Honestly loving software engineering right now. The age of magic incantations and magic meat is over. I’m the wizard now. We all are.
And it’s awesome.
I didn't go to school for CS or adjacent: I went to art school 20 years ago for 'new media' which feels like a _silly_ thing to have on a diploma in 2026.
My career started in high school and ran this way: print design w/ computer geekery on the side -> classes in all sorts of digital media production methods -> web design -> web development -> full-stack development w/ a UI/UX focus -> engineering manager ? -> engineering director ??
Then Claude comes crashing in a couple years ago and suddenly code I would grid on to get right got easier and easier to ship. I have enough _experience_ to know not to trust it, put in the appropriate guardrails, and now we can deliver work at a velocity that makes more people happy and keeps my team grounded in a reliable 40hr workweek.
Back to power tools: I'm done going to READMEs and docs and learning the order of operations to build with a hammer and nails. Turns out I didn't really _love coding_. The Job To Be Done was to build the app/feature in a way that satisfies business and user requirements, can be reliably maintained over time, and is securely integrated with existing systems. The tools are now fully-automatic instead of semi-automated with IDEs and linters. Turns out I just like delivering product that solves business objectives (working on turning that into a bigger thing).
I'm still functionally the Responsible Party that gets in trouble if things break down, and its been a couple years of codegen entering our repos and things haven't broken down.
I'm using the lightness of mind the above now provides to find space for the things that strike me creatively, like I did when I was younger and more into art and music. I'd rather spend that creative juice elsewhere, not coding.
So I'm sorry to the coders who love the craft and feel like the industry is slipping from them. Like many industries that have started as craft, code has officially entered its mechanization phase. It requires less finish carpenters who know how to work a coping saw and more general contractors with the latest 18v line of tools.
There's a bigger audience of businesses and consumers that want solutions built quickly, reliably, from a trusted party with experience than there is for tailored code.
I don't mean for this to be discouraging. I really like photos OP took in this piece, and that NoAi camera app looks really great! I'm sorry there's no profitable market for it, but I'm glad it exists! I feel like the skills that created that app belong at an Adobe or an Apple working on creative tools where they can afford to hire someone to work on just single feature or idea.
I wish there was more opportunity for everyone to do work that brings them good brain tingles makes you feel the most human you can be. "Fuck it, make it anyway" is exactly the right attitude rn if you can afford to do it.
It's also a little disheartening for me to see people crashing out about philosophy of aesthetics at a time when I'm terrified of grey goo and killer drones, but that's more on me than him. I'm not exactly doing much to prevent it either, so staying on the previous societal crisis seems defensible!
On the (well written!) post's particulars:
I can't help but feel like this attitude is... "myopic" is too far, but perhaps... intensive? Namely, it seems to be treating the contemporary craft of game design as some hallowed pursuit that artificial claws are ripping away from us, when in fact I'd argue it's one of the most recent and most rapidly-changing SWE subfields around. Yes, a lot of the skills he learned will be useless. Yes, that is inherently embarassing and anxiety-inducing and enraging, and no, none of us saw this coming (don't believe the scruffies, their fingers were crossed up till ~2018, too!).
But is a world in which video game designers get to make higher quality games faster really such a bad one? I've felt frustrated with the scope and polish of AAA games for years, and the quintessential indie dev story involves way too many years of toil.
Of course that falls apart if you assume that involving neural networks at any point in the process necessarily leads to worse outcomes, but... well, don't? That's clearly just a dogma, so either open it up to actual scientific experimentation or just adopt a different, more reality-amenable dogma. Living life as an anti-AI purist (or Luddite, I say with the utmost respect for King Ludd) puts you in a cognitive place where the soul of humanity is under seige by shadowy, chrome figures, and the only way to get to a healthier place is to examine that assumption.
Like, clearly, software made with Soul and Taste and Intuition and Experience and Consciousness can still be published -- and I'm glad the author and his friend are doing so! The threat is that they might not perform as well in a marketplace ruled by capital, but, I mean... did they ever? Writing your own game engine in C++ was already the equivelant of going to university for Tuba, or striking out as a full-time landscape painter; it was mostly for the children of the rich.
*TL;DR:* Would a radical shakeup of the video game world really be such a disaster? Assuming we aren't just assuming a disaster, that is.