My grandma made Platonically Ideal Pies, and I took up the art years ago. Mine, if I say so myself, are quite good, given that with Grandma's example I know what I'm shooting for.
I haven't made one for a few years, though - having a pie in my house is a recipe for me eating 5000 calories of pie and vanilla ice cream over the next few days.
When my grandma died a few years ago, I asked my aunts if I could have one of her pie pans. Apparently none of her other 17 grandkids thought to ask that - so I got all three (philistines!). Those basic metal pans are among my most cherished possessions.
I might be tilting at a strawman of your definition of vibe coding - apologies in advance if so.
But LLM-aided development is helping me get my hands dirty.
Last weekend, I encountered a bug in my Minecraft server. I run a small modded server for my kids and I to play on, and a contraption I was designing was doing something odd.
I pulled down the mod's codebase, the fabric-api codebase (one of the big modding APIs), and within an hour or so, I had diagnosed the bug and fixed it. Claude was essential in making this possible. Could I have potentially found the bug myself and fixed it? Almost certainly. Would I have bothered? Of course not. I'd have stuck a hopper between the mod block and the chest and just hacked it, and kept playing.
But, in the process of making this fix, and submitting the PR to fabric, I learned things that might make the next diagnosis or tweak that much easier.
Of course it took human judgment to find the bug, characterize it, test it in-game. And look! My first commit (basically fully written by Claude) took the wrong approach! [1]
Through the review process I learned that calling `toStack` wasn't the right approach, and that we should just add a `getMaxStackSize` to `ItemVariantImpl`. I got to read more of the codebase, I took the feedback on board, made a better commit (again, with Claude), and got the PR approved. [2]
They just merged the commit yesterday. Code that I wrote (or asked to have written, if we want to be picky) will end up on thousands of machines. Users will not encounter this issue. The Fabric team got a free bugfix. I learned things.
Now, again - is this a strawman of your point? Probably a little. It's not "vibe coding going straight to production." Review and discernment intervened to polish the commit, expertise of the Fabric devs was needed. Sending the original commit straight to "production" would have been less than ideal. (arguably better than leaving the bug unfixed, though!)
But having an LLM help doesn't have to mean that less understanding and instinct is built up. For this case, and for many other small things I've done, it just removed friction and schlep work that would otherwise have kept me from doing something useful.
The ones that feel the most like they "get me" are probably Weird Studies and Very Bad Wizards. I'm a fan of Sam Harris's Making Sense podcast too.
When I want to dip into political news, I trust the Fifth Column guys to have fairly measured and reasonable takes with a vaguely libertarian bent. I have a handful of other political shows too from various perspectives of the aisle that I'll sometimes tune into when something big seems to be happening, but I generally don't consume much politics.
Also, I'd be remiss not to mention the excellent Knifepoint Horror, whose creator has been delivering exemplary horror short fiction of a very particular style for over a decade now. I always listen to those basically immediately after they come out.
At least in my experience, there's another mechanism at play: people aren't making it visible if AI is speeding them up. If AI means a bugfix card that would have taken a day takes 15 minutes, well, that's the work day sorted. Why pull another card instead of doing... something that isn't work?
If one has a github sub, you can use OpenCode -> github -> \A models. It's not 100% (the context window I think is smaller, and they can be behind on the model version updates), but it's another way to get to \A models and not use CC.
Yup, the context window there is only half of what you get in CC so only a weak alternative. They burned bridges with the dev community by their decision to block any other clients
When did they successfully close the loophole? I know they tried a few times, but even the last attempt from a week or two ago was circumvented rather easily.
Oh, sounds like I'm just out of the loop then. I had an Opencode install that I was planning to check out, and then like, the next day there was the announcement from a week or two ago, so I just kinda shrugged and forgot about it.
It's not really that the 4th amendment is less applicable, it's that the procedural protections are lower in civil proceedings.
I think it's a pretty big undersell to describe ICE as "marshals" too - they've got plenty of discretion in how they prioritize targeted people and who they detain. They are not just a neutral party executing court orders.
In theory yes, but in practice it's more unclear. There are conflicting Supreme Court precedents, that weaken the Fourth Amendment in cases where criminal penalties don't apply. Asset foreiture is another example.
> I think it's a pretty big undersell to describe ICE as "marshals" too - they've got plenty of discretion in how they prioritize targeted people and who they detain. They are not just a neutral party executing court orders.
Yep. That's also a difference between theory and practice.
reply