Software, infrastructure, and everything in between.
A working notebook rather than a portfolio: the technologies I actually use, what each one is good for, and the small tools I build to understand them better.
01
By the numbers
Counted from the atlas itself, not typed in by hand.
- technologies catalogued
- 63
- used daily or in production
- 73%
- layers, from languages to game servers
- 8
- linked to other entries
- 63
- Infrastructure12
- Backend11
- Frontend9
- Languages8
- Tooling8
- Platforms & services7
- Game servers5
- Data3
02
What I do
The half of the picture that is not a list of tools.
- Full-stack: from the interface to the deployment, one person and one mental model.
- Web development: fast, accessible pages that survive real content.
- Software development: CLIs, services and integrations around the main product.
- Problem solving: turning a vague complaint into a small, testable theory.
- Technical troubleshooting: reading logs, isolating variables, finding the cause.
03
Daily drivers
The part of the atlas I touch every week.
- TypeScript
- JavaScript
- Vue 3
- Nuxt
- Pinia
- Vite
- SCSS
- Node.js
- Bun
- REST
- Zod
- PostgreSQL
- Docker
- Docker Compose
- Linux
- Git
- GitHub
- ESLint
- Prettier
04
In the lab
Small tools running live in your browser: no keys, no accounts, nothing sent anywhere.
JSON → TypeScriptPaste an API response, get interfaces you can actually keep.Contrast checkerCheck any two colours against WCAG AA and AAA, with this site's own tokens preloaded.Expected-value modelTurn probabilities and payoffs into one comparable number, then watch what one wrong guess does to it.Regex labWrite a pattern, watch every match and capture group light up as you type.What your browser saysThe user agent, the screen and a dozen media queries describe your device before you touch anything. Here is what this page can read — and where the official classification stops being true.
Open the lab 05