I'm a TypeScript engineer who builds full stack web applications for a living. The kind of work where you start the morning arguing about database indexes and end it nudging a button two pixels to the left because something felt "off." I genuinely enjoy both ends of that spectrum, which probably says something about me that a therapist would find interesting. I've always believed a jack of all trades beats a master of one.
I have a hobby graveyard. Lego collecting, Rubik's cube solving, online sim racing - plenty of half-finished side projects. Every few months something new catches my attention, consumes me entirely, and then quietly joins the pile. This site exists so none of that feels wasted. If I learned something along the way, it deserves to be written down somewhere — even if the hobby itself didn't survive.
The plan here — and I'm using that word generously — is to write about whatever grabs my attention. Engineering stuff, mostly. Architecture decisions I've made that I'm either proud of or haunted by. Tools that changed how I work. Hobbies I'm currently enjoying. Anything else that comes to mind.
If any of it helps you solve a problem or avoid a mistake I've already made, fantastic. If nothing else, writing things down forces me to actually understand them instead of just vibing my way through implementation details and hoping nobody asks follow-up questions.
There's no schedule, no editorial calendar, and absolutely no newsletter signup modal that slides in right when you start reading. Just a developer with a text editor and the occasionally irresistible urge to put thoughts on the internet.