Write the decision, not the meeting
tipIf a remote discussion needs a call, start with a short written proposal: context, options, recommendation. Meetings go faster when the thinking is already visible.
Off the clock
Personal stuff
Films, books, tools I actually reach for, small snippets, channels and blogs I follow, plus the devices I use (affiliate links where noted). Dummy seeds included; I'll swap in the real picks over time.
Toolkit
Daily driver apps
The tools I keep open every day.
Daily drivers
Favorite tech stack
Not everything I've touched, just the tools I prefer when I get to choose.
Typescript + Hono + Tanstack Router + Anvia
#01Default for production full-stack AI applications that strong, fast, scalable and reliable
Next.js
#02Fast path from idea to shipped UI without fighting the type system. I only use this for small to medium scale
Python
#03Python is my go-to language for data analysis, automation, reporting, visualization, and building data-driven insights.
Langfuse
#04Agentic work without observability is just vibes. Traces keep me honest.
Figma/Excalidraw
#05I sketch systems before I code them. Shared pictures beat long threads.
Pocket notes
Snippets
Short tips and tiny code bits. Seeded with placeholders for now; more coming.
Diagram before the ticket
tipBefore opening a PR for a change that spans services, I draw the request path on a whiteboard (or Excalidraw). Half the bugs die in that sketch.
Prefer early returns
kotlinfun process(order: Order?): Result {
if (order == null) return Result.Invalid("missing order")
if (!order.isPaid) return Result.Invalid("unpaid")
return Result.Ok(fulfill(order))
}Always EXPLAIN the scary query
sql-- Before shipping a hot path query:
EXPLAIN ANALYZE
SELECT ...
WHERE ...;Watchlist
Five films I keep recommending
5 films · links open on Letterboxd
Want the professional side?
Experience, services, and selected work live on the rest of the site.