Software developer and DevOps engineer. Most of what I build is private, these are the public bits.
| Project | What it is |
|---|---|
| kshows | Shows a Kubernetes cluster as physical space: nodes as rectangles, pods sized by real usage vs. requests. Read-only, single Go binary. |
| tmop | Task Manager OverPowered: a skinnable Windows system monitor in Rust. |
| forge | Offline-first, single-binary MCP runtime manager. |
| stapler | PDF merging tool in Rust. |
| mc-admin | Web UI for administering a Minecraft server over RCON and HTTP. |
| Project | What it is |
|---|---|
| Botmate | Describe in a few sentences how your chess bot should play, then watch it take on other players' bots in the arena. |
I wrote a lot of code by hand before. Now I'd rather design the system and let AI do the implementation, as long as I still understand how it works.
I don't read everything. tmop is mostly unread (Rust is ugly), and so is most of kshows: I needed a tool for my own cluster and it works. Anything that involves other people, money or data, I read properly.
I build my own CLIs and TUIs to manage agents and run them in parallel. I don't follow a fixed workflow and keep tweaking it.
AI is a great tool if you bring some common sense: solid software engineering and CS fundamentals, an eye for long-term maintenance, and an honest idea of what AI can do and what it can't, yet.




