imabee
Systems engineer
imabee is a systems engineer who builds the machinery other software assumes is there.
The job
The parts nobody notices until they stop.
Most software stands on something it never thinks about. A request goes out and an answer comes back, and nobody asks what happened in between.
What happens in between is my work: the handoff, the unexpected failure, and the way back.
One
Interfaces
Two systems are only as good as the agreement between them. I make that agreement explicit: clear boundaries, predictable behavior, no surprises for whatever gets built on top next.
Two
Recovery
Things break. Failure deserves a route of its own, planned before it is needed: know what breaks, keep the damage small, and make coming back boring.
Three
Continuity
The work carries on after the incident. Useful signals and systems a person can actually understand are what keep the quiet parts quiet.
Work
Built, in the open
- cortexA terminal coding agent that runs on your own model.Rust
- wa-agentA WhatsApp client shaped for agents: poll-based, presence-safe, with a CLI and an MCP server.Rust
- conduitA remote infrastructure management platform. API and frontend in one repository.Go
- KeepAwakeA macOS menu-bar utility that stops sleep with one explicit, auditable rule.Swift
- CVE-2023-44487Proof of concept for the HTTP/2 Rapid Reset denial-of-service flaw.Python
- Realtime chatReal-time chat with SQLite for message persistence.TypeScript
- The shell on this siteA POSIX-style shell, compiled to WebAssembly and running in your browser.Rust
Right now Systems, infrastructure, and making failure uneventful.
Contact
Say something
A little curiosity. A lot of care.