Building stuff with Go • Prev Dev Ed @ClerkDev, @PlanetScale • Follower of Jesus ✝️

Chicago, IL
👋 I’m beta testing Coalesce, an iOS app for people who combine training disciplines (ex: running + lifting) The app looks for conflicts across your whole week instead of treating each workout plan independently. I’m looking for a few free beta testers who train across multiple disciplines and are willing to give honest feedback. Reply or DM me if that sounds like you.
2
3
5
302
Also big SO to @BraydonCoyer for shipping Launchframe today. I used it to create the social graphic above. Super timely lol
I built a tiny tool for devs launching apps. It's called LaunchFrame. Add your App Store, Google Play, or website URL and it turns your app icon into a polished 7-second launch video, like the one below. I built this in my free time over two days. Here's how it works 👇
1
3
151
I’ve been using Notion as the operating system for my coding agents. Not just somewhere to dump notes when the work is done. The codebase tells them how the product works. Notion tells them what needs to happen next. 🧵
2
3
250
9/ I think durable context is a big part of making coding agents actually useful long term. The codebase gives them implementation context. Notion gives them the history and what needs to happen next. The Work Item gives them something concrete to finish.
1
29
10/ That’s been a much better setup than treating every agent session like a fresh start. The more context they can carry forward, the less time I spend re-explaining the project and the more useful they become.
23
Brian Morrison II retweeted
security-audit-skill is a Cloudflare coding agent skill for multi phase security audits. It outputs verified, machine readable findings for Cursor and Codex. 3,288 stars. github.com/cloudflare/securi…
22
201
2,132
155,321
I switched an active project from Claude Code to Codex expecting the handoff to be a mess. Instead, Codex picked up where Claude left off almost immediately. Here is a quick thread on my experience switching tools 🧵
5
1
4
517
10/ It's how little friction there was moving between them. We're getting closer to a workflow where the codebase is the source of truth and coding agents are interchangeable tools around it.
1
23
11/ Use one agent for a task it handles particularly well. Switch to another when the workflow or model fits better. Then switch back without having to rebuild everything. That feels much more interesting to me than picking a single winner.
27