5 ms·

Why craft-lovers are losing their craft

98 points by vinhnx 7mo ago

jazz9k 7mo ago
The 'make it go' people that I worked with usually didn't understand many of the underlying code, and the 'craft' people always need to fix it. Craft people aren't losing anything. If anything, they are more valuable because they need to fix the slopware written by AI and the 'make it go' developers.
- PaulKeeble 7mo ago
  Its one thing when code was hammered out by someone to just work, its worse fixing code that no one even wrote to begin with. This period of programming is going to produce a lot of code people dump and replace because its not worth fixing.
  - Forgeties79 7mo ago
    And like SEO blog spam it’s just going to grow in volume because people want to pad their CV’s with all sorts of activity in GitHub regardless of the quality
  - gibbitz 7mo ago
    This is the pattern. The labor is nearly worthless, so just have the bot reinvent the wheel every time.
  - Ekaros 7mo ago
    What I fear is that early or even current steps of this process is replacing parts of the code or all code wholesale. With as broken or just slightly less broken code. Albeit the way it is broken could be different each time. So problems are not fixed, they are just replaced with different problems. Ad nauseum...
  - sph 7mo ago
    "Single-use applications" but instead of a bash script, it's a 250k lines monstrosity in Rust because "static typing"
- lmorchard 7mo ago
  Meanwhile, Undertale, one of the most celebrated video games, famously has a 1000+ line switch statement and AI had nothing to do with it. Sometimes you have to bang out something that works, just to even get the chance to be annoyed at how bad it is for next version.
  - tytho 7mo ago
    Game development is often a completely different set of skills and maintenance profile compared to enterprise SaaS development. Many single-player games especially indie ones don’t need to worry about multi-year contracts or having to work through many cycles of different developers coming in and out of a project. Having a 1000+ line switch statement seems totally reasonable on a project with a handful of developers that will continue to work on the project. My understanding is that the switch statement was for npc character conversation text. That seems pretty reasonable, even in enterprise SaaS for something like translations. It might not be as easy to maintain in other circumstances.
    - airbreather 7mo ago
      I would suggest that the 1000 line switch statement implies a state machine that has suffered from the "state explosion". This usually results from an inadequate system-subsystem decomposition and/or not considering modes, both of which lead to hierarchal state machines instead of one big flat one. This aspect of architecture is difficult to teach, it is one of the "black arts" that comes from experience and is difficult to codify. Just one example why, is that often it might require the synthesis of state machines not directly evident as needed from the functionality, eg to perform a one to many or many to one functionality.
      - 8note 7mo ago
        https://i.redd.it/vglorgtzx0kd1.png https://i.redd.it/vglorgtzx0kd1.png can't find the actual code, but its a look up table for what dialogue to use. The existence of a switch statement does not force the code to be a state machine. it could still be some architectural deficit around making it harder to look up the dialogue rather than having it in place when uts triggered, but it makes it nice to understand all the dialogue in the game at once
- AngryData 7mo ago
  Would you say mechanics, repairmen, and other trade workers are more valuable today? They have become rarer yes, and everyone thinks they must be making bank off their rarer skill set, and yet the actual wages those skilled people receive haven't gone up. Sure sure you can point to some random plumber living in the heart of NYC that is sitting on a multimillion dollar piece of land to hold their supplies and vans as making a lot of money, but that doesn't make up for the other 99% of the plumbers of the nation who don't make such wages despite having just as valuable of a skill. How many people here can frame a house? Meanwhile I stopped framing because I made more money driving a forklift around a warehouse. My father stopped wrenching because he made more money selling heavy equipment parts than he did fixing million dollar pieces of heavy equipment in shitty and hazardous environments. When tools make skill less relevant, the skilled workers get the boot. Even if the skilled versus non-skilled ends up a wash in dollar per productivity so you think the lower quality would make the skilled workers preferable, the unskilled workers will still win out because they are far easier to replace. You fire the best cabinet maker around in 200 miles, you are in trouble. If you fire 10 doofuses a year for shitty work, you can just get 10 more within just a few days. Quality may suffer but volume makes up for it and will push out competition because quality is not easily measured or seen by customers who can't recognize it.
  - tempodox 7mo ago
    This is why “worse is better” always wins eventually.
  - PinkMilkshake 7mo ago
    I think it might depend on where you live. In Australia, tradies make bank.
- ryandvm 7mo ago
  Perhaps, but damn, fixing shitty code is not the "craft" that I signed up for twenty years ago.
gibbitz 7mo ago
I've been feeling the craft side of this for the last few years. My education is in Fine Art and I am a self taught UI developer. To me this was a craft of making the code do what the designer envisioned and working with creatives to create engaging and unique interfaces. Slowly but surely "standardization" eroded this via bootstrap and material UI and interfaces lost that spark of creativity. This was the beginning of thinking of sites as products in my mind. LLMs are just the nail in this coffin. Since tools like Claude Code and Cursor have entered the market, I don't do tech in my free time anymore. I don't enjoy it now. I just use the LLM at work like the business dictates (and monitors) then clock out promptly at 5:00.
charcircuit 7mo ago
>The market is penalizing them for it. I don't like this framing. Does the market penalize people for going to see a movie or going skiing? The most effective way for someone to make money and someone's hobbies usually do not overlap and when they do turning a hobby into a job often results in one growing to hate the hobby.
- abracadaniel 7mo ago
  If you were to want to do it between 8am and 5pm, yeah I’d say it does. Lots of places demand much longer hours as well, and would pass over people who want to make use of their free time.
- lmorchard 7mo ago
  No, but it's increasingly penalizing folks for focusing on well-crafted code on company time.
- linguae 7mo ago
  My take is that there used to be a significant overlap between hobbyist-style exploration/coding and what industry wanted, especially during the PC revolution where companies like Apple and Microsoft were started by hobbyists selling their creations to other people. This continued through the 1990s and the 2000s; we know the story of how Mark Zuckerberg started Facebook from his Harvard dorm room. I am a 90s kid who was inspired by the stories of Steve Jobs and Bill Gates to pursue a computing career. I was also inspired by Bell Labs and Xerox PARC researchers. The “hacker-friendliness” of software industry employment has been eroding in the past decade or so, and generative AI is another factor that strengthens the position of business owners and managers. Perhaps this is the maturing of the software development field. Back when computers were new and when there were few people skilled in computing, employment was more favorable for hobbyists. Over time the frontiers of computing have been settled, which reduced the need for explorers, and thus explorers have been sidelined in favor of different types of workers. LLMs are another step; while I’m not sure that LLMs could do academic research in computer science, they are already capable of doing software engineering tasks that undergraduates and interns could do. I think what some of us are mourning is the closing of a frontier, of our figurative pastures being turned into suburban subdivisions. It’s bigger than generative AI; it’s a field that is less dependent on hobbyists for its future. There will always be other frontiers, and even in computing there are still interesting areas of research and areas where hobbyists can contribute. But I think much of the software industry has moved in a direction where its ethos is different from the ethos of enthusiasts.
