LATEST NOTES:
No notes published yet. In the meantime, explore the projects and talk below.
No matching notes. Clear the search or try another topic.
See all notes →PROJECTS
THINGS I MADE BECAUSE I WANTED THEM TO EXIST.
Some started with a practical annoyance. Others began with a question I wanted to see moving.
I kept losing reference images behind my editor. Float is the small app I wanted: pin an image, adjust its opacity, and get back to what I was doing.
PathfindingI wanted to watch search algorithms make decisions instead of reading another diagram. This Rust/WASM playground lets you edit the grid, change the algorithm, and step through the search.
Kibana Log Investigation MCPI wanted agents to investigate logs through small, read-only operations instead of clicking through Kibana. This MCP gives them a structured path from source discovery to focused queries.
These are only the tidier ones. Everything else is on GitHub →
TALKS & EXPLANATIONS:
I like the moment an idea finally makes sense to someone else. This talk was my practical argument for using Rust where API reliability, performance, and cost matter.
THE QUESTIONS ARE OFTEN MORE INTERESTING THAN THE TOOLS.
I tend to circle around the same ideas, whether I’m debugging a system or starting a side project.
- What is really happening?
- I like tracing a problem through the whole system before deciding which part deserves to change.
- Can we make it click?
- I enjoy finding the diagram, example, or name that makes a complicated idea easier to carry.
- Who needs to understand this?
- Software becomes useful when the people around it can reason about it, question it, and change it.
- What happens if we test it?
- I would rather give an idea a fair experiment than argue about it in the abstract for too long.
“I have a weakness for good names. The right one can make an API contract, a meeting, or a half-formed idea suddenly click.”