RE: https://cosocial.ca/@mhoye/116148772813747144

To expand this point: software is composed of code, organizational processes, and people. A surprisingly large number of software developers are narrowly focused on generating code and miss all the surrounding processes and people (humans' skills, knowledge, understanding of goals) that make that code usable.

Even if you accept "it's so good at generating code" (and I'm skeptical it'd be capable of doing a lot of things I've worked on, like memory profilers), that still doesn't address the costs in other categories:

- Degradation of processes. For example, you get denial of service on code reviews, which means code reviews go away, "it passes tests, it's fine!"

- Degradation of people's skills and knowledge. If it breaks, no one will know how it works because no one really understands the code. Especially once you've given up on code reviews! And an experienced engineer can only control an agent because they have experience _writing code_. If you stop writing code, those skills degrade. And if agents are all you're using, new programmers don't get that experience at all, and control of the agent degrades even more.

For more on this narrow focus on artifacts, and not the surrounding organizational processes and structure, I highly recommend the book "What Machines Can't Do: Politics and Technology in the Industrial Enterprise", by Robert J. Thomas. It has nothing to do with AI, it's about manufacturing, but even so you see the failure modes from what he describes as having only "an aesthetic of product", and no "aesthetic of process". Similar failure modes (throwing things over the fence) resulted in the original DevOps movement, which was a political movement, not a job title.

@itamarst
THIS is the bit that the VCs & many CEOs miss.

The software is doing a great deal of the work, yes. But the success of the company as a whole is dependent on the PEOPLE in the company understanding the customers’ problems, as (oft poorly) described by the PEOPLE who work at the customers’ companies… then adjusting the software as needed to solve those problems, once they’re clearly understood.

AI can help with that, sometimes a lot. But AI can’t DO all of that.

@itamarst
But VCs will happily trash stability & longevity for a tiny bit more short term profits.

Burn it all, so long as I can exit this shit-hole with more wealth.

Stupid, vile fuckers.

@kelvin0mql Definitely part of it is the focus on short wealth extraction (not really profits though, but rather the exit price). But also, my sense is VCs find workers to be _distasteful_. Wrote about this here: https://codewithoutrules.com/2018/11/09/the-cold-incubator/
The cold incubator: the VC dream of workerless wealth

Chicken incubators are hot: eggs need heat to thrive. This was a different sort of incubator, a glass enclosure within a VC office. The VCs had the best views, but even we could look down ten stories and see the sun sparkling on the Charles River and reflecting off the buildings of downtown Boston. It was summer when I joined the startup, but even so the incubator was freezing. The thermostat was skewed by a hot light sensor right below it, and the controls reset every night, so mornings were frigid. I took to wearing sweaters and fingerless gloves; the team at the other side of the incubator had figured out a way cover the AC vents with cardboard in a way that wasn’t visible to passersby. But I didn’t have to suffer from the cold for very long. Soon after I joined the startup I unwittingly helped trigger our eviction from the rent-free Eden of the incubator to the harsher world outside. The fall from grace Most of the people who worked out of the incubator just used a laptop, or perhaps a monitor. But I like working with a standing desk, with a large Kinesis keyboard, and an external monitor on top. My desk towered over everyone else: it was big and imposing and not very neat. Which is to say, the incubator started looking like a real office, not a room full of identical tables with a few Macbook Airs scattered hither and yon. And standing under the freezing air conditioner vent made my arms hurt, so I had to setup my desk in a way that was visible from the outside of the incubator. And that view was too much for one of the partners in the VC firm. There were too many of us, we had too many cardboard boxes, my standing desk was just too big: it was time for us to leave the incubator. The dream of workerless wealth VCs take money, and (if all goes well) turn it into more money. But the actual reality of the work involved was too unpleasantly messy, too uncouth to be exposed to the sensibilities of wealthy clients. We had to be banished out of sight, the ever-so-slightly grubby realities of office work hidden away, leaving only the clean cold dream of capital compounding through the genius of canny investors. This dream—a dream of profit without workers—is the driving force behind many an investment fad: The dream in its purest form, Bitcoin and cryptocurrencies promise wealth pulled from thin air, spinning hay into gold without the involvement of any brutish Rumpelstiltskins. Driverless cars promise fleets of assets without those dirty, messy, expensive drivers; but until they come round, Uber and Lyft’s horde of drivers are safely kept at a distance as independent contractors with five star reviews. Artificial intelligence promises decision making without human involvement, an objective encoding of subjective prejudice that will never feel moral qualms. And if you work for a VC-funded startup, this dream takes on a nightmarish tinge when it turns to consider you. Unbanished—for now The point here is not that VCs want to reduce effort: who wouldn’t want a more efficient world? The dream is not driven by visions of efficiency, it’s about status and aesthetics: doing actual work is ugly, and paying for work is offensive. Of course, some level of work is always necessary and unavoidable. And so VC firms understand that the startups they fund must hire workers like me and you. But the cold dream is always there, whispering in the background: these workers take equity, they take cash, they’re grubby. So when times are good hiring has to be done as quickly as possible, but when times are bad the layoffs come just as fast. And when you are working, you need to work as many hours as humanly possible, not because it’s efficient—it isn’t—but because paying for your time is offensive, and so you better damn well work hard. Your work may be necessary, but to the cold dream it’s a necessary—and ugly—evil.

Code Without Rules