Oh yes. Enough turkey soup, frozen, to last the rest of the year

I think I would need to hire someone to post there for me

I just absolutely cannot with that place

Even without vibe coding there’s always the temptation to make the second system so toweringly abstract in order to account for every edge case discovered in the first system that it collapses under its own weight before serving a single hello world query

Haha yeah I know :D

-> everyone else is stuck maintaining the first system

The extra fun part was where it was supposed to analyze classified data and I didn't have clearance, so I could feed it the data but not know if the results were correct or even made sense.
Made debugging super-fun.

I think a future of all-LLM code is that all the time as a vibe. More or less.

Now if only we could convince my managers of this!

(…also jesus I really have been doing this for more than twenty years when did that creep up on me 😳)

This somewhat reminds me that I initially learned Matlab by being forced to read code that had been generated by python script.
Just the idea that would be the norm is completely nightmare inducing

And at least there it was generated in a deterministic way and you can maybe even inspect the Python script!

and I don’t have it because I’ve spent twenty years fixing other people’s code. So I think there’s some danger to not spreading that work around a little bit both from a social standpoint as well as a skills development one

Early in my career I kind of resented being the junior dev who got given the CTO or super-dev’s prototype and told to make it good because prototyping always felt like the fun part. Now a couple months into a big project of my own I’m realizing that there really is a skill to prototyping well

In general imho we have a large tendency to believe that outcomes are driven more by consistent individual traits than they are, as opposed to difficult to imagine but very powerful environmental effects. So for org leaders, I encourage identifying structural levers first!

-> When it becomes clear the second system will never launch he runs into the woods never to be seen or heard from again

Honestly I suspect it to follow the usual circle of life from before vibe coding, which was vibe code up an overgrown prototype -> it becomes structural for the company -> the original author is like “we can build a better second system” -> vibe codes up a second even more overgrown prototype

My worst case of this I had five direct managers and four skips in fifteen months

Or any one person’s individual tenure in them