It's clear that AI assisted coding is dividing developers (welcome to the culture wars!).
-
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 we've all become luddites, in typical silicon valley fashion, they did it to themselves even.
-
@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 -
@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.
@grishkaHolger, as far as I understand the capabilities of LLMs, they only really produce a passable result when given a blank slate and the task at hand is some variation of gluing some libraries and/or REST APIs together.
-
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 It's honestly hard to express how I see it. As someone that has always been interested in tech I'm honestly curious about anything new but at the same time I don't like all the hidden natural and human cost behind it. I also hate being forced to use it because "we need to be an AI first company" and what I see here is the same process again: we hook you up, we lock you in and then we enshittify everything.
-
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 thanks for this framing, it is one that I can fully recognize myself in. I am uninterested in any so-called "AI"-assisted coding and I am not a very good coder, I came to coding via science, it is not a craft I have mastered or perfected in any way. but I do care about results making sense, code being maintanable, the socio-political economy of technology, labor, ecology, decolonial struggles and tending to my cognitive capacities...
-
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 "This mission is too important for me to allow you to jeopardize it...."
-
@plexus our hobby has always known culture wars
https://www.bennadel.com/blog/1682-coldfusion-vs-xyz-it-finally-got-physical.htmI think alot of colleagues don't have the luxury to choose, but have an employer that orders them to use AI.
When the draft of our strategy document was submitted i responded with some caution not to double down on the hype. I am fortunate that i can have a voice in this matter at my job.@moonshinebrigade @plexus I'm one oh that guys. At the beginning of the year, my manager told me "why didn't you use AI this month?".
I had to answer "dude, I was on vacation until yesterday"
-
@plexus It's honestly hard to express how I see it. As someone that has always been interested in tech I'm honestly curious about anything new but at the same time I don't like all the hidden natural and human cost behind it. I also hate being forced to use it because "we need to be an AI first company" and what I see here is the same process again: we hook you up, we lock you in and then we enshittify everything.
@plexus adding to this what about losing the craft? If you just review the produced code and never practice the craft anymore, you will lose it and then what?
There are tons of other things going on in my mind and at the top my 12 yrs old kiddo is getting hooked into programming without using LLMs. What should I say to him? Don't worry too much, do a shitty job you don't like because a bunch of VC sharks decided that's better to invest in machines than humans? -
@plexus adding to this what about losing the craft? If you just review the produced code and never practice the craft anymore, you will lose it and then what?
There are tons of other things going on in my mind and at the top my 12 yrs old kiddo is getting hooked into programming without using LLMs. What should I say to him? Don't worry too much, do a shitty job you don't like because a bunch of VC sharks decided that's better to invest in machines than humans?@plexus and my last point is that "us, developers" are an anomaly in the job market, well paid workers with many benefits doing the job they love. An anomaly that VCs want to be fixed...
-
…
- LLMs generate straw-fire software. It seems to burn at first, but it's not even hot enough to start a real fire.- This seems cheap in a very short-term view, and it might satisfy short-term “wants”, but it's not sustainable.
- We need to start fixing somewhere. Two holes in a bucket are not a dilemma, but two tasks.
@Ardubal @hanshuebner @plexus "Move fast and break things" has been one of the worst motivators of our time.
-
@hanshuebner @plexus I don't know what your point is?
-
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.
-
Holger, as far as I understand the capabilities of LLMs, they only really produce a passable result when given a blank slate and the task at hand is some variation of gluing some libraries and/or REST APIs together.
-
@hanshuebner @plexus I don't know what your point is?
-
@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/
@hanshuebner @plexus Did you ever read the toot you replied to before arguing with standard AI propaganda points?
-
@hanshuebner @plexus Did you ever read the toot you replied to before arguing with standard AI propaganda points?
-
@hanshuebner Thanks but I guess I will see the effects of using LLMs over a longer period of time on a bigger codebase at work anyway. I'm actually more concerned about the effects on the developers, which brings us back to Arne's original toot.
@grishka @plexus -
Hans, thanks but I'm not looking to change my workflow at this time. I'm fully satisfied with it as is now.
-
@hanshuebner @plexus yes and no. It‘s a systemic problem that needs a fix on a regulatory scale. But enough single devs opting out can also make a difference. Furthermore, regulation is done by politics, which in the end is the sum of the votes and voices of the people.
@can @hanshuebner @plexus
> on a regulatory scaleYou can't "regulate" anymore.
The one-hour income of the business to be regulated surpasses sum* of whole-live earnings of less than thousand politicians that might regulate.
*Sans the side channel paymnts from the unregulated.
-
@hanshuebner Thanks but I guess I will see the effects of using LLMs over a longer period of time on a bigger codebase at work anyway. I'm actually more concerned about the effects on the developers, which brings us back to Arne's original toot.
@grishka @plexus@schaueho @grishka @plexus I believe it is mostly a learning challenge. It was always possible and common to write bad and good software, and with LLMs generating code, new ways will need to be developed to ensure quality. This is the systemic part.
The personal part is that for some developers, their development activity changes. Merely writing code will not be a very common job for humans. Focus will be more on architecture, feature definition, requirements engineering etc.
