Ben Johnson

@levelsio @litestreamio Let me know if you have any questions or feedback on Litestream!

💾 Finally set up @Litestreamio for the first time on 🏡 Interior AI to test It is open source and free and lets you add kind of a listener to your SQLite db which is constantly making a live copy of your databases to any S3-compatible bucket In my case I use Cloudflare's R2 In this case if I have a server failure, I have a literally as fresh as possible copy of my SQLite databases (which is the only db I use on all my sites) This is in addition to local provider backups, daily external backups, and cold storage off-site backups I have (e.g. the 3-2-1 Backup Rule!) Will let you know how it goes but it was VERY easy to set up so I can recommend it to anyone who uses SQLite!

Taking control of the #sqlite WAL - a deep dive into how rqlite lifts the lid on SQLite. And a h/t to @benbjohnson whose work on Litestream showed it was possible. philipotoole.com/taking-control…

@tqbf I didn’t want to believe it either but I heard it in an interview with him

I don't believe he said this.

@ibuildthecloud That hasn’t been my experience but I’m happy to talk through what it might be if you have any code to share. I put up a “Tips & Caveats” section for SQLite on the Litestream docs but I assume you’ve probably made all these tweaks: litestream.io/tips/

I can't be the only one right? I'm not an idiot, every time I use sqlite it's just not worth it because I don't know the magical incarnation or something to make it work. Then I switched to postgres. It's fine. Maybe someone needs to create a SQLite go driver that defaults to a sane behavior.

Annie really did do a killer job distilling Litestream down. I don’t even think I can explain Litestream in four minutes.

I just got opt-in, per-transaction synchronous replication working for litestream. I haven't written c in 25 years. The whole LLM thing is pretty neat

Wrote up about my personal journey from AI skeptic to someone who finds a lot of value in it daily. My goal is to share a more measured approach to finding value in AI rather than the typical overly dramatic, hyped bait out there. mitchellh.com/writing/my-ai-…

@mitchellh Thanks for the post, that was great. It lines up with a lot of how I use AI too. I find contexting switching to be brutal. I'm also not inclined to have multiple agents going at the same time because I expect agent performance will increase and it will be a moot point soon.

@nnajiabraham @wesmckinn @JonathanRoseD Yeah, Litestream would work well for the SQLite side. If you need to back up the DuckDB side though, I’m not sure what’s available.

@wesmckinn @JonathanRoseD Litestream by @benbjohnson should make this easier I think

I've used Gmail for 20 years. Almost 2M emails, 150K attachments. Rather than let Google hold my data hostage, I built msgvault: local-first email archive with a terminal UI and MCP server, powered by DuckDB. Open source, single Go binary. wesmckinney.com/blog/announcin…

I’ve noticed in the past when I tried CC for features in the past that it would get something fundamental wrong and then make later decisions based off those poor fundamental choices and the whole code change would be fucked. With a phased approach, I can’t correct those fundamental choices early.

@bradgessler @zeddotdev I haven’t tried Zed but I’ve found success with Claude Code when I make phased plans and step through each phase one at a time. It’s been good at spitting out a small bit of code that’s easy to review and it can help me in breaking up large feature work.

Tried using the Claude Code CLI for the first time and I gotta say, it's not a good way to build stuff with AI. Tools like @zeddotdev are great because you see the code by the agent output. What Zed doesn't quite get right is conversing with the agent about a git commit. Zed also has some major issues that result in "loss of work" including the "Reject All" button on the agent panel that zaps your work and the agent history gets wiped out on restart. Hopefully that gets fixed in the future!

@bradgessler Your company parties are going to be a hoot 🍻

@benbjohnson Hell yeah. I’m going to let them each present them at the Q1 kick-off offsite.

I’m not this deep yet, but my remedy for this is going to be treating AI a network of distinctly different assistants & advisors. Each agent will have its own name, email, Slack, 1Password vault, credit card, etc., kind of like a company. If an agent acts up, I’ll fire them.

I’m tempted to make a Chrome extension that hides all blog posts and YouTube videos that have the phrase “this changes everything” in it. Is everyone just asking Claude to make up their titles these days and that’s why they’re all the same?

@corylanou He's also the person that got me into writing Go more than 12 years ago. He's someone I look to for understanding upcoming trends more than anyone else.

I've been harassing my friend @corylanou to start recording his workflow with Claude Code. He's taught me so much on AI in the last few months and he finally released his first video! Check it out and give him some feedback. 🙏 youtube.com/watch?v=-GKBBM…

@fideloper Can you ask Claude to remove that guardrail from your Claude installation?

the whole point of this vm is to fuck it up!

@fideloper @aarondfrancis @steve_tenuto I just bought it! Thanks!

@benbjohnson @aarondfrancis @steve_tenuto it's good!

Working with @steve_tenuto for a year or two leveled up my video skills by like 10x, conservatively. One of the biggest hacks for that quality feel: filming the monitor is better than screen recording (also, buy a camera slider)

@fideloper @aarondfrancis @steve_tenuto Oh damn, how’d I miss that 🤦‍♂️

@benbjohnson @aarondfrancis @steve_tenuto my brother screencasting.com (unless you mean something else!?)