Compiler · language design · semantic analysis · ownership · data flow · LSP
I contribute upstream when I find something worth fixing, simplifying, or extending.
What I tend to optimize for
- explicit semantics and predictable behavior
- small, understandable abstractions
- centralized invariants rather than scattered special cases
- architecture that makes incorrect implementations harder to introduce
- codebases where a change does not require reconstructing the entire system in your head
How should the system be structured so the next change is difficult to get wrong?
| Languages | Go · C · Rust · C++ · TypeScript · Python · C# · Lua |
| Frontend | SvelteKit · Astro · React |
| Compiler work | Parsing · Semantic Analysis · Type Systems · Ownership · Data Flow · LSP |
| Systems | Linux · Networking · Databases · IPC · Platform Abstractions |
| Tooling | Git · Zed · VS Code · CMake |





