FR version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
71% Positive
Analyzed from 16405 words in the discussion.
Trending Topics
#code#don#more#things#llms#doing#still#software#art#thing
Discussion (236 Comments)Read Original on HackerNews
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.
I think it's the opposite. When I'm on the edges of Real Difficult Stuff (TM), then LLMs are less of help compared to when I just need basic web applications or similar "beginner stuff". If what you're working on doesn't exists in the training data at all, the LLMs can sometimes be more in the way than helpful, as they don't seem to even "grasp" the problems correctly.
I still get tons of productivity boosts from LLMs, don't get me wrong, and I wouldn't stop working with them even though they aren't perfect for everything, they do with a lot of monotonous tasks, like all the stuff you outlined. But the moments I'm working without LLMs, that's the time I'm working very much on "not beginner stuff".
I very actively work using LLMs (no “agentic” stuff) and agree with you - they are only really worth tasking out tedium to.
But a lot of - say a DM feature - is tedium. Something simple like adding reactions, adding read receipts. It’s not hard at all. The LLM easily excels at the task and yet I didn’t have to do it. There are 1000s of those tasks. Handling file uploads, filling out a W9 and emailing it to the user, cron jobs for digest emails. All very easy problems most LLMs can do. There are just countless tasks if you’re building a real SaaS and I don’t want to do them all.
The big problems LLMs can’t do are only as such because there’s no way to put it into a simple, linear instruction. Once you can though, it’s now an easy task (whether or not you use an LLM).
But yeah we’re saying the same thing - let the LLM do the 1000s of tedious tasks you normally wouldn’t be bothered to spend time on.
Build the entire SaaS (which is mostly that tedium) instead of just the MVP thing you need without any niceties. I find it opens up more opportunity, like for example, we are about to hire our first full-time employee because we’re taking on so much more business.
Yep.
Plenty of products attacked this tedium from different angles, from Ruby and Rails to Supabase. And half of NPM. Heck, more than half.
LLMs are doing it a bit better, IMO. I don't have to rewrite the app in <whatever> or install <horrible dependency> to take advantage of it.
The agents are building all these small features, up to a full SaaS; and all the code is excellent?
How much time do you spend in code review?
"Make me this thing there are a million examples of" vs. "make me this unique thing in this exact, particular way".
I don't think there's anything an LLM can't write given enough direction. (It's a one-sentence fuck-it one-off on one end of the spectrum, and it degenerately ends with you giving it exact code and prompting it to echo it back to you on the other.)
But the jobs of making basic apps and web pages are the new WordPress jobs in terms of pay, I'd agree.
The danger of vibe coded SaaS:es isn't the customer building the thing themselves, but that the increased competition drives down the profit margin.
Reasonable thing was to pay $39 and forget about it.
And I think the people it doesn't appeal to, I think we need perspectives like theirs.
> LLMs
It’s probably worth doing a very thorough audit of how you’re handling user-uploaded files, it’s full of non-obvious footguns.
Just what the world needed. 100s new SaaS churned by AI.
I'm frankly tired of SaaS.
You might not care about making anything or getting customers but this is HackerNews so get used to people like me
Has someone gone and made 3 accounts to make it seem like their take is more popular?
I see you are a self proclaimed “babysitter for devs”
I think if you made more stuff you’d be happier, and you wouldn’t even feel like you need to attack people online haha.
Sad man, I can’t imagine putting myself out there negatively like that with ZERO accomplishments like that!
There is an epidemic of high rep accounts here who never made anything.
I find people that are the "unconscious incompetence" stage of software development absolutely love them because they produce output that looks fine to them and they can't find anything wrong with it because they simply lack the ability to perceive quality. For a contact widget that might be acceptable as it will be used a few dozen times so who cares if it breaks, but let's not pretend you can actually build a compliant e-signing or invoicing software without having domain expertise and investing a ton of editing/revision time.
Put more bluntly, a domain expert that, as of currently, refuses to use LLMs can easily start using LLMs in their work, an idiot who uses LLMs cannot easily become a domain expert. Now let's think about who you would rather hire or who do you think will have the better future career outlook. Pretty damning how many people here are willing to reject the idea that domain expertise or ability to write program code yourself is a waste of resources.
Worst people here
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?
In my opinion, that’s not the whole thing and the article and the parent post touch on this. The part about the process of struggling to get your mind to understand new ideas and new ways of doing things, the satisfaction in putting together a solution that fits in just right and gets the job done. The feeling of goals accomplished and having improved oneself. These are things that are still out there, and the work is still valuable.
The difference, for me, is this constant background conversation that seems to be saying “this is worthless” and “you’re wasting your time”. I don’t think this is true but it’s hard to hear. Depending on where a person is in life, it can hit pretty hard.
It feels to me like suffering through programming built that knowledge, and so that knowledge was an indicator of taste and experience and persistence, but then it became cosplayed as people sought the knowledge itself in "patterns", or "features" rather than the experience of just building things.
The LLM thing just cuts the same way. It's probably not using your favorite pattern or language feature, or maybe it automatically is, but either way your annoyance is about it stems from the quality signals being discounted: You can't really assert experience through that kind of knowledge anymore if people are providing value while stepping around your hard-won lessons and using your favorite pattern or feature through LLMs. You saw this in the linkedin posts early on: All the programming influencers asserted their value by saying they wrote better quality code than the code the LLM wrote.
This is worst for junior devs. Making a clean, well factored codebase as a portfolio project was a near-instant win on the job market because it meant this person either suffered like you did, or they listened to seniors and walked the walk. That signal is absolutely gone now.
I think that dilution of signal explains almost all of the jr hiring freeze, actually: https://jodavaho.io/posts/ai-signalling.html
What I also think they are thinking (because I am one of them) is not that we can produce value easier and quicker. It's that there's a devaluing of education and expertise to the point where organisations will become wise to the fact that you're able to produce much more quickly because you're just relaying what they want to your prompt. And because you're doing it on their time, can just copy your processes, get rid of you because they have their own ideas. (For personal projects and entrepreneurship this isn't applicable)
Let's take an example organisation with a team of 10 Devs. In the short term, they'll be able to build and provide value to the company and they will see the power that AI can bring. But with time they are now finding it harder to compete because everyone can build similar competitive services. So they try to reduce head count and those who control the purse are often not the devs so they reduce or remove the dev team because prompt engineering has gotten so good that they don't need your expertise anymore, they'll try it themselves.
So in the short term the organisation has all 10 devs producing a bunch of output. In the medium term, the company headcount can shrink because you no longer need to be aware of what is happening under the hood.
But because every business has this realisation, everyone will have the same ideas. So it will be harder to avoid being copied by competitors because ideas are no longer gate-kept by effort and expertise. SaaS will decline, in the medium to long term because you can vibe a replacement, in the long term the open models get good enough that the OpenAIs of the world aren't needed so the moat goes to the Nvidias of the world, then the hardware design can be automated/vibed, so the only moat is the land and raw materials. The manual labour will get flooded with knowledge worker refugees but that flood will probably force costs down there too.
In summary, I think they are mourning the feeling of being an expert and doing things others cannot, but I think more strongly they are looking at the "value" proposition and not seeing how it's sustainable.
I think both sides agree that building is much easier like you have articulated really well. I think they just take it a few steps further.
30 years in tech, programing and I have the complete opposite take.
My lawyer and writer friends asking me about containers and cron jobs is fascinating. These people are fulfilling the old promises of VB script, AppleScript, IFTT and all the drag and drop coding tools that we have ever created. For the first time people are bringing me the "hard" technical challenges rather than the "I have a startup idea" or "can you fix my computer" type questions.
> The people who are upset by this change...
Are the ones who view their responsibility as code and system ownership. Where they feel smart because they know where the problem is when they hear it described. That isn't the job any more - and the people and the tools have not caught up.
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.
The correct analogy would be, your mom can also just go to the supermarket and get much cheaper mass-produced tomatoes; which is… exactly the current situation?
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).
People didn't stop solving sudokus when sudoku solvers appeared.
"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.
Used to be you had to calculate things by hand on paper. Then we got calculators, then spreadsheets. Complaining that by hand was better seems line nonsense.
I'm old enough to have taken typing lessons in high school on typewriters with real ink and needed to use white-out to fix things and if there are too many mistakes having to start over from scratch. I don't want to go back.
Construction went from using a tap-and-die to make your own screws, now CnC machines, 3d printers, power drills, etc....
LLMs to me are just another tool. They help me get what I wanted (an app, a game, a web site). I'm still directing. It's still my idea, with the features/look I want. My design choices still make the end project.
I really don't get the hate.
Was I proud to write my own linked-list library and red-black tree system in the late 80s. Sure. And yet I was much happier when it was just a built in part of the language.
I'm really happy I can draw something in a drawing program and not have to sketch it on graph paper like I did in the 80s and manually convert the image to hex codes
Each step removed one more piece of friction.
I'm not trying to tell you what to like. If you like certain activities be my guest. I like to cook sometimes even though ordering out would be easier.
All I'm saying is I don't get the hate that something got easier. We have 1000s of examples fo things getting easier horses -> cars, wagon -> trucks, ships -> planes, oil paints -> photos, math -> spreadsheets, etc... So LLM made yet another thing easier. If you didn't complain about those other things getting easier, why are you complaining now?
---
I find it interesting there's a post about inverse kinetics which is could be argued is "how to automate animation" or "how get rid of animators" or "how to make lots of animation less tedious" It's celebrated. Yet LLMs doing the similar things for coding is derided.
Tedious animation is something that animators I worked with also hated doing, and they were always after tools to accelerate their workflow, so they could focus on the high-level decisions.
I've also used and built lots of refactoring tools. I've been fanatic about them for decades.
Using LLMs for that isn't that different, maybe it was a bit less deterministic before, but lately... holy shit, they've become good at it.
But the "animation is dead" discussion would still bother me if I was an animator.
The inspiration, the ideas, the workflow, the vision, the end product - all mine. The grunt work that takes all the time - hand it off to the LLM, and make sure it bloody works at the end.
With that approach, I built a compiler for my own language - it runs on {Mac, Linux, Windows} and any of those can produce code for {Mac, Linux, Windows, WASM, iOS, Android, Zynq, m68k, 6502} - the last 3 being more useful to me than most people I expect. I have a signed binary running on my phone, which was developed on a Linux box and never saw anything from an Apple Xcode installation...
That compiler was how I (and Claude) wrote a WASM client to a server back end, all of which use the exact same classes and data formats, making integration trivial.
I'm working on a cross-platform UI framework now, with a Cocoa-like UI description, that you drag lines between your code and the various UI platforms you want to support {Desktop, tablet, phone}, with mobile variants offering portrait and landscape. Write your actual program logic once, and visually connect UI into it, on a target-by-target basis. Support any platform with one codebase.
I wouldn't have considered taking on a program of this complexity without the LLM. It'd just have been a pipe-dream. They're tools. Wonderful tools, but still tools.
> I really don't get the hate
I hate that you are reducing my craft to just the end results and nothing else. No value in my expertise or knowledge, all of the hours slogging through blog posts, IT forums, stackoverflow and technical pdfs and you have reduced that to "well what can you build for me?"
It's not just you, your attitude is very common, what else am I supposed to do except hate it? Just shrug my shoulders and smile, like "hey I just wasted 25 years of my life on pursuit of mastery of a skill that now has zero value to anyone?"
I wish I could press a button and erase everyone who thinks that way from existence. How dare you devalue my experience and passion so offhandedly and treat it like I'm the asshole for being upset by it.
On top of that there's the "did you enjoy the craft or did you enjoy the compliments" framing. Are people who use pre-existing libraries just fishing for compliments too? No, of course not, they're making a cost-benefit analysis and deciding that certain tasks are better off delegated rather than repeated by hand. Same goes for choosing when to use AI. Not everything in every project justifies full human effort, regardless of how much those humans enjoy their craft.
Many of the other replies have referenced the arts, but I think a better example would be research. Scientists have constantly been in a position where improvements in technology shift the nature of their work without being able to change what they fundamentally do.
They might enjoy the art of manually calibrating an instrument to extreme precision, but ultimately their craft is to do research. If the auto-calibration is going to be sufficient for their experiment's needs, there's no reason to waste time doing a manual calibration. Yet, not requiring extreme precision does not mean the experiment's results have no scientific value, nor does it reflect on their dedication towards their craft.
Can't speak for the OP but I definite care what my code is supposed to do. :) The last little program I wrote was a 40-line thing to compute my estimated quarterly taxes so I wouldn't have to launch a spreadsheet. It had better work right!
I could have used an LLM to write it, but that would have been boring as hell.
Got no compliments for it. No one has even seen it. I don't care; it was just relaxing and fun to code.
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. Just like with any other activity that aims at a work.
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 bet people generated solutions end up significantly different from AI generated solutions. People learn more about the problem as they work it through and they don’t always end up with the thing they were imagining when they started.
I think others need to embrace that too. Your work can be fun, and can be a joy. But that shouldn't be folks only outlet for themselves to measure.
At one point in my career I was ONLY reviewing and guiding off-shore contractors. It felt even worse than LLMs. But I did enjoy it though, but going to LLMs didn't drastically change my workflow. LLMs feel like leading a bunch of juniors with no real stake or business context.
So for me it didn't fundamentally change things, it just meant I could steer the progress before a PR is created later in the week that misses the mark completely.
There were plenty of other issues in the software development business that sucks the soul of creating out.
So I think you asking the right questions. Cause I felt like I've asked myself those questions even before LLMs.
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.
If I switched to spending more time on the hobbyist craft, I would pretty quickly have to give up doing well at the job. And the parts of the craft I enjoyed the most are the puzzles around distributed systems and high-scale correctness, which tend not to come up in the hobbyist context anyway.
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.
It won't, they'll just do analog recordings and remaster them with Codex, but it's pretty clear that anyone who finds a market inefficiency here will find that inefficiency addressed forthwith to keep the casino rigged in favor of the owners.
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
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
You might not be aware of this, but you've answered the question - just indirectly.
Call me suspicious.
I don't think I am less of a 'hacker' or programmer than the next person on HN.
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.
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 in software, precisely because some of the final form necessarily a cognitive 50% grey, even just for interoperability alone.
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.
No, I think the industry is hopeful that AI is helpful to their bottom line.
I don't really think there is very strong evidence that the ROI is good.
The problem is that the industry is riddled with FOMO and FUD: everyone thinks everyone else is using it so they must. And this FUD and FOMO is being imposed upon them from above: there is a mandate to be afraid and fearful you're not using AI enough.
Even I, a burned out freelancer who once used to be happiest writing code, have to accept that if I return to my career, I must develop ways to use AI to keep up with people who are clearly already using it indiscriminately (or at best over-optimistically). And I must develop ways to talk to potential clients about the aspects of indiscriminate AI use that they should care about, and about the value of stepping back from one-shotted ideas.
I am trying to operate without FOMO and to see past FUD, but I accept I am compelled to do that or quit.
I think SWEs can't unionize for very different reasons, and that if you hang out on HN long enough you will develop a deeper understanding about why. But I am not restarting that discussion beyond saying this, because it always makes my head hurt!
AI use in creative fields is similar now to PEDs use in sports, except more ubiquitous.
No, I'm actually not. I'm an active creative portrait photographer and I take part in photographic communities with people much, much better than me, I am surrounded by dozens of gigging and working musicians, songwriters and composers in my friend group (and play a couple of instruments myself); I know painters and illustrators of great ability (though I am not that kind of artist).
I listen to what people say and I talk with them about how they feel about it.
> AI images make amazing collages/photobash inputs,
I fully, fully disagree. I think using AI images in this way — for collage or moodboard — is completely ruining the point. I do know some photographers who haven't yet figured this out, unfortunately, but they will. Letting an AI image into your collage or inspiration for another piece of work is just opting out of a creative choice; you might as well place a grey rectangle, because that is what it is.
> and AI music is useful to sample or use as inspiration for parts you're stuck on
AI music is not and cannot be inspirational. It's the absolute opposite of it. And serious musicians know it.
AI content might have some value as placeholder but even then you have to be careful that the prototype does not go into production.
I'm also aware of someone who used AI images to generate a series of test prints for her new alternative process printing practice, precisely to make sure that her test prints never had any accidental value — it makes it essentially compulsory for her to destroy them when they have served their purpose.
I have no particular problem with them being used as a more varied alternative to a step wedge like that, but the point is this:
AI generated creative works have zero value. Anyone who is seriously involved in creativity knows that even replacing something that is working against you with something that has no value either way is probably a bad idea. And putting out work that has this absolute zero value does you more harm than bad work.
It's way better to try and fail than not to try. Think for example of all the ambitious, earnest failures of movies you've seen; would any of them have been actually improved by AI?
> AI use in creative fields is similar now to PEDs use in sports, except more ubiquitous.
You were saying that you thought it was an "amazing" tool, and now you are saying it's like drug-assisted cheating? I think you still have some of the internal work to do.
The comment about hobby vs. work is correct, and it’s the crux of this.
OP is attempting to console themselves. “I shouldn’t have to change to avoid ‘falling behind.’ I like how I’m doing it. I’m good at what I do.”
The fact of the matter is the LLMs can be used to produce effective work faster than you. Yes. You are falling behind. And yes, it will reduce your value in the job market. Eventually it will be a dramatic reduction.
That doesn’t mean you must stop coding by hand, because you love it. But I don’t think you do love it. I think you love being praised for being smart. The pats on the head. That’s the most likely explanation for why your motivation for coding by hand has disappeared. Once the results stopped being a special output from your special brain, you stopped feeling special.
You have a choice now that the landscape is changing. You can find a way to produce unique and outstanding results that still matter, or you can slowly fade into a hardened stance of obsolescence and spend your time grumbling about the change.
I think you (and almost everyone in this thread) are missing an important point here: even without relying on external input on our work, we feel less proud of the work we produce by hand when we know we could have prompted our way there orders of magnitude faster.
If I build something cool by hand, and I enjoy the process of building it, then why does AI affect anything? The problem lies in how I feel about the final result. It feels fundamentally bad to know that however hard I worked on this, it would have been better, faster, or both had I used AI to produce it. I think it really is that simple.
'Quality' is a function of filling in the gaps of the new tools, not eschewing them entirely.
But I refuse to leave understanding the codebase to machines. I did that the other day as an exception and fortunately my reviewer picked up on things which weren't exactly broken - just redundant and inelegant - e.g. two variables which easily could have been one, passed between several methods.
We have an automatic reviewer as well and there wasn't even a peep from it regarding any of that.
And this is really the crux of the issue - LLMs won't ever create elegant and minimal code, because their style is based on the mean, which in turn is dominated by the work of people who shit out a lot of working, but write-only code.
Skills not exercised degrade as well, if you don't actually write code then your skill at reading and interpretting it degrades, you just become a "looks good" step.
In theory if disciplined enough you could resist that but our brains seem to take the lazy path whenever it is offered, thinking hard and focussing are a skill and one I don't feel is been exercised when using AI.
Before ~3 years ago, they are more or less similar to me: it's mostly pure creation and sparks joy and makes me fulfilled. I love working and it pays well, and my hobby improves my work skill. It's like living in the dream.
Now? I can "make it anyway" like the author suggested indeed, but only for my hobby. I don't think I can keep coding the old way during work without getting myself fired.
I guess there's no much to complain. Lots of people work only for a living. It's a rare privilege to love one's work. I should be grateful that I can choose to keep my hobby.
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.
For me it's more like being a chef but having a cook to cut up things and start cooking them, but you decide when it's done, what spices to put, and how to serve it - arguably the most fun and creative part.
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.
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'm an old systems programmer (embedded, c/c++, linux, etc) with an EE background (but not one of them if you know what I mean. I enjoyed software and appreciate the art). But early on I came to believe software engineering at a workplace is not your personal art project. If you want that, great, go write code on your own time(as many of us do!). But on the job I often get annoyed by folks who don't want to do the obviously correct thing, or want to fight against good refactoring or design feedback (usually not from me.. I'm like a 'B' tier programmer and in awe of the 'A' level I work with). People treat software as an art and while you want to be artful in execution, if you are a paid artist, it is a commission work. Honor the requirements of the company (business needs) and not just your personal feelings and desire to only make art.
The minute I also realized this, I moved out of software development into a different function. Pooping out lines of ugly code full of compromises was just not my thing. If I was still coding for work when AI came around, that would have definitely pushed me out of the career.
If I was a door dash driver or something, and I just wanted to get from A to B, then yeah, maybe I would ride an e-bike instead. But I like cycling. I'm not going to stop liking cycling just because someone made a robot that also can do cycling.
(incidentally, the proliferation of unregistered/unlicensed motorcycles marketed as "e-bikes" has done enormous damage to the viability of e-bikes as a general category)
I was planning to earn some money from my second Steam game. Than AI happened.
I did not gave up on because competition is now higher. I gave up because programming was fun for me, been at for 20 years. But right i always know in part of my brain 'this 1000 lines of code could have been just a prompt'.
Joy is not there for me anymore. I hope to get it back someday.
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.
I also made a image filter builder, hosted on the web so it runs locally, even though I knew that it was an over-saturated market. I saw those apps and decided to do better. It scratched an itch. Do people use it, or talk about it? Of course not - see above.
For both tools I did the initial coding myself, then let LLMs look at (but not change) the code so they could suggest areas for improvements. Engaging LLMs at that point, in that way, is fun work for me.
Just because things can do things faster, sometimes better, than me doesn't mean I should stop doing themselves myself. That's not a fun approach to life, for me.
Just an hour ago I made my most recent pen plotter generative art free on my website. I plan to send high resolution scans to everyone who joins my mailing list so you can print them at home.
In contrast with the author, I actually enjoy creating code with LLM’s. I’ve been on the technical management track, instead of boots on the ground coding, for quite a few years now. LLMs are letting me produce software again with limited time.
I still enjoy writing code by hand too and my generative art work is mostly that.
https://art.joeldare.com
On the game side, I recently created a Shut the Box game that runs in the web browser. This was created entirely by an LLM. In fact, it was the test project for a Dark Software Factory I’ve built.
I love that I can describe a project, from my phone, put it away, and have a prototype built a few minutes later.
The game is clearly unique and consistent with my own personal style. And, I’m enjoying playing it.
https://dark.joeldare.com/shut-the-box
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.
A related discussion I saw before: https://news.ycombinator.com/item?id=49340013
The attitude of just leaning into your creativity regardless is good though. I know a bunch of local metal bands that kinda suck, but they grind away at it because it's fun and they love metal, not for some hope of a future payday. They don't care if AI makes better music than them, it's a community/personal expression exercise.
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 bet if you set Astra codex against this task on the $100 plan it would have it done at a speed that would shock you. Potentially even by the end of the day and mostly uninterrupted.
The SOTA models can reverse engineer whole codebases even from assembly now. If you have to specify with words what you want to do it's still hard but if you have a codebase to work from, you can pretty much arbitrarily convert apps and games into other languages / platforms now as if by transitive property.
The issue is that I store user data. Also, the users of the app are a very privacy-sensitive demographic. That raises the stakes, considerably.
I can't just "vibe code" an app that does the same thing mine does. It needs to be vetted by a good native Android developer that I trust, and that gets expensive.
Traditional art is still valued. Good AI art takes time and effort and taste and usually some amount of traditional skills. And even some bad AI art is actually a good idea that needs a few talented friends to make happen traditionally - but no one can see the vision without the tterrible AI rough draft. There is room for all of it, and I'm sick of having to skulk around in the shadows with the things I've made for fear of tripping some Shrill Cancel Protocol.
And if you're worried about your traditional art job, organize; the people who want to replace you with AI will replace you with cheap outsourced labor instead, if you let them. AI isn't the problem.
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.
1 isn’t only about seeing the effects of your thoughts, it’s at least as much about transforming your thoughts into a more suitable, discrete and exact representation, whose effects you will in turn see. Having code as the intermediate representation that you work on, and that you work in terms of, is essential to both 1 and 2. Similar to how for a physicist, writing down formulas and working with them, transforming them, is essential.
The code is the language of thought, the model of thought, of what then gets reified as behavior at runtime.
I wonder what's the ratio of these 2 on Hacker News and similar spaces, many posts and comments seem kind of vague about this.
For me, it's mainly about jobs and money. If I was retired or in a safe job, I would watch all of this with excitement. Don't get me wrong, I can fully empathize with the other stuff. I love thinking, creating and inventing stuff that is high quality technically and UX-wise and makes people's lives better.
But at the end of the day, job and money is easily at the top of the "Maslow's hierarchy". I can easily have a similarly happy life without programming or without building products (I don't enjoy programming at work anyway).
Me: "Holy cow, LLMs are getting good. You should take another look at how good recent tools are because without them we're going to get left behind."
Them: "But I like writing code!"
Which is cool, but completely irrelevant in the context of a career. Write all the software you want. Paint all the pictures you want. Carve wood. Build a boat. Great! But in 3 years absolutely no one is going to pay you $500k+/year to do any of that and if you can't get your head around it you're going to have a bad time.
Idk folks, maybe it's because I actually don't like writing software as much as I thought I did. I'm realizing I actually like making products and creatively solving problems, and software is a mildly enjoyable means to and end for that. I also like many aspects of the job of programming (money, sitting on my ass, dictating much of my workday, feeling like a boss, also money, etc). I was lucky to be alive in a time when that role was in demand but I can now see that is coming to an end for at least 80% of us. Yes, probably you, and probably me.
Now is the time a lot of us should be contemplating our next move in life. Not easy given we're about to enter a period of utter economic chaos that makes the industrial revolution look tame. I'm saving money, building other skills and renewing my social connections.
None of this is a value judgement on AI. I'm not saying it's good or bad. It's probably both. I'm not making this statement based on anticipated future gains of AI. LLM advances could stall, token prices could quadruple. None of that changes the economics and the already existing technology that is sufficient to effectively end the role of a software engineer.
Yep, this is what I realised. I like solving a problem/fixing something. I am not really interested in hooking up a Go/Python/C# web service to a database for the umpteenth time.
I've been partially vibe-coding a new desktop environment for Linux and creating my own UI framework. I know how UI frameworks generally work, and I know how desktop environments generally work. What I want to do is build a DE that works well and fits my vision of how it should work functionally.
I am reasonable at C++ (I don't do it professionally). Do I want to spend 20 hours doing a load of UI boilerplate code in C++? No, I don't. I am sure I can do it, I've written UI frameworks before in other languages. But I get the machine to do all the boring stuff, and I develop the product. If the code it starts churning out is crap, I have the ability to fix it.
There seems to be a lot of crap about not being able to code after using AI for a few months. This is rubbish. I used to code when I was a kid in BBC BASIC and didn't for years, I then started coding again in my early 20s and all of the stuff I learned came back to me, and I was programming in Java. Same recently, I didn't program for about 4 months and had to program without the AI as the AI couldn't solve what I was doing, and I was fine.
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.
I don't like AI, but AI generated images have use cases. For instance, if you program a browser game but you lack human artists. Then AI generated images can be useful. Many of these images suck and feel misplaced, but some are quite nice, so I don't think it applies to all of AI generated content.
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.
You can use the AI tools but still program by hand every day for practice and fun. Programming becomes deliberate practice to keep your skills and mind sharp. Like going to the gym, but for your brain. You can use the LLMs to push and challenge yourself, setting more aggressive and ambitious goals than you might have in the old days for learning.
I used to think of software dev like climbing a mountain. Hard, and I loved it. I loved it because of the difficulty. That was the most fun part. Getting to the top, the summit. That was incidental to me. I wouldn't even defend that as a good thing. Certainly not good engineering. It was just what I liked. Any good engineering was incidental to how fun the hard parts of the puzzle were.
Then LLMs came along and I thought "this is like a helicopter. You can go straight up to the top in a few minutes." While very practical, it also led to the feelings the author described. After months of handwringing and using the tools, having existential crises - I've arrived at a new conclusion:
It's not a helicopter. It's a jetpack. And it's still hard to use if you push it to it's absolute limit. Knowing just the right spot to grab the rock as you fly by. Taking as much risk as possible, but not too much. Pushing both the jet pack (or perhaps it's an iron man suit now with latest models) and the rock climbing knowledge as far as they will go. Screwing up, falling off the wall, and learning.
And with this jetpack you can get to places you never could have climbed to without it. Not just the top. Weird, interesting spots on the mountain.
That perspective, which I've taken to over the last month or two has helped me find the fun again. The existential crises have ended and I'm back to feeling about software dev the way I felt a few years ago. Boundless joy and excitement. Probably more now.
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_.
If your goal was to prove that people don't care about how derivative games are, I think you picked some pretty bad examples, because Ubisoft is not in a good place right now. And I'd argue that the main reason behind it is precisely that lack of originality.
Hell, even the biggest titans of the "release the same game every year" part of the industry, such as Call of Duty, have been stumbling in recent years due to people inevitably getting bored of playing derivative slop made by people who don't understand what made the originals good, and can only mindlessly copy it over and over.
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 was never true, otherwise "stealth startups" wouldn't have been a thing.
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?
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.
The tradeoff is that it is now easier to do more complex sorcery, even as someone who is writing the code. My motivation has always been the sheer joy of solving each puzzle and moving on to the next. That joy is no less real in the world of LLMs, and having one in the backseat to check my code and answer questions has genuinely expanded the horizon.
I still have my own "fuck it, make it anyway" moments as the premium on my skill disintegrates. I don't think we want a world where humans are no longer involved in controlling that power, and the puzzles are still fun.
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.
It’s fine to keep apprised of, but I really do miss the actually-genuinely-interesting topics and projects which used to pop up here, pre ai days.
I feel like it's the same with programming now. So you built something in a week that used to take two. Ok, that's expected now. Expectations are raised before you can even blink, but it's very difficult to lower them. So that's it. We've built the rod for our backs and now must shit out code quicker than we can think.
I'm sad I won't get to take pride in anything I program any more. But oh well. There are other things in life that are more important. I expect I'll become more of a plumber just joining together slop to make things happen.
Some things I've done that have been incredibly fun and invigorating and never would have happened if not for AI:
https://afterword.exe.xyz (I wanted badly to play Jonah's original Word After Word (desktop only) game on my phone or just in a web browser and with remote friends/family, so got his blessing for a web remake)
https://github.com/jgbrwn/fetchcade
https://loderunner2099.exe.xyz/
https://v2.my-upc.com (don't ask, if you know, you know)
https://cartalk-amp.exe.xyz
https://aiconversation.apps.techpique.com
https://github.com/jgbrwn/mst3k-anything (Paste a video URL. Get back a robot-heckled version)
https://hn-readtheroom.exe.xyz/
https://jgbrwn.itch.io/cannonsmash-web
https://history-of-webhosting.exe.xyz/
https://wordizzle.exe.xyz/ (WIP)
https://exe-muttha-fukken-dev.exe.xyz/ (fansite lol)
https://github.com/jgbrwn/vibebin
https://github.com/jgbrwn/rsync-web
https://github.com/jgbrwn/retro-computing-stream
https://github.com/jgbrwn/github-repo-stream
An art analogy:
Imagine that the AI doesn't paint the painting, and it certainly doesn't decide what to paint. Instead it washes the brushes, stretches the canvas, mixes the paints, and cleans your studio.
If you try to make it do the actual art, what you'll get -- the "slop" people talk about -- is a mathematical average of all art, or a skewed average if you try to prompt it out of that central attractor. That's why visual AI art looks "plastic" and weird and falls into a kind of uncanny valley.
The reason I love AI in coding is: with painting the stuff I listed (washing brushes, stretching canvas, cleaning the studio) is a small part of painting. With coding stuff like CRUD, glue, endless obvious tests, and re-implementation of "embarrassingly solved" algorithms ends up by like 90% of all manual coding by time spent.
Coding is like painting if the other stuff around painting took up 90% of the time, leaving only 10% of the time to paint.
For complex projects 10% is generous. In many cases glue and CRUD and CI scripts and detailed bulleted git commit messages and merges and tests and very boring sorts of documentation and and and and and takes up more like 99% of the time, leaving like 1% for actual creativity.
This has been a legitimate complaint of coders forever, especially when one is coding for a job. AI, properly deployed, shrinks the fraction of grunt work dramatically. What's left is the most interesting stuff, architecture, design, planning, and deep implementation work of parts that need that kind of focus.
And that's the actual painting as far as coding is concerned.
The role of AI in both art and coding should be to do the uncreative parts.
Edit:
The only caveat is: I get the idea that the whole thing can be craft. But I think most projects are not like this, and projects done for money are almost by definition not like this. If you want to some code purely for the craft and the art and not use AI that's fine and nobody will stop you.
I expect to see a kind of hand-made software niche or market the way there is for hand-crafted furniture, hand-forged metallurgy, hand-blown glass, and so on.
That will not be a report generator for an internal portal inside an insurance company or a SaaS backend for managing policy on other SaaS backends. That stuff's gonna be vibe coded almost 100%. Good.
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.
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.
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.
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.