What I'm curious about right now

I don't chase every new release, but I keep a short list of things I want to understand better — not because they'll look good on a resume, but because they scratch an itch.

AI agents in real workflows

Not the demo where an agent books a fictional flight. I'm interested in narrow, bounded agents: summarizing incident threads, drafting test cases from requirements, helping navigate unfamiliar codebases. The hard part isn't the model — it's guardrails, observability, and knowing when not to automate.

System design beyond interview questions

LeetCode system design feels like drawing boxes for an audience. Real design is negotiating tradeoffs with a team that has different risk tolerances. I've been revisiting how caching, message queues, and idempotency show up in systems I've actually worked on — not as patterns to name-drop, but as tools with costs.

Writing as thinking

This blog is part of that curiosity. Writing forces me to notice what I only vaguely believe. If I can't explain it in plain language, I probably don't understand it yet.

Sustainable pace

Less glamorous, more important. I'm paying attention to how senior engineers protect focus time, how they say no, and how they stay useful without burning out. That's a skill no course teaches.

Curiosity changes quarter to quarter. This is the snapshot for right now — a mix of technical depth and the quieter work of building a career that lasts.