Since Fable, my legit infrastructure project has turned into the sort of thing I can do 95% on my phone. It’s reliable enough instead of doing big reviews, I’ve just been giving it smaller tasks, and dozens in parallel.
I created a skill that’s focused on getting PRs merge-ready, and now my attention is fully back where it should be, on deciding what changes will make the product better.
Our entire stack is Apache 2.0 open source, including the agent docs, so if you wanna try sitting at a higher level of abstraction, install the skill in your repo or just clone our whole project and start adding features: https://good.vibes.diy/blog/beast-mode-skill-for-claude-code
The only reasonable solution shape I've seen is the one that trusts the parents to set an operating system setting that says whether or not the user is allowed to access adult content. And so it doesn't actually verify age, it just verifies parental intent.
Thanks for sharing your perspective. It’s reminding me of how I was feeling about crypto in the early days. I begin specifying a project on those lines way back when and the ideas behind it are still interesting. Maybe you’ll enjoy: https://www.wired.com/2014/07/document-coin/
One of the thing is we’ve seen at vibes.diy is that if you have a list of jobs and you have agents with specialized profiles and ask them to pick the best job for themselves that can change some of the behavior you described at the end of your post for the better.
Certain workflows prefer non-queueing, for instance the throng empowers the bartender to load balance different groups, delay drinks to over consumers, etc etc. So other cultures can have those workflows in places we might not expect, that is not necessarily a matter of respect. In pub culture, queueing disrespects the bartender.
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.
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.
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.
https://vibes.diy
[email protected]
CouchDB / Couchbase Mobile / $BASE