https://bsky.app/profile/j-chris.bsky.social/post/3m2zjzshad...
1,874 karma · joined June 8, 2017
https://vibes.diy
jchris@vibes.diy
CouchDB / Couchbase Mobile / $BASE
https://bsky.app/profile/j-chris.bsky.social/post/3m2zjzshad...
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
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.
I have fairly decent engineering credentials, but when the task fits, I prefer to vibe code.
Then MCP and other agents can run wild within a safer container. The issue here comes from intermingling data.
How many musicians or artists are finding their need to explore similarly met by opportunities that simply didn’t exist in 2002? If art is expression than we should expect the people who might have wielded a brush or guitar to be building software instead.
If this is you, I recommend Rick Rubin’s The Creative Act. It’s as pure an expression of the way I like to work in music, as it is aligned with how I think about code and product design.