I have this conversation (or a variation threof) with some friends: I suspect that the vast majority of “mainstream commercial software development” is flat out just cooked. We won’t be writing code, nor debugging it. It’ll will just be people throwing more LLM compute at everything.

Open source, hobbyist and personal projects will probably remain the last bastions of “human in the loop” and human-written code, and I suspect these circles will retract into smaller, tighter circles.

I’ve seen no discussion about what the social consequences are going to be if a predicted 2/3rds of people lose their jobs.

I don’t imagine they’re pretty.

Large swathes of this industry have an obsession with investing 10x more resources into the wrong thing, than simply fixing the underlying issue.

That’s why they spend all their time on LinkedIn creating “7 levels of ai readiness” instead of…actually doing anything productive and useful.

I’m curious to know why this requires a whole CRD + operator setup, instead of just being a deployment that watches config(s) somewhere?

Presumably a CR can be validated by k8s against a schema and will fail at an early step. I admit I like the operator-pattern.

You’re copping downvotes for this, but you’re not wrong.

“It will get better, and then we will use it to make many of you unemployed”

Colour-me-shocked that swathes of this industry might have an issue with that.

Nothing in this space “smells right” at the moment.

Half the “ai” vendors outside of frontier labs are trying to sell shovels to each other, every other bubbly new post is about this-weeks-new-ai-workflow, but very few instances of “shutting up and delivering”. Even the Anthropic C compiler was torn to pieces in the comments the other day.

At the moment everything feels a lot like the people meticulously organising desks and calendars and writing pretty titles on blank pages and booking lots of important sounding meetings, but not actually…doing any work?

I for one, would certainly prefer a wider ecosystem of _more refined_, less bloated tools.

The current system of a near-monoculture of garbage sucks.

Users care about performance and jank, it’s just that they’ve been successfully forced to shut-up-and-deal-with-it. They’re not involved in purchasing or feedback, and the people that are don’t use it enough to care, or just don’t care. Users who complain about it may as well shout into the void for how much companies take note, but hey, at least we got an ai button now!

Atlassian products are a great example of this. Everyone knows Atlassian has garbage performance. Everyone complains about it. Never gets fixed though. Everyone I know could write customer complaints about its performance in every feedback box for a year, and the only thing that would happen is that we’d have wasted our own time.

Users _care_ about this stuff. They just aren’t empowered to feedback about it, or are trained to just sigh and put up with it.

I find outside of specific use cases the performance and jank are down to the developers and not whether it's native or not

Obsidian is an Electron app which is pretty much universally loved. We can both give single examples

i think you've to be more nuanced here - perf becomes important only on the extreme. i think there are compromises to be made between perf and go-to-market.

“They just aren’t empowered to feedback about it, or are trained to just sigh and put up with it” is a roundabout way of saying users don’t care about it enough.

Software decisions are often not made by who will use said software.

Aaaaand that is why we, as end users get machines which are sluggish, because literally every. Single. Application is taking this attitude.

Shock horror, the waste adds up, and it adds up extremely quickly.

I don't really care about memory or how much of it is taken up by the editor. I have enough memory for the work that I do & UI performance would make no difference to my workflow.