It's clear that AI assisted coding is dividing developers (welcome to the culture wars!). I've seen a few blog posts now that talk about how some people just "love the craft", "delight in making something just right, like knitting", etc, as opposed to people who just "want to make it work". As if that explains the divide.

How about this, some people resent the notion of being a babysitter to a stochastic token machine, hastening their own cognitive decline. Some people resent paying rent to a handful of US companies, all coming directly out of the TESCREAL human extinction cult, to be able to write software. Some people resent the "worse is better" steady decline of software quality over the past two decades, now supercharged. Some people resent that the hegemonic computing ecosystem is entirely shaped by the logic of venture capital. Some people hate that the digital commons is walled off and sold back to us. Oh and I guess some people also don't like the thought of making coding several orders of magnitude more energy intensive during a climate emergency.

But sure, no, it's really because we mourn the loss of our hobby.

@plexus In the end, software engineering is about creating solutions to problems other people have. The solutions are not a byproduct, but the primary purpose. To the majority of users, the inner workings and the creation process of software is opaque. The qualities that software exposes on the outside are largely independent of its inner workings.

This means that for most people in the software industry, adapting to the new tooling that makes the creation process more efficient is 1/

Hans, except in the modern software industry, the problems that are being solved by software products are not those of the end users, but instead those of the company that makes it or its investors. You can't explain all the humiliatingly hostile UX decisions of the last decade of software otherwise. No user problems are being solved by onboardings that get in your damn way when you want to use the app for its one and only purpose in a hurry.

@grishka Right on, and then consider that with the traditional mode of writing software, the cost of creating something that is good is very high.

I'd argue that with faster (machine assisted) software creation, it is easier to meet the need of users because the cost of change is drastically reduced. I'm experiencing that with those system that I'm currently writing that way.

The whole argument that software written by humans is better does not bear any merit for me.

@hanshuebner What does "software is better" even mean in this context?

I wonder if this entire "LLM generated code is good enough and it's creation is much more efficient" argument will stand the test of time when a lot of code is generated on the same product / project by many people. We do not know the answer to this yet.
@grishka

@schaueho @hanshuebner @grishka

1/2

> "LLM generated code is good enough and it's creation is much more efficient" argument will stand the test of time when a lot of code is generated on the same product / project by many people. We do not know the answer to this yet.

I do suspect that some of the divide we see in the debate on Mastodon relates to the fact that some of the people arguing against it have not used LLMs to assist in writing Very Good Software At Scale using the methodologies available today.

I ship software to ~6 million monthly active users, with confidence, using Claude Code. I haven't written code by hand in ~10 months.

So, to the "We do not know the answer to this yet.", I think that we do.

We know that LLMs, used naively, make mistakes. And a craftsperson who knows the limitation of their tools (LLMs) can mitigate and verify in a number of ways.

Concession: LLMs were not ethically trained. Data centers are having awful impact on the energy grid + water use. I will never begrudge a person's choice to boycott.

Counterpoint: today, LLMs running on e.g. Apple Silicon approach the performance of the SOTA models. We're gonna see more of this, which will mitigate the individual's environmental impact as well as the need to pay forever-rent to big tech.

@schaueho @hanshuebner @grishka

I will never begrudge a person's decision to boycott LLM usage.

But I do grow weary of folk on Mastodon earnestly insisting that "the flaws in LLMs will somehow all be laid bare, and handcrafted, artisanal code is somehow inherently superior"

Y'all cheering for John Henry without understanding that this is a job that's actually very well suited for a machine.

https://en.wikipedia.org/wiki/John_Henry_(folklore)

John Henry (folklore) - Wikipedia

@dusk
OT, but cool John Henry video: https://www.youtube.com/watch?v=kt9NSMZR0dM
JOHN HENRY AND THE RAILROAD | Omeleto

YouTube