Working on a way for us to communicate software changes properly with people, systems and AI.
I'm frustrated at how we just do library updates and get whatever is next. Things break. Finding a changelog sucks. Vendor updates maybe put something in X.
We can do better so I'm starting an open initiative to tackle that.
Are you using multiple agents on the same project? If you are, use git worktrees.
I personally prefer 3-4 concurrent terminal sessions, working on different projects. Claude code usually runs around everywhere with agents, and sometimes takes 20 minutes to get shit done. During that time I'm shipping open source work, etc.
I use my own tools to help: Sugar and RemembrallMCP.
Sugar is used for memory that's stored outside sessions. So I say store this in sugar memory. If I open a new claude session later, and ask it to lookup sugar memory, it's there.
RemembrallMCP is a AST and code graph that helps the agents understand change impact of your codebase. Instead of insane greps veritical and horizontal, it uses this to quickly understand impact with very high accuracy, time reduction and low token limits.
Have them show you and talk about what they built. If they are not curious and building side projects, doing open source for excitement and making an app for a friend's business, their family member or some passion project, to me that's a red flag.
We are in a new age when the barrier to building is literally the lowest it's ever been. If your GitHub still is a dead graveyard fix that immediately.
I have over 2k commits in 2026 alone and I'm not even an IC anymore. Not including my work account.
I have like 12 side projects being built usually, working on 3-4 in parallel. A few are open source and growing.
All of this has helped me learn at a crazy rate. If your candidate is still just slogging 9-5, doing stand-ups then clocking out without anything extra.... That's all you need to know.
Curious, self learning, high potential people with a track record and good communication skills. That's it.
This looks to solve something I've been struggling with in my project, Sugar (1). Using the SDK and having sub agents running I found it difficult to have real- time insight into exactly what they were doing.
You can create a huge task list and Ralph mode can crank through it and also store persistent memory.
I'm frustrated at how we just do library updates and get whatever is next. Things break. Finding a changelog sucks. Vendor updates maybe put something in X.
We can do better so I'm starting an open initiative to tackle that.
reply