I'm a big fan of this explanation/rant from Andrew Murphy.

Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

Debugging Leadership

So why are we still trying to optimize code creation?

For decades, people with power - executives and product people - have been shifting the blame for strategy failures and poor market insight onto development "productivity."

This AI moment should be incredibly clarifying. Like, it should be the reductio ad absurdum of a productivity-centric approach.

The fact that we are *not* seeing wildly improving software all around us tells us everything we need to know.

There is no flourishing of value delivery, new product categories, more needs being satisfied better. It’s the opposite.

All we are seeing is decreases in quality, because 👏 code 👏 creation 👏 is not 👏 the problem.

@elizayer @hbons give me some time. I’ve only been using LLMs to code for a few months… so far I’ve only managed to write an operating system https://codeberg.org/dpp/meows
A new scripting language https://codeberg.org/dpp/meowscript
An eBPF to FPGA converter https://codeberg.org/dpp/lycaon
And some misc utils
But this is weekend work
meows

A vibe coded OS that is a blend of microkernel and Erlang

Codeberg.org

@dpp @elizayer @hbons

after a few minutes with that codebase:
cool test case bro (it should check the const and not a hardcoded value) https://codeberg.org/dpp/meows/src/commit/73bb89ecc559b5bd023e2d179b1b0cef177a61e5/plugins/devmgr/src/probe.rs#L205

I found another bug typical for slop (discrepancy between an explaining comment and what the code actually does - comment is correct but code is wrong) and an architecture mistake, sadly you'll have to discover those yourself or pay me 🙃

meows/plugins/devmgr/src/probe.rs at 73bb89ecc559b5bd023e2d179b1b0cef177a61e5

meows - A vibe coded OS that is a blend of microkernel and Erlang

Codeberg.org

@dngrs @elizayer @hbons I appreciate that you’ve reviewed the code (I say this with honesty and no sarcasm)

There is plenty wrong with it. It’s about exploring, not a final shippable OS

The OP asked where the innovation is. This is an example of an OS (it boots on real hardware) that explores MACH style message passing and Elang style supervisor hierarchies

It’s part of broader exploration into local first and end to end encrypted systems