Alice Averlong🏳️⚧️it's especially funny seeing the "aren't you worried about getting left behind?" argument about AI, speaking as a retrotech person.
Like, come on. I'm still writing software for DOS and Windows 95. What even is "behind" at this point?
Brooke Vibber 
@foone I'm not concerned about being left behind, but I do worry about the people who are going whole-hog into outsourcing their cognitive capacity to a venture-capital backed bubble economy. I think a lot of them are going to be in for a rough shock when the prices go up by an order of magnitude and many of the vendors stop updating their models.
solo “claire” esta bien@brooke @foone this, but it also feels to me that vendors updating their models will have just as much impact on maintenance of systems. Suddenly you need to rework everything because your model says all that way of doing things was wrong. Are the prompts the code? Are we programming in natural language yet really? (I don't actually care for suggestions here, I am speaking rhetorically)
EntitasI concur and add further:
Let's say some new paradigm in development comes out. You think Claude's gonna have training data to be able to vibe code it for you? Hell no. All it can do for you is poorly port things into Rust while everyone else is moving onto this new hotness. You got a few years and models before the training data catches up to do it reliably.
AI, by nature of being dependent on things already made, leaves *you* behind.
@TheEntity @brooke @foone but consider their larger play, this is all a great opportunity for AI companies who eek out a lead in the code generation tool side to drive the cloud OS, services and libraries of the future. the agents will be so much more productive (less likely to malfunction) in their environments. they will own the stacks completely. write code on your own computer? unsafe! what are you some kind of hacker?
Eric Goodwin@brooke @foone @kimcrawley was on a call the other day with a developer who literally copy and pasted an error message into whatever the redacted they use now for development rather than go look at the line number in the error message.
RyeNCode 🇨🇦@auxonic @brooke @foone @kimcrawley
I had a short and painful stint where their production env was always had full stack traces visible to clients. Both the product and the dev of it was very LLM focused.
The same things done five or six different ways throughout the codebase, little to no Documenting Comments (dotnet c# based), fractured class hierarchy,
I can't blame LLM coding on all of it, there was a legacy beyond that there too, but the influence of auto-incorrect was strong.
I had a short and painful stint where their production env was always had full stack traces visible to clients. Both the product and the dev of it was very LLM focused.
The same things done five or six different ways throughout the codebase, little to no Documenting Comments (dotnet c# based), fractured class hierarchy,
I can't blame LLM coding on all of it, there was a legacy beyond that there too, but the influence of auto-incorrect was strong.
Emma: ƒ(☕️, 🐈⬛️, 🚀️) ⇒ ℂ