I struggle with the "good guys vs bad guys" framing here.<p>Is a small indie dev "dodgy" if they use AI to unblock a tricky C# problem so they can actually finish their game? Yarn Spinner seems to conflate "Enterprise Scale Replacement" (firing 500 support staff) with "assistive tooling" (a solo dev using GenAI for texture variants).<p>By drawing such a hard line, they might be signaling virtue to their base, but they are also ignoring the nuance that AI -- like the spellcheckers and compilers before it -- can be a force multiplier for the very creatives they want to protect.<p>Personally, I do agree that there are many problems with companies behind major LLMs today, as well as big tech companies C-levels who don't understand why AI can't replace engineers. But this post, as much as written in a nice tone, doesn't frame the problem correctly in my mind.
> I struggle with the "good guys vs bad guys" framing here.<p>It's because generative AI has become part of the "culture wars" and is therefore black and white to lots of people.
I think most people don't have an issue with the models themselves, just the big service providers who are up to some very shady and possibly illegal stuff.<p>Personally I'd rather a future where everyone used local models.
I think the only people they're calling "dodgy" are the ones offering these AI tools, and not the people using them.
Here is some text from the post<p>> You need to realise that if you use them, you’re both financially and socially supporting dodgy companies doing dodgy things. They will use your support to push their agenda. If these tools are working for you, we’re genuinely pleased. But please also stop using them.<p>> Your adoption helps promote the companies making these tools. People see you using it and force it onto others at the studio, or at other workplaces entirely. From what we’ve seen, this is followed by people getting fired and overworked. If it isn’t happening to you and your colleagues, great. But you’re still helping it happen elsewhere. And as we said, even if you fixed the labour concerns tomorrow, there are still many other issues. There’s more than just being fired to worry about.
One could probably think of dozens of reasonable arguments for avoiding LLM use, but this one is awful. If LLMs actually are able to get more work done with fewer people aka "firing people" that would be wonderful for humankind. If you disagree and like getting less work done with more people, you are welcome to forego tractors, dishwashers, the steam engine, and all the rest.
Yeah. This has been an interesting cultural shift, especially with “the kids”.
I’ve had at least a few people passionately tell me that using (non-generative, non-LLM) AI to assist with social network content moderation, is unethical, because it takes away jobs from people. Mind you, these are jobs in which people are exposed to CSAM, gore, etc. A fact that does not dissuade people of this view.
There are certainly some sensible arguments against using “AI” for content moderation. This is not one of them.<p>It’s really intriguing how an increasingly popular view of what’s “ethical” is anything that doesn’t stand in the way of the ‘proletariat’ getting their bag, and anything that protects content creators’ intellectual property rights, with no real interest in the greater good.<p>Such a dramatic shift from the music piracy generation a mere decade or two ago.<p>It’s especially intriguing as a non-American.<p>Again, as you say, many sensible arguments against AI, but for some people it really takes a backseat to “they took our jerbs!”
I can't speak to outside the US, but here companies have gotten much more worker-hostile in the last 30 years and generally the economy has not delivered a bunch of wonderful <i>new</i> jobs to replace the ones that the information age already eliminated (let alone the ones that people are trying to eliminate now). A lot of new job growth is in relatively lower-paying and lower-stability roles.<p>Forty years ago I would've had a personal secretary for my engineering job, and most likely a private office. Now I get to manage more things myself in addition to being expected to be online 24x7 - so I'm not even convinced that eliminating those jobs improve things for the people who now get to self-serve instead of being more directly assisted.
They took our jerbs is a perfectly valid argument for people which face ruin without a jerb.<p>Capitalism is not prepared nor willing to retrain people, drastically lower the workweek, or bring about a UBI sourced from the value of the commons. So indeed, if the promises of AI hold true, a catastrophe is incoming. Fortunately for us, the promises of AI CEOs are unlikely to be true.
This is the bit I get frustrated by - the need for jerbs at all.<p>If we manage to replace all the workers with AI - that's awesome! We will obviously have to work out a system for everyone to get shelter, and food, and so on. But that post-scarcity utopia of everyone being able to do whatever they want with their time and not have to work, that's the goal, right? That's where we want to be.<p>Jerbs are an interim nightmare that we have had to do to get from subsistence agriculture to post-scarcity abundance, they're not some intrinsic part of human existence.
I personally wish for the time when AI can replace everything I can do (at least in my current field). I'm not sure how exactly I'll feel about it then, but it'd be a technological advancement I'd enjoy seeing in my lifetime.<p>One question perhaps is, even if AI can do everything I can do (i.e., has the skills for it), will it do everything I do? I'm sure there are many people in the world with the superset of my skills, yet I bet there are some things only I'm doing, and I don't think a really smart AI will change that.
Yup. The problem was never with the technology replacing work, it was always with the social aspect of deploying it, that ends up pulling the rug under people whose livelihood depend on exchanging labor for money.<p>The luddites didn't destroy automatic looms because they hated technology; they did it because losing their jobs and seeing their whole occupation disappear ruined their lives <i>and lives of their families</i>.<p>The problem to fix isn't automation, but preventing it from destroying people's lives at scale.
<i>Would</i> being the operating word here. In a capitalist economy with wage labour, it is a catastrophe.
Does this argument still work if LLMs end up increasing unemployment and making it a lot harder for graduates to find good jobs? Who is it good for in that case, the shareholders? It's nice if humans can always create more jobs, but that's not what the tech bros are promising investors. They're making claims about how AI is going to seriously reduce the need for human labor. Programming, writing and art are just the starting ground for what's coming, if their predictions are anywhere close to being correct.
> This comment pops up a few times, often from programmers. Unfortunately, because of how messy the term AI now is, the same concerns still apply. Your adoption helps promote the companies making these tools. People see you using it and force it onto others at the studio, or at other workplaces entirely. From what we’ve seen, this is followed by people getting fired and overworked. If it isn’t happening to you and your colleagues, great. But you’re still helping it happen elsewhere. And as we said, even if you fixed the labour concerns tomorrow, there are still many other issues. There’s more than just being fired to worry about.<p>What other people and companies do because I happen to use something correctly (as an assistive technology), is not my responsibility. If someone happens to misuse it or enforce it use in a dysfunctional work environment, that is their doing and not mine.<p>If a workplace is this dysfunctional, there are likely many other issues that already exist that are making people miserable. AI isn't the root cause of the issue, it is the workplace culture that existed before the presence of AI.
I'd be more concerned when AI companies decide its time to make a profit. The more effective its supposed to be, the more they can justify charging for it.
> AI is now a tool for firing people<p>In essence we have an ownership problem. If I own the AI, I can do my work in couple of hours and then some and then have rest of the day off to enjoy things I like. If the company owns AI - I'm out of work. The difference between a world of plenty and beauty vs the world of misery for many of us - is who owns the AI.
> then have rest of the day off to enjoy things I like<p>But that's not what companies expect from you, even if you owns AI. They expect you to output more, and when you do, someone else is probably out of work.
It's like saying we won't use compilers because it puts all the people who would manually create punch cards out of a job
There is a difference here, though. Compilers and the languages they enable aren't out-and-out ripping off previous creations.<p>Lots of folks are mad about how the power of these tools comes from training things they put out in the open but didn't intend to be used to enrich or exclude others like this technology is enabling.<p>Interesting times ahead... it's so powerful people who ignore it are going to get left behind to some degree. (I say this as someone who actively avoids kubernetes and it does give off the vibe I've been left behind compared to my peers who do resume driven development.)
I wonder if the title of this post will someday be a certification?
programming is just turning calories/energy into text. some of you are just not that efficient at it, some of you produce garbage when you do. it's only been three years, there is still low hanging fruit on the new branches.
I’d love to work for a company like this, but when you said, “by the time we finished our doctorates,” I knew you were way out of my league.
I wish.
I have just witnessed a engineer on our (small) team push a 4k line change to prod at the middle of the night.
His message was: "lets merge and check it after".
AI can help good team become better, but for sure it will make bad teams worse.<p>I sorry friends, I think imma quit to farming :$
I don’t really see how this is an AI issue. We use AI all the time for code generation but if you put this on my desk with specific instructions to be light on review and it’s not a joke, I’m probably checking to see if you’re still on probation because that’s an attitude that’s incompatible with making good software.<p>People with this kind of attitude existed long before AI and will continue to exist.
Try to comply to an infosec standard. Typically one of many compliance controls are "every change must be reviewed and approved by another person". So no one can push on their own.<p>I know folks tend to frown on security compliances, but if you honestly implement and maintain most of the controls in there, not just to get a certificate -- it really make a lot of sense and improves security/clarity/risks.
If I could at all help it, I would simply not work somewhere with that sort of engineering culture. Huge red flag.
One should not be able to push to prod on their own especially in the middle of the night? Unless its a critical fix
> Unless its a critical fix<p>The bar for human approval and testing should be even higher for critical fixes.
Who cares, AI has lowered the bar. If AI can produce rubbish 20+% of the time, so can we.
There’s a weird thing going on - I can see value in using LLM’s to put something together so you can see it rather than investing time to do it properly initially.<p>But to just copy, paste and move on… terrible.
The reflexive and moralistic anti-AI takes are starting to get more annoying than the actual AI slop
I suspect a subpopulation of software development is going to become a bit religious, for a short while, split into "morally pure anti AI" and those who are busy using software as a means to an end to solve some real world problem. I think the tools will eventually be embraced, out of necessity, as they become more practically useful (being somewhere around "somewhat useful" right now).<p>As a result, I think we'll eventually see a mean shift from rewarding those that are "technically competent" more towards those that are "practically creative" (I assume the high end technical competence will always be safe).
Getting annoying, yes, not more annoying than the actual slop, though, that's ridiculous.
No they aren't.
I didn't either but I have now realised yes it uses a lot of energy and yes it can be a total waste of energy, but if you are doing good with it, then it is worth the cost.<p>I have decided I can only use AI that has a benefit to society at all. Say lower energy use apps for eink devices.
“You’ll get left behind if you don’t learn AI”<p>Left behind where? We all live in the same world, anyone can pick up AI at any moment, it’s not hard, an idiot can do it (and they do).<p>If you’re not willing to risk being “left behind”, you won’t be able to spot the next rising trend quickly enough and jump on it, you’ll be too distracted by the current shiny thing.
I read it as "compared to others, in the current context".<p>If you take some percent longer to finish a some code, because you want that code to maintain some level of "purity", you'll finish slower than others. If his is a creative context, you'll spend more time on boilerplate than interesting stuffs. If this is a profit driven context, you'll make less money, less money for staff. Etc.<p>> If you’re not willing to risk being “left behind”...<p>I think this is orthogonal. Some tools increase productivity. Using a tool doesn't blind a component person...they just have an another tool under their belt to use <i>if they personally find it valuable</i>.
If the people developing and supporting chat- and c0rn-bots are anxious about the future, that is the <i>correct</i> emotion to be feeling.
This article is silly. Your employees are using AI to get shit done whether you like it or not. They are just being sneaky about it.
[dead]
Didn't know yarn spinner was used to make so many cool games. Norco is a favorite from the last few years.<p>The anti-ai stance just makes em even cooler.
Here’s a paragraph summary of the story, written by Sonnet 4.5:<p>The Yarn Spinner team explains they don’t use AI in their game development tool despite having academic and professional backgrounds in machine learning—they’ve written books on it and gave talks about ML in games. Their position shifted around 2020 when they observed AI companies pivoting from interesting technical applications toward generative tools explicitly designed to replace workers or extract more output without additional hiring. They argue that firing people has become AI’s primary value proposition, with any other benefits being incidental. Rather than adopt technology for its own sake (“tool-driven development”), they focus on whether features genuinely help developers make better games. While they acknowledge numerous other AI problems exist and may revisit ML techniques if the industry changes, they currently refuse to use, integrate, or normalize AI tools because doing so would financially and socially support companies whose business model centers on eliminating jobs during a period when unemployment can be life-threatening.