Technical Leader at Doxee by day β this account is everything else. Twenty-odd years of shipping frontends, which means my commit history reads like a tour of technologies that were definitely the future at the time: ActionScript, Flex, AIR, Haxe, and a brief but sincere belief in 3D in the browser via Papervision.
These days it's Vue, TypeScript and Node, plus a lot of thinking about how LLMs change the way we actually write software. Same job as always, really β take "wouldn't it be nice ifβ¦" and turn it into something that survives contact with production.
Mostly working with:
Previously, and fondly:
- ANE-Google-Analytics : Native extension wiring AIR apps to Google Analytics on iOS and Android. The one people actually used.
- robotlegs-utilities-macrobot : Sequential and parallel command batches for Robotlegs.
- robotlegs-utilities-starling : Same Robotlegs patterns, but on Starling and Feathers.
- ANE-Android-Expansion : Managing Android APK expansion files, back when 50MB was a hard ceiling.
These are archaeology now β the platform they targeted has been dead for years β but the issues still trickle in occasionally, which I choose to find touching. The rest of what's here is Advent of Code (350π so far), homelab bits, and the odd minimal reproduction for a bug I've filed somewhere.
A Proxmox cluster running Talos Kubernetes, deployed via GitOps, with NixOS for anything that needs to be reproducible. It is enormously more infrastructure than one person needs, and that is entirely the point.
The rest of the yak-shaving budget goes to my dotfiles β GNU Stow, zsh with Starship and a slightly embarrassing number of Oh-My-Zsh plugins, and Neovim on LazyVim that I keep failing to leave alone:
- I missed JetBrains' scope language enough to write a parser for it in Lua, so I can
filter the file explorer with
file:src//*.ts && !file://*test*. Recursive descent, the whole thing. Worth it? Unclear. Do I use it daily? Yes. - Follow mode, a toggle that rips out LSP, diagnostics and treesitter-context so I can watch Claude Code edit thirty files without tsserver deciding to reindex the universe each time. Syntax highlighting and autoreload stay β everything expensive goes.
Both of these are one good weekend away from being actual plugins. I keep meaning to pull them out into their own repos. Ask me again in six months and I'll tell you the same thing.
Twenty years next to designers taught me exactly enough to be dangerous, so I've been going the other way lately: Control Room, a neon-noir design language for dense operational dashboards, built the way I'd want to consume one β tokens as the source of truth, components authored once and compiled to six frameworks, four themes, and a set of laws explaining why each rule exists so future-me can't argue with it.
I want to be clear that I am learning this in public and out of my depth in the parts that matter. I can build the pipeline in my sleep; picking the colors is the hard bit. Turns out "just make the spacing consistent" is load-bearing advice that I have been nodding along to for two decades without fully appreciating.
π Modena, IT Β· π alebianco.dev Β· πΌ LinkedIn
/\_/\
( -.- ) "Fixed in the next release."
> ^ <
Opinions and cats are my own.



