I just vibecoded with exe.dev and Opus 4.5 a backoffice for our FIPS 140 validation, with a separate view for the lab (where they can also upload test vectors), public links for clients, and guided scripts for testing. I have not looked at the code once. It works great. I am... processing this.

I dusted off the blog to explain how I set things up for writing code with @exe.dev

Backseat coding with a ghost driver

How Shelley and I write code together

skybrian.substack.com

I’d like a “seed your follow list with those you interacted with most on Twitter” for @bsky.app. ChatGPT didn’t return anything helpful. Am I alone?

about me: i like writing small programs that don't meet industry "best practices." they are easy to understand, easy to improve, and easy to make fast. let's make some better best practices.