I share what I'm building, breaking, and fixing — from system design sketches to tiny bugs that taught me big lessons. If you're a recruiter, engineer, or curious builder, this is where you see how I think.
You can replace this with your own article later.
How I shipped a feature end-to-end: breaking down the problem, designing a clean API, avoiding hidden complexity, and leaving the codebase easy for the next engineer to change.
Read full post (coming soon)Shorter notes you can turn into full articles later.
A quick mental checklist I run before opening any profiler: state shape, unnecessary renders, and expensive work happening in the wrong place.
A race condition story, plus how better logging and simpler state design would have saved us hours.
Instead of chasing every new framework, I track my gaps around fundamentals, systems, and tools that actually compound.
Why predictable patterns beat clever tricks when you're building products that multiple people will maintain.
From editor setup to git habits — focusing on what removes friction instead of just looking "aesthetic".
Tiny lessons: off-by-one issues, async mistakes, and assumptions that were silently wrong in production.