It makes a great code reading tool if you use it mindfully. For instance, you can check the integrity of your tests by having it fuzz the implementation and ensure the tests fail and then git checkout to get clean again.

I got mine to bundle all that bs into a one word suffix "DISCLAIMER." which it puts at the end of responses now but basically doesn't bother me with that stuff.

Can you share that part of your prompt? Initial attempts are failing for me, but that would be a great outcome.

The marginal cost of a hob is likely not the price driver.

I was staying at a Maasai owned ecolodge in Kenya on the day they switched over from generator to solar. It was so much quieter, and with their new electric Range Rover they don’t ever have to go into town except for parts.

This reads like a timeline in a game of Civ. Love it.

If that’s your first thought, then you’ll hate this influential perspective: https://en.wikipedia.org/wiki/Worse_is_better

htmx forever

We handle this in Fireproof with a deterministic default algorithm, in addition to having a hash-based tamperproof ledger of changes. Fireproof is not SQL based, it is more like CouchDB or MongoDB, but with cryptographic integrity. Apache 2.0 https://use-fireproof.com

In practice during CouchDB's heyday, with lots of heavy users, the conflict management API almost never mattered, as most people can make do with deterministic merges.

It’d be amazing to see a collab with the Exquisite Creatures Revealed artist. He preserves all kinds of insects and presents them in a way that highlights the color and iridescent effects nature offers. I was so blown away by the exhibit I went back. Artist: https://christophermarley.com/

Yes, that exactly. If you have to read the code or the manual, you’re not vibe coding. I think vibe coding is super good for the industry and people in general.

If you can’t do it while you’re also singing a karaoke song, then you’re not vibing.

I have fairly decent engineering credentials, but when the task fits, I prefer to vibe code.