RagnarD 7mo ago
One solution: do NOT just program for work. If it's not work related - where management can dictate how you work - you can whatever you want, and if what you want is to keep writing software and not outsource your brain to an AI, absolutely do so.
- linguae 7mo ago
  I’ve come to the same conclusion, though my line of work was research rather than software engineering. “He who pays the piper calls the tune.” It’s fun as long as I enjoyed the tunes being called, but the tunes changed, and I became less interested in playing. I am now a tenure-track community college professor. I’m evaluated entirely by my teaching and service. While teaching a full course load is intense, and while my salary is nowhere near what a FAANG engineer makes, I get three months of summer break and one month of winter break every year to rejuvenate and to work on personal projects, with nobody telling me what research projects to work on, how frequently I should publish, and how fast I ship code. This quote from J. J. Thomson resonates with me, and it’s more than 100 years old: "Granting the importance of this pioneering research, how can it best be promoted? The method of direct endowment will not work, for if you pay a man a salary for doing research, he and you will want to have something to point to at the end of the year to show that the money has not been wasted. In promising work of the highest class, however, results do not come in this regular fashion, in fact years may pass without any tangible results being obtained, and the position of the paid worker would be very embarrassing and he would naturally take to work on a lower, or at any rate a different plane where he could be sure of getting year by year tangible results which would justify his salary. The position is this: You want this kind of research, but, if you pay a man to do it, it will drive him to research of a different kind. The only thing to do is to pay him for doing something else and give him enough leisure to do research for the love of it." (from https://archive.org/details/b29932208/page/198/mode/2up https://archive.org/details/b29932208/page/198/mode/2up).
  - coliveira 7mo ago
    That was the original strategy for universities: teaching was the job, and research was the side-product of having some very smart people with free time. Until some "genius" decided that it was better to have professors competing for money to pay directly for their research. This transformed a noble and desirable profession into just another money searching activity.
RcouF1uZ4gsC 7mo ago
I don’t think this split is fundamental or permanent. Look at photography. You have both - the point and shoot people and the ones that use photography as a craft. And I am seeing that with LLMs as well. You do have craft people that find joy in figuring out craft the perfect one shot prompt or create a system that coordinates a bunch of agents. That is also craft, but like photography, craft with a more capable tool.
bananamogul 7mo ago
I guess there's a quota on HN where every day, some dev has to whinge about how AI is ruining The Way It Used To Be. How is this post different than dozens that have come before it? It's the same gnashing of teeth, just with different analogies each time.
pclowes 7mo ago
I do hand tool woodworking as a hobby. Aside from rough dimensioning, all the final cuts, planing, mortising, carving, dove tails etc are done by hand. Sometimes using tools over 100yrs old, not out of some fetish for the past, they are just better and cheaper than hand tools today. It takes forever but I want to work the wood and develop actual skill. I don't want to just push wood through a series of saws, sanders, jigs and other machines. It has also made me much better at building “we need this now” type things (decks, cabinets etc) with power tools in general. I am much more precise, sensitive, and detail oriented. I hope and feel there is something similar with coding and LLMs. A way to repurpose that hard earned sensitivity and recover some of the zen aspects as well. I am still figuring that out, part of it has been tiring but honestly a lot of it has made programming more fun too.
- burntoutgray 7mo ago
  The way some people wield LLM, etc is like using a chainsaw to cut a dovetail because it is faster.
  - snek_case 7mo ago
    You're definitely going to get people using LLMs running on 8x $50K GPUs in a datacenter to do the job of a bash script.
    - edgyquant 7mo ago
      I already see people using an agent to write a git commit
      - derwiki 7mo ago
        What’s wrong with that? The agent session had all the business context, knows what changed, and how we verified it. It takes 5s to turn that into a PR desc vs 10-100x that by hand
        7mo ago
wewewedxfgdf 7mo ago
The "it's my craft" developers seem to often disparage the "it's a means to an end" people as not being good at programming.
- smackeyacky 7mo ago
  That can go both ways, I’m more make it go and I hate nothing more than debugging somebody else’s over complicated solution but technically fascinating code. In my world boring code is good, maintainable code.
turlockmike 7mo ago
One craft is automated and a new one is just beginning. Building AI agents is really fun and the problem of having them be reliable adaptable efficient is actually really challenging and I'm having a lot of fun with it trying to figure it out. To me it's a lot like factorio or my personal favorite Dyson sphere program where at first you do everything by hand and then you automate and then you automate the automation. For the first time in human history we can automate intelligence with a computer but just because we can automate it doesn't mean all the good automation is good and we need engineers who can figure out how to automate it reliably scale it deploy it maintain it. And yes eventually we will automate the automation too.
eadwu 7mo ago
Craft is caring about the x in y = mx + b, while the so called "it's a means to an end" care about the y. The difference between "craft lovers" and "doers" is that one operates at a better fitting abstraction (that is more aligned to the values of capitalism). You can say "doers" are just "craft lovers" in and of itself - there is little distinction between them - this is just reiterating the change from binary to high level languages.
- auggierose 7mo ago
  I like that description. Maybe use y = f(x); now craft lovers care about the f, while doers care about the y. You usually cannot do much about the x.
burntoutgray 7mo ago
To use an analogy, back in the days of film cameras and before 1 hour labs, the "craftsman" photographer would carefully frame the shot, carefully setting the exposure, aperture and focus. The most meticulous would take notes in a notebook. There were only 36 frames to a roll of film and all going well, the photographer had to wait a couple of days to get back the proof sheet. Those were the days when expert photographers were commissioned to take photos for special events, etc. These days, everybody is an expert photographer, taking thousands of irrelevant photos with their smartphones. The volume of photos has exploded, the quality of the best has minimally changed (i.e. before being photoshopped, etc.) The current crop of AI-aided tools are comparable to the early digital cameras in phones.
- dugite-code 7mo ago
  > These days, everybody is an expert photographer If that were true there would be no wedding photographer's or any sales of high end DSLR's. The barrier of entry may have fallen but the need for real experts and tools still exists. I expect AI's will cause a similar shift, lower barrier to entry but still requiring the hand of the expert in critical situations.
  - airbreather 7mo ago
    Just wait long enough
  - mpalmer 7mo ago
    This fails to take into account a pervasive, global lowering of standards on all fronts. Who will retain the good taste to keep paying a premium for professional photographers, etc?
    - calvinmorrison 7mo ago
      We shot our wedding (2021) entirely on film. Some medium format, some 35mm, some instant film (polaroid and instax mini)
- belZaah 7mo ago
qsera 7mo ago
Using an LLM for coding is like using a Electric shaver. It is unpredictable and you have to keep going over the same area in hopes that it will pick up the remaining few stubs of hair. Boring, irritating but very convenient. Use a straight razor, which is predictable and you feel time flying and you end up with perfect shave.
- fragmede 7mo ago
  Interesting analogy! Not all electric razors are created equal though, some will nick your skin, dull blades will pull out hair painfully. And of course, in this analogy, I'd have to point out laser hair removal. You could use the LLM to build some software to do a thing, or you could have the LLM just do it for you!
flankstaek 7mo ago
I think this article misses a potential connection in the capitalist critique of LLMs to correlate this to the equivalent "industrialization" of coding. When a craft becomes industrialized, as is talked about here, you see the divergence in hobbyists and mass production. I think because of the uniqueness or newness of the craft of programming - this shift hadn't actually occurred and you were seeing hobbyist programmers landing jobs and being able to output professional code by crafting it thoughtfully as there wasn't a major output difference previously. Now we are seeing that difference. Food for thought, interesting article!
- tdeck 7mo ago
  Absolutely. These tools are being used to deprofessionalize our work. At some point, perhaps in our lifetime, most of us will no longer be able to bring anything to the table that commands either job security or a good wage. This is the dream of most of the employing class. There will be a glut of laid off software engineers all jockeying for positions babysitting a dozen LLM agents at a time, agents that work constantly and never run out of questions and review requests to ping us with. Perhaps we'll be measured on our response time to agent inquiries. Just like all the cottage weavers who ended up stuck in a thunderously loud power loom weaving shed for 14 hours a day, we are going to discover what a big loss in status and security feels like. Any special knowledge, taste, or communication skills we think we are bringing to the table will be siphoned into LLMs and used to train them. The way we boss the LLM around to make it produce better work will be incorporated into the next model version, rendering our contributions less and less valuable. Companies will make deals with LLM providers to suck all their internal customer interactions and team chats into the LLM so they can tune it to replicate those interactions. Perhaps it will go off the rails now and then, but think of the savings.
4162-123w 7mo ago
These kind of inevitability articles always citing the same bloggers are just there to support AI. They never address: - Real developers like Rob Pike who hate AI. - The IP theft that powers the models. - The actual useful output of LLMs that is very low. - The fact that 99.9999% of useful software was produced before AI. - The fact that "nostalgic developers" are not interested in "writing" code, but understanding algorithms and creating beauty. These articles lie by omission, direct your attention to the points they want you to discuss, present false dichotomies and are generally deceptive. If these people win, we are in for a horrible future.
- operatingthetan 7mo ago
  All of your bullet points look deceptive or dishonest to me. They are either untrue or something that won't stop the march of progress. When the car was invented was it a useful counter-argument to suggest 99.9999% of miles traveled so far were horses or bicycles? No.
  - martin-t 7mo ago
    No, you're the dishonest one. The only bullet point a reasonable person might disagree with it "99.9999%". The rest is true. - Many real devs criticize "AI". Documented: https://bsky.app/profile/robpike.io/post/3matwg6w3ic2s?ref=itsfoss.com https://bsky.app/profile/robpike.io/post/3matwg6w3ic2s?ref=i... - LLMs are trained without respecting the licenses of the original work, not even giving attribution which almost all OSS licenses require. AGPL required derivative works to be also AGPL - this should include the model and all its output for any reasonable meaning of derived work. - SOTA models even today produce absolute garbage. A week ago, Claude Sonnet 4.6 tried to call one constructor from the body of another in C# using syntax which doesn't exist. Less glaring issues are completely normalized. This is why "agentic" generation is so popular today - it puts guard rails around the slop. - I and other devs I've talked to are not interested in the mechanical writing of code but in the additional understanding which comes from engaging deeply with the problem and solution.
    - operatingthetan 7mo ago
sudo_cowsay 7mo ago
Should we stop protesting the change and just accept it and adapt?
- techbrovanguard 7mo ago
  “Don’t ask questions, just consume Product and then get excited for next Product”.
padolsey 7mo ago
There is indeed a painful dissonance here. I like this new world, but feel sorrow for the loss of something. I try to remember how empowering AI is. It is already allowing millions of people to finally use the devices they've been sitting in front of all these years. No longer do they have to feel constrained by software creators who have made choices for them. Now it is their tool through-and-through, and they can construct software on-the-fly to match their needs precisely. They have been buying computers with both hands tied behind their backs. Now they are in control.
- Insanity 7mo ago
  I disagree. There's definitely _some_ who will use these tools to build systems for themselves. But do you think the chef who's been pulling insane hours in the restaurant wants to come home and build his own software? Or the teacher who just had to deal with an annoying classroom all day? People want software that just works, they'll pay for it, they don't want to use their computers to build their own software. That idea is just software and computer geeks (said affectionately) projecting their own desires on a larger community.
  - padolsey 7mo ago
    Does it have to be mutually exclusive? On-the-fly software does not destroy software. Gatekeeping software creation does not mean shoving the existing creators out, it just means creating a larger space that others can occupy, like when 'real' programmers had to slowly permit 'script kiddies' into their spaces. All feels a bit 'old guard' vs 'new guard'.
    - Insanity 7mo ago
      Not mutually exclusive, but I thought your initial post painted an overly rosy picture with the sentence "[..] allowing millions of people to finally use the devices they've been sitting in front of all these years". I don't think it's happening at this scale. I'll admit I have no real data to back that up, it's just a hunch really. But I find it hard to believe that those people whom previously weren't interested in building software are now suddenly interested to build stuff with an LLM. I'm sure _some_ people are doing this, and then they either hit roadblocks and quit or stick with it an learn actual software engineering. Looking at my non-tech bubble of friends and family, I don't see anyone actually doing that. I think it's a vocal minority that is doing this. That's just anecdata of course.
d--b 7mo ago
It’s called karma? We, software developers, as a profession took over countless crafts. It started with people doing calculations by hand, then moved on to people typing on typewriters and continued from there. People used to edit films with scissors and scotch tape. People used to place lead fonts on a matrix to print news articles. Databases used to be little cards made carefully by people whose job it was to organize and modify them. It’s a bit indecent for a developer to complain that LLMs took away the pleasure of molding a clay made of bits, while the robots we enabled to build took the actual clay off of potmakers actual hands. And what the author forgets to mention is that we got it good. Oh boy. As a software developer, I can work in any field I want. I started on video compression. I moved to finance. I make games in my spare time. I make plugins for music. And I get to be paid way more than my neighbor who’s a heart surgeon. I can work remotely 100%. I can go to a nice beach in Thailand, work 2 hours in the morning and enjoy the rest of the day, and still make more than the median salary in France, where I live. The grief is not the loss of the craft alone, it’s the loss of that craft that paid for your house. As they said: software is eating the world. Well, it is now eating itself. It’s only fair. The author is right though, human societies need to ask themselves whether they are willing to sacrifice all the crafts on the altar of productivity and convenience. The Amish decided they didn’t want to. It’s a bit of a weird choice, but it is a choice.
- padolsey 7mo ago
  Precisely. I dare say software developers bemoaning this new world don't realise that they - too - are supplanters of a prior world. A sweet irony.
- dahlia 7mo ago
  [dead]
- chromacity 7mo ago
  I think this is a bit facetious. Although software had a bunch of localized impacts, it killed only a handful of mainstream professions. People still had to typeset articles, there was just less lead involved. For a writer, switching from a typewriter to a keyboard didn't mean you somehow needed less skill to write. That said, I'm with you that it's tacky for software engineers to complain about their own hardships. We are some of the wealthiest and most pampered white collar workers out there, and we're not exactly innocent bystanders.
iwontberude 7mo ago
The author conflates two paradigms: The first is one of a child learning BASIC not for beauty but for making things happen on the screen. The second is an adult producing software not because he enjoys the act, challenge and workflow, but for shipping software. I don’t see any difference between the child learning BASIC for its beauty and the chase to make things happen on the screen. Secondly, there is a very profound difference between a child creating and an adult creating for profit. The profit motive changes everything, even for someone “doing it for the love of it.”
airbreather 7mo ago
All the whingers about AI - if it is as bad as you say, then you don't have a problem On the other hand, if it is not, then stop wasting effort arguing against the inevitable and use that effort to get ahead of the curve. Either way, whinging about it is the least effective use of your skills and time.
bakugo 7mo ago
> Craft-lovers and make-it-go people sat next to each other, shipped the same products, looked indistinguishable. The motivation behind the work was invisible because the process was identical. I do not agree with this assertion and I don't know why I don't see more pushback against it, neither here nor in the comments for the original post. If you're a "craft-lover" sitting next to and working with a "make-it-go person", odds are you will be very much aware of it. Even non-technical leadership is likely to be able to notice it if they're perceptive enough.
juris 7mo ago
i think anyone who feels dispossessed from the advance of technology should rekindle that spirit of hands-on adventure by looking at clay pots at the museum. the souls of a thousand hours sit there behind glass and valued for their richness and simplicity, against all odds, and people to this day carry on those traditions to improve the art. did the soul of pottery die with the industrial revolution? will your hand code? it won’t be for everyone, but it’s there for you. find a book by Soetsu Yanagi on the subject of “min gei” and it will help you.
dinkumthinkum 7mo ago
It seems like this is a Marxist that is recycling his posts through an LLM. This other post of his is eerily similar: https://writings.hongminhee.org/2026/02/acting-materialistically-in-an-imperfect-world/ https://writings.hongminhee.org/2026/02/acting-materialistic...
tuan 7mo ago
There's another camp that don't care about the craft AND also don't care about the product. This camp, wielding power of AI, is making life worse for the other two camps. I've been getting so many code reviews that are generated by AI, but the author does not even has the decency to self review the generated code before they send out pull requests. It feels like an insult sometimes. For example, unit tests that basically assert if `a = 1` after setting a to 1. Every PR now has lots of unit tests, but they test the implementation details, not the spec. So now every change that breaks their implementation details causes false positive test failures. This creates a self enforcing negative loop. Every PR now comes with tons of unit test fixes. People start responding to PR comments with something along the line of: I ask AI but it was not able to solve the problem, if you have a solution, LMK. Or another variant I see often is: I think this is wrong, but AI says this is fine, so I'll leave it as is. I see craft lovers or product people using AI effectively. I use AI daily too. But the above camp is making my day to day job sometimes unbearable.
justonepost2 7mo ago
I guess I’m not the target audience but the flood of articles about craft or “deep blue” feel like a psyop. When the middle class disappears and your comfortable salary is replaced by, at best, a $1000/mo UBI (that’s 12k per year by the way) most people won’t have time to think or care about this nonsense
roncesvalles 7mo ago
This is probably contrary to conventional wisdom (esp among the startup/VC crowd) but: there are very few scenarios where how quickly you build something matters more than the quality of what you build. The AI coding era has brought about an unhealthy obsession with speed of software dev (where "speed" is often measured by fallacious metrics like LOC pushed per day, but that's tangential). And it's obvious why, this is the main commercial value proposition (if you can build 2x faster, you need 50% as many devs). Except that the speed only comes "for free" until a certain point. Beyond that point, you're trading off quality for more speed, and this trade is almost never worth it. If it takes you 6 months to handcraft a high quality version of your product (with selective AI assistance only until the boundary where it's not eating quality), almost always this is a better approach than banging out some heavily vibe/agent-coded crap in 1 month.
- gibbitz 7mo ago
  Why is this never a "we can make more products" conversation with businesses? It's always about how many people we can not pay versus how many more things we can sell. I think this is very telling of where the message is coming from and how the tools are being sold. Typically a good thing would be creating more value for a company's consumers, not increasing unemployment. Are these tools to make our lives better or to increase profits for shareholders without taking risks?
deleted 7mo ago
[deleted]
jeremie_strand 7mo ago
[flagged]
- _aavaa_ 7mo ago
  The output of hand watchmaking is likely also indistinguishable to most customers. I am skeptical that people buying 250k watches can tell if the perfect design was done by hand vs done by machine. The manufacturers play up the handcrafted nature to justify.
pugchat 7mo ago
[dead]
delimit 7mo ago
I think the craft isn't gone, it's shifting. I use three different AI coding assistants depending on the task, and the skill is knowing what to ask for, how to review what comes back, and maintaining coherence across a codebase that multiple models have touched. The craft is now in system design, specification, and verification — not in typing the code yourself.

98 points by vinhnx 7mo ago

The 'make it go' people that I worked with usually didn't understand many of the underlying code, and the 'craft' people always need to fix it. Craft people aren't losing anything. If anything, they are more valuable because they need to fix the slopware written by AI and the 'make it go' developers.

PaulKeeble 7mo ago
Its one thing when code was hammered out by someone to just work, its worse fixing code that no one even wrote to begin with. This period of programming is going to produce a lot of code people dump and replace because its not worth fixing.
- Forgeties79 7mo ago
  And like SEO blog spam it’s just going to grow in volume because people want to pad their CV’s with all sorts of activity in GitHub regardless of the quality
- gibbitz 7mo ago
  This is the pattern. The labor is nearly worthless, so just have the bot reinvent the wheel every time.
- Ekaros 7mo ago
  What I fear is that early or even current steps of this process is replacing parts of the code or all code wholesale. With as broken or just slightly less broken code. Albeit the way it is broken could be different each time. So problems are not fixed, they are just replaced with different problems. Ad nauseum...
- sph 7mo ago
  "Single-use applications" but instead of a bash script, it's a 250k lines monstrosity in Rust because "static typing"
lmorchard 7mo ago
Meanwhile, Undertale, one of the most celebrated video games, famously has a 1000+ line switch statement and AI had nothing to do with it. Sometimes you have to bang out something that works, just to even get the chance to be annoyed at how bad it is for next version.
- tytho 7mo ago
  Game development is often a completely different set of skills and maintenance profile compared to enterprise SaaS development. Many single-player games especially indie ones don’t need to worry about multi-year contracts or having to work through many cycles of different developers coming in and out of a project. Having a 1000+ line switch statement seems totally reasonable on a project with a handful of developers that will continue to work on the project. My understanding is that the switch statement was for npc character conversation text. That seems pretty reasonable, even in enterprise SaaS for something like translations. It might not be as easy to maintain in other circumstances.
  - airbreather 7mo ago
    I would suggest that the 1000 line switch statement implies a state machine that has suffered from the "state explosion". This usually results from an inadequate system-subsystem decomposition and/or not considering modes, both of which lead to hierarchal state machines instead of one big flat one. This aspect of architecture is difficult to teach, it is one of the "black arts" that comes from experience and is difficult to codify. Just one example why, is that often it might require the synthesis of state machines not directly evident as needed from the functionality, eg to perform a one to many or many to one functionality.
    - 8note 7mo ago
      https://i.redd.it/vglorgtzx0kd1.png https://i.redd.it/vglorgtzx0kd1.png can't find the actual code, but its a look up table for what dialogue to use. The existence of a switch statement does not force the code to be a state machine. it could still be some architectural deficit around making it harder to look up the dialogue rather than having it in place when uts triggered, but it makes it nice to understand all the dialogue in the game at once
AngryData 7mo ago
Would you say mechanics, repairmen, and other trade workers are more valuable today? They have become rarer yes, and everyone thinks they must be making bank off their rarer skill set, and yet the actual wages those skilled people receive haven't gone up. Sure sure you can point to some random plumber living in the heart of NYC that is sitting on a multimillion dollar piece of land to hold their supplies and vans as making a lot of money, but that doesn't make up for the other 99% of the plumbers of the nation who don't make such wages despite having just as valuable of a skill. How many people here can frame a house? Meanwhile I stopped framing because I made more money driving a forklift around a warehouse. My father stopped wrenching because he made more money selling heavy equipment parts than he did fixing million dollar pieces of heavy equipment in shitty and hazardous environments. When tools make skill less relevant, the skilled workers get the boot. Even if the skilled versus non-skilled ends up a wash in dollar per productivity so you think the lower quality would make the skilled workers preferable, the unskilled workers will still win out because they are far easier to replace. You fire the best cabinet maker around in 200 miles, you are in trouble. If you fire 10 doofuses a year for shitty work, you can just get 10 more within just a few days. Quality may suffer but volume makes up for it and will push out competition because quality is not easily measured or seen by customers who can't recognize it.
- tempodox 7mo ago
  This is why “worse is better” always wins eventually.
- PinkMilkshake 7mo ago
  I think it might depend on where you live. In Australia, tradies make bank.
ryandvm 7mo ago
Perhaps, but damn, fixing shitty code is not the "craft" that I signed up for twenty years ago.

gibbitz 7mo ago

I've been feeling the craft side of this for the last few years. My education is in Fine Art and I am a self taught UI developer. To me this was a craft of making the code do what the designer envisioned and working with creatives to create engaging and unique interfaces. Slowly but surely "standardization" eroded this via bootstrap and material UI and interfaces lost that spark of creativity. This was the beginning of thinking of sites as products in my mind. LLMs are just the nail in this coffin. Since tools like Claude Code and Cursor have entered the market, I don't do tech in my free time anymore. I don't enjoy it now. I just use the LLM at work like the business dictates (and monitors) then clock out promptly at 5:00.

charcircuit 7mo ago

>The market is penalizing them for it. I don't like this framing. Does the market penalize people for going to see a movie or going skiing? The most effective way for someone to make money and someone's hobbies usually do not overlap and when they do turning a hobby into a job often results in one growing to hate the hobby.

abracadaniel 7mo ago
If you were to want to do it between 8am and 5pm, yeah I’d say it does. Lots of places demand much longer hours as well, and would pass over people who want to make use of their free time.
lmorchard 7mo ago
No, but it's increasingly penalizing folks for focusing on well-crafted code on company time.
linguae 7mo ago
My take is that there used to be a significant overlap between hobbyist-style exploration/coding and what industry wanted, especially during the PC revolution where companies like Apple and Microsoft were started by hobbyists selling their creations to other people. This continued through the 1990s and the 2000s; we know the story of how Mark Zuckerberg started Facebook from his Harvard dorm room. I am a 90s kid who was inspired by the stories of Steve Jobs and Bill Gates to pursue a computing career. I was also inspired by Bell Labs and Xerox PARC researchers. The “hacker-friendliness” of software industry employment has been eroding in the past decade or so, and generative AI is another factor that strengthens the position of business owners and managers. Perhaps this is the maturing of the software development field. Back when computers were new and when there were few people skilled in computing, employment was more favorable for hobbyists. Over time the frontiers of computing have been settled, which reduced the need for explorers, and thus explorers have been sidelined in favor of different types of workers. LLMs are another step; while I’m not sure that LLMs could do academic research in computer science, they are already capable of doing software engineering tasks that undergraduates and interns could do. I think what some of us are mourning is the closing of a frontier, of our figurative pastures being turned into suburban subdivisions. It’s bigger than generative AI; it’s a field that is less dependent on hobbyists for its future. There will always be other frontiers, and even in computing there are still interesting areas of research and areas where hobbyists can contribute. But I think much of the software industry has moved in a direction where its ethos is different from the ethos of enthusiasts.

RagnarD 7mo ago

One solution: do NOT just program for work. If it's not work related - where management can dictate how you work - you can whatever you want, and if what you want is to keep writing software and not outsource your brain to an AI, absolutely do so.

linguae 7mo ago
I’ve come to the same conclusion, though my line of work was research rather than software engineering. “He who pays the piper calls the tune.” It’s fun as long as I enjoyed the tunes being called, but the tunes changed, and I became less interested in playing. I am now a tenure-track community college professor. I’m evaluated entirely by my teaching and service. While teaching a full course load is intense, and while my salary is nowhere near what a FAANG engineer makes, I get three months of summer break and one month of winter break every year to rejuvenate and to work on personal projects, with nobody telling me what research projects to work on, how frequently I should publish, and how fast I ship code. This quote from J. J. Thomson resonates with me, and it’s more than 100 years old: "Granting the importance of this pioneering research, how can it best be promoted? The method of direct endowment will not work, for if you pay a man a salary for doing research, he and you will want to have something to point to at the end of the year to show that the money has not been wasted. In promising work of the highest class, however, results do not come in this regular fashion, in fact years may pass without any tangible results being obtained, and the position of the paid worker would be very embarrassing and he would naturally take to work on a lower, or at any rate a different plane where he could be sure of getting year by year tangible results which would justify his salary. The position is this: You want this kind of research, but, if you pay a man to do it, it will drive him to research of a different kind. The only thing to do is to pay him for doing something else and give him enough leisure to do research for the love of it." (from https://archive.org/details/b29932208/page/198/mode/2up https://archive.org/details/b29932208/page/198/mode/2up).
- coliveira 7mo ago
  That was the original strategy for universities: teaching was the job, and research was the side-product of having some very smart people with free time. Until some "genius" decided that it was better to have professors competing for money to pay directly for their research. This transformed a noble and desirable profession into just another money searching activity.

RcouF1uZ4gsC 7mo ago

I don’t think this split is fundamental or permanent. Look at photography. You have both - the point and shoot people and the ones that use photography as a craft. And I am seeing that with LLMs as well. You do have craft people that find joy in figuring out craft the perfect one shot prompt or create a system that coordinates a bunch of agents. That is also craft, but like photography, craft with a more capable tool.

bananamogul 7mo ago

I guess there's a quota on HN where every day, some dev has to whinge about how AI is ruining The Way It Used To Be. How is this post different than dozens that have come before it? It's the same gnashing of teeth, just with different analogies each time.

pclowes 7mo ago

I do hand tool woodworking as a hobby. Aside from rough dimensioning, all the final cuts, planing, mortising, carving, dove tails etc are done by hand. Sometimes using tools over 100yrs old, not out of some fetish for the past, they are just better and cheaper than hand tools today. It takes forever but I want to work the wood and develop actual skill. I don't want to just push wood through a series of saws, sanders, jigs and other machines. It has also made me much better at building “we need this now” type things (decks, cabinets etc) with power tools in general. I am much more precise, sensitive, and detail oriented. I hope and feel there is something similar with coding and LLMs. A way to repurpose that hard earned sensitivity and recover some of the zen aspects as well. I am still figuring that out, part of it has been tiring but honestly a lot of it has made programming more fun too.

burntoutgray 7mo ago
The way some people wield LLM, etc is like using a chainsaw to cut a dovetail because it is faster.
- snek_case 7mo ago
  You're definitely going to get people using LLMs running on 8x $50K GPUs in a datacenter to do the job of a bash script.
  - edgyquant 7mo ago
    I already see people using an agent to write a git commit
    - derwiki 7mo ago
      What’s wrong with that? The agent session had all the business context, knows what changed, and how we verified it. It takes 5s to turn that into a PR desc vs 10-100x that by hand
      - 7mo ago

wewewedxfgdf 7mo ago

The "it's my craft" developers seem to often disparage the "it's a means to an end" people as not being good at programming.

smackeyacky 7mo ago
That can go both ways, I’m more make it go and I hate nothing more than debugging somebody else’s over complicated solution but technically fascinating code. In my world boring code is good, maintainable code.

turlockmike 7mo ago

One craft is automated and a new one is just beginning. Building AI agents is really fun and the problem of having them be reliable adaptable efficient is actually really challenging and I'm having a lot of fun with it trying to figure it out. To me it's a lot like factorio or my personal favorite Dyson sphere program where at first you do everything by hand and then you automate and then you automate the automation. For the first time in human history we can automate intelligence with a computer but just because we can automate it doesn't mean all the good automation is good and we need engineers who can figure out how to automate it reliably scale it deploy it maintain it. And yes eventually we will automate the automation too.

eadwu 7mo ago

Craft is caring about the x in y = mx + b, while the so called "it's a means to an end" care about the y. The difference between "craft lovers" and "doers" is that one operates at a better fitting abstraction (that is more aligned to the values of capitalism). You can say "doers" are just "craft lovers" in and of itself - there is little distinction between them - this is just reiterating the change from binary to high level languages.

auggierose 7mo ago
I like that description. Maybe use y = f(x); now craft lovers care about the f, while doers care about the y. You usually cannot do much about the x.

burntoutgray 7mo ago

To use an analogy, back in the days of film cameras and before 1 hour labs, the "craftsman" photographer would carefully frame the shot, carefully setting the exposure, aperture and focus. The most meticulous would take notes in a notebook. There were only 36 frames to a roll of film and all going well, the photographer had to wait a couple of days to get back the proof sheet. Those were the days when expert photographers were commissioned to take photos for special events, etc. These days, everybody is an expert photographer, taking thousands of irrelevant photos with their smartphones. The volume of photos has exploded, the quality of the best has minimally changed (i.e. before being photoshopped, etc.) The current crop of AI-aided tools are comparable to the early digital cameras in phones.

dugite-code 7mo ago
> These days, everybody is an expert photographer If that were true there would be no wedding photographer's or any sales of high end DSLR's. The barrier of entry may have fallen but the need for real experts and tools still exists. I expect AI's will cause a similar shift, lower barrier to entry but still requiring the hand of the expert in critical situations.
- airbreather 7mo ago
  Just wait long enough
- mpalmer 7mo ago
  This fails to take into account a pervasive, global lowering of standards on all fronts. Who will retain the good taste to keep paying a premium for professional photographers, etc?
  - calvinmorrison 7mo ago
    We shot our wedding (2021) entirely on film. Some medium format, some 35mm, some instant film (polaroid and instax mini)
belZaah 7mo ago

qsera 7mo ago

Using an LLM for coding is like using a Electric shaver. It is unpredictable and you have to keep going over the same area in hopes that it will pick up the remaining few stubs of hair. Boring, irritating but very convenient. Use a straight razor, which is predictable and you feel time flying and you end up with perfect shave.

fragmede 7mo ago
Interesting analogy! Not all electric razors are created equal though, some will nick your skin, dull blades will pull out hair painfully. And of course, in this analogy, I'd have to point out laser hair removal. You could use the LLM to build some software to do a thing, or you could have the LLM just do it for you!

flankstaek 7mo ago

I think this article misses a potential connection in the capitalist critique of LLMs to correlate this to the equivalent "industrialization" of coding. When a craft becomes industrialized, as is talked about here, you see the divergence in hobbyists and mass production. I think because of the uniqueness or newness of the craft of programming - this shift hadn't actually occurred and you were seeing hobbyist programmers landing jobs and being able to output professional code by crafting it thoughtfully as there wasn't a major output difference previously. Now we are seeing that difference. Food for thought, interesting article!

tdeck 7mo ago
Absolutely. These tools are being used to deprofessionalize our work. At some point, perhaps in our lifetime, most of us will no longer be able to bring anything to the table that commands either job security or a good wage. This is the dream of most of the employing class. There will be a glut of laid off software engineers all jockeying for positions babysitting a dozen LLM agents at a time, agents that work constantly and never run out of questions and review requests to ping us with. Perhaps we'll be measured on our response time to agent inquiries. Just like all the cottage weavers who ended up stuck in a thunderously loud power loom weaving shed for 14 hours a day, we are going to discover what a big loss in status and security feels like. Any special knowledge, taste, or communication skills we think we are bringing to the table will be siphoned into LLMs and used to train them. The way we boss the LLM around to make it produce better work will be incorporated into the next model version, rendering our contributions less and less valuable. Companies will make deals with LLM providers to suck all their internal customer interactions and team chats into the LLM so they can tune it to replicate those interactions. Perhaps it will go off the rails now and then, but think of the savings.

4162-123w 7mo ago

These kind of inevitability articles always citing the same bloggers are just there to support AI. They never address: - Real developers like Rob Pike who hate AI. - The IP theft that powers the models. - The actual useful output of LLMs that is very low. - The fact that 99.9999% of useful software was produced before AI. - The fact that "nostalgic developers" are not interested in "writing" code, but understanding algorithms and creating beauty. These articles lie by omission, direct your attention to the points they want you to discuss, present false dichotomies and are generally deceptive. If these people win, we are in for a horrible future.

operatingthetan 7mo ago
All of your bullet points look deceptive or dishonest to me. They are either untrue or something that won't stop the march of progress. When the car was invented was it a useful counter-argument to suggest 99.9999% of miles traveled so far were horses or bicycles? No.
- martin-t 7mo ago
  No, you're the dishonest one. The only bullet point a reasonable person might disagree with it "99.9999%". The rest is true. - Many real devs criticize "AI". Documented: https://bsky.app/profile/robpike.io/post/3matwg6w3ic2s?ref=itsfoss.com https://bsky.app/profile/robpike.io/post/3matwg6w3ic2s?ref=i... - LLMs are trained without respecting the licenses of the original work, not even giving attribution which almost all OSS licenses require. AGPL required derivative works to be also AGPL - this should include the model and all its output for any reasonable meaning of derived work. - SOTA models even today produce absolute garbage. A week ago, Claude Sonnet 4.6 tried to call one constructor from the body of another in C# using syntax which doesn't exist. Less glaring issues are completely normalized. This is why "agentic" generation is so popular today - it puts guard rails around the slop. - I and other devs I've talked to are not interested in the mechanical writing of code but in the additional understanding which comes from engaging deeply with the problem and solution.
  - operatingthetan 7mo ago

sudo_cowsay 7mo ago

Should we stop protesting the change and just accept it and adapt?

techbrovanguard 7mo ago
“Don’t ask questions, just consume Product and then get excited for next Product”.

padolsey 7mo ago

There is indeed a painful dissonance here. I like this new world, but feel sorrow for the loss of something. I try to remember how empowering AI is. It is already allowing millions of people to finally use the devices they've been sitting in front of all these years. No longer do they have to feel constrained by software creators who have made choices for them. Now it is their tool through-and-through, and they can construct software on-the-fly to match their needs precisely. They have been buying computers with both hands tied behind their backs. Now they are in control.

Insanity 7mo ago
I disagree. There's definitely _some_ who will use these tools to build systems for themselves. But do you think the chef who's been pulling insane hours in the restaurant wants to come home and build his own software? Or the teacher who just had to deal with an annoying classroom all day? People want software that just works, they'll pay for it, they don't want to use their computers to build their own software. That idea is just software and computer geeks (said affectionately) projecting their own desires on a larger community.
- padolsey 7mo ago
  Does it have to be mutually exclusive? On-the-fly software does not destroy software. Gatekeeping software creation does not mean shoving the existing creators out, it just means creating a larger space that others can occupy, like when 'real' programmers had to slowly permit 'script kiddies' into their spaces. All feels a bit 'old guard' vs 'new guard'.
  - Insanity 7mo ago
    Not mutually exclusive, but I thought your initial post painted an overly rosy picture with the sentence "[..] allowing millions of people to finally use the devices they've been sitting in front of all these years". I don't think it's happening at this scale. I'll admit I have no real data to back that up, it's just a hunch really. But I find it hard to believe that those people whom previously weren't interested in building software are now suddenly interested to build stuff with an LLM. I'm sure _some_ people are doing this, and then they either hit roadblocks and quit or stick with it an learn actual software engineering. Looking at my non-tech bubble of friends and family, I don't see anyone actually doing that. I think it's a vocal minority that is doing this. That's just anecdata of course.

d--b 7mo ago

It’s called karma? We, software developers, as a profession took over countless crafts. It started with people doing calculations by hand, then moved on to people typing on typewriters and continued from there. People used to edit films with scissors and scotch tape. People used to place lead fonts on a matrix to print news articles. Databases used to be little cards made carefully by people whose job it was to organize and modify them. It’s a bit indecent for a developer to complain that LLMs took away the pleasure of molding a clay made of bits, while the robots we enabled to build took the actual clay off of potmakers actual hands. And what the author forgets to mention is that we got it good. Oh boy. As a software developer, I can work in any field I want. I started on video compression. I moved to finance. I make games in my spare time. I make plugins for music. And I get to be paid way more than my neighbor who’s a heart surgeon. I can work remotely 100%. I can go to a nice beach in Thailand, work 2 hours in the morning and enjoy the rest of the day, and still make more than the median salary in France, where I live. The grief is not the loss of the craft alone, it’s the loss of that craft that paid for your house. As they said: software is eating the world. Well, it is now eating itself. It’s only fair. The author is right though, human societies need to ask themselves whether they are willing to sacrifice all the crafts on the altar of productivity and convenience. The Amish decided they didn’t want to. It’s a bit of a weird choice, but it is a choice.

padolsey 7mo ago
Precisely. I dare say software developers bemoaning this new world don't realise that they - too - are supplanters of a prior world. A sweet irony.
dahlia 7mo ago
[dead]
chromacity 7mo ago
I think this is a bit facetious. Although software had a bunch of localized impacts, it killed only a handful of mainstream professions. People still had to typeset articles, there was just less lead involved. For a writer, switching from a typewriter to a keyboard didn't mean you somehow needed less skill to write. That said, I'm with you that it's tacky for software engineers to complain about their own hardships. We are some of the wealthiest and most pampered white collar workers out there, and we're not exactly innocent bystanders.

iwontberude 7mo ago

The author conflates two paradigms: The first is one of a child learning BASIC not for beauty but for making things happen on the screen. The second is an adult producing software not because he enjoys the act, challenge and workflow, but for shipping software. I don’t see any difference between the child learning BASIC for its beauty and the chase to make things happen on the screen. Secondly, there is a very profound difference between a child creating and an adult creating for profit. The profit motive changes everything, even for someone “doing it for the love of it.”

airbreather 7mo ago

All the whingers about AI - if it is as bad as you say, then you don't have a problem On the other hand, if it is not, then stop wasting effort arguing against the inevitable and use that effort to get ahead of the curve. Either way, whinging about it is the least effective use of your skills and time.

bakugo 7mo ago

> Craft-lovers and make-it-go people sat next to each other, shipped the same products, looked indistinguishable. The motivation behind the work was invisible because the process was identical. I do not agree with this assertion and I don't know why I don't see more pushback against it, neither here nor in the comments for the original post. If you're a "craft-lover" sitting next to and working with a "make-it-go person", odds are you will be very much aware of it. Even non-technical leadership is likely to be able to notice it if they're perceptive enough.

juris 7mo ago

i think anyone who feels dispossessed from the advance of technology should rekindle that spirit of hands-on adventure by looking at clay pots at the museum. the souls of a thousand hours sit there behind glass and valued for their richness and simplicity, against all odds, and people to this day carry on those traditions to improve the art. did the soul of pottery die with the industrial revolution? will your hand code? it won’t be for everyone, but it’s there for you. find a book by Soetsu Yanagi on the subject of “min gei” and it will help you.

dinkumthinkum 7mo ago

It seems like this is a Marxist that is recycling his posts through an LLM. This other post of his is eerily similar: https://writings.hongminhee.org/2026/02/acting-materialistically-in-an-imperfect-world/ https://writings.hongminhee.org/2026/02/acting-materialistic...

tuan 7mo ago

There's another camp that don't care about the craft AND also don't care about the product. This camp, wielding power of AI, is making life worse for the other two camps. I've been getting so many code reviews that are generated by AI, but the author does not even has the decency to self review the generated code before they send out pull requests. It feels like an insult sometimes. For example, unit tests that basically assert if `a = 1` after setting a to 1. Every PR now has lots of unit tests, but they test the implementation details, not the spec. So now every change that breaks their implementation details causes false positive test failures. This creates a self enforcing negative loop. Every PR now comes with tons of unit test fixes. People start responding to PR comments with something along the line of: I ask AI but it was not able to solve the problem, if you have a solution, LMK. Or another variant I see often is: I think this is wrong, but AI says this is fine, so I'll leave it as is. I see craft lovers or product people using AI effectively. I use AI daily too. But the above camp is making my day to day job sometimes unbearable.

justonepost2 7mo ago

I guess I’m not the target audience but the flood of articles about craft or “deep blue” feel like a psyop. When the middle class disappears and your comfortable salary is replaced by, at best, a $1000/mo UBI (that’s 12k per year by the way) most people won’t have time to think or care about this nonsense

roncesvalles 7mo ago

This is probably contrary to conventional wisdom (esp among the startup/VC crowd) but: there are very few scenarios where how quickly you build something matters more than the quality of what you build. The AI coding era has brought about an unhealthy obsession with speed of software dev (where "speed" is often measured by fallacious metrics like LOC pushed per day, but that's tangential). And it's obvious why, this is the main commercial value proposition (if you can build 2x faster, you need 50% as many devs). Except that the speed only comes "for free" until a certain point. Beyond that point, you're trading off quality for more speed, and this trade is almost never worth it. If it takes you 6 months to handcraft a high quality version of your product (with selective AI assistance only until the boundary where it's not eating quality), almost always this is a better approach than banging out some heavily vibe/agent-coded crap in 1 month.

gibbitz 7mo ago
Why is this never a "we can make more products" conversation with businesses? It's always about how many people we can not pay versus how many more things we can sell. I think this is very telling of where the message is coming from and how the tools are being sold. Typically a good thing would be creating more value for a company's consumers, not increasing unemployment. Are these tools to make our lives better or to increase profits for shareholders without taking risks?

deleted 7mo ago

[deleted]

jeremie_strand 7mo ago

[flagged]

_aavaa_ 7mo ago
The output of hand watchmaking is likely also indistinguishable to most customers. I am skeptical that people buying 250k watches can tell if the perfect design was done by hand vs done by machine. The manufacturers play up the handcrafted nature to justify.

pugchat 7mo ago

[dead]

delimit 7mo ago

I think the craft isn't gone, it's shifting. I use three different AI coding assistants depending on the task, and the skill is knowing what to ask for, how to review what comes back, and maintaining coherence across a codebase that multiple models have touched. The craft is now in system design, specification, and verification — not in typing the code yourself.