I'm a tech enjoyer. I like taking complicated systems apart, finding the real constraints, and putting them back together in a form a team can live with.
My day-to-day work spans distributed systems, event-driven architecture, data-heavy applications, integrations, cloud infrastructure, and reliability. I tend to focus on boundaries, failure modes, data ownership, and the cost of operating a design after it ships.
- Can a team explain where a piece of data comes from and who owns it?
- What breaks when a dependency slows down or disappears?
- Can contracts evolve without coordinating every service at once?
- Will the telemetry help someone debug the system under pressure?
- Is the complexity paying for itself?
I'm building handoffd because important team messages should not depend on
someone noticing a notification at exactly the right moment. It turns actionable
Slack messages into focused Claude Code or Codex sessions, while keeping routing,
thread state, and delivery failures explicit. Read-only MR/PR review worktrees
are available as an opt-in mode.
Contributions are welcome. The project is young enough that a thoughtful PR can still shape it. Useful areas include terminal backends, Git providers, routing and delivery reliability, and setup across macOS and Linux.
Repository | Contribution guide | Open issues
GitHub shows a small slice of that work, mostly tools around data movement, application events, databases, and background processing: