Journal
Thoughts on frontend engineering, UI/UX, and the lessons learned building real products. Written from experience, not theory.

Engineering · October 21, 2025 · 2 min read
There's a quote that's been repeated so many times it's become background noise: 'There are only two hard things in computer science — cache invalidation and naming things.' Developers laugh, nod, move on, and then go name a function handleData that processes, validates, transforms, and persists three different types of records. The quote is right. The behavior doesn't change.
Read more
Engineering · September 8, 2025 · 2 min read
The complaint comes up in almost every team that adopts TypeScript: it's slower. Writing types takes time. The compiler is strict. Things that would have just worked in JavaScript now need annotation, inference help, or a proper interface before they compile. The complaint is correct. TypeScript does slow you down. The part people miss is that slowing you down is half the value.
Read more
Engineering · August 14, 2025 · 2 min read
Every developer has said it. 'It worked on my machine.' It's almost a rite of passage — your first prod incident, your first 2am Slack message, your first time staring at logs that make no sense because locally everything runs fine. But here's what nobody tells you in those moments: the bug isn't the problem. Your mental model of the system is.
Read more
Engineering · July 3, 2025 · 2 min read
Full-stack used to mean something. It meant you could build a feature end-to-end — handle the data, write the API, ship the UI. That's a legitimate skill. But somewhere along the way, it became a resume line that means 'I have done something on both sides of the network at least once.' And employers started hiring for it as if depth doesn't matter, and developers started leaning into it as if breadth is the same thing as mastery.
Read more
Engineering · June 4, 2025 · 2 min read
I've seen a lot of pull requests reviewed in a lot of codebases, and I've noticed a pattern: most code reviews are too polite to be useful. Comments like 'maybe consider extracting this?' or 'not sure if this is intentional?' wrapped in enough qualifiers that the author can safely ignore them. The reviewer feels like they did their job. The code ships as-is. And six months later, everyone's debugging the thing nobody wanted to call out.
Read more
Engineering · May 12, 2025 · 2 min read
At some point in almost every side project, and more than a few real ones, someone says it. 'We should design this to handle millions of users.' The project has twelve. The architecture discussion that follows costs a week, produces a document, and results in an abstraction layer that nobody ever needs to justify because the scale never comes.
Read more
Engineering · April 3, 2025 · 3 min read
Nobody teaches you how to read code. You get tutorials that walk you through writing it, courses that have you build things from scratch, challenges where you produce output from a blank file. But the moment you join a real team and open a real codebase — thousands of files, no author to ask, no walkthrough — you're on your own. And most developers are much worse at this than they realize.
Read more
Engineering · April 3, 2025 · 2 min read
I've seen it happen on almost every team I've been part of. Someone opens a new project, sets up the folder structure, and before a single feature is built — Redux is already in the package.json. Not because the app needs it. Because it feels like the responsible thing to do.
Read more
Engineering · March 10, 2025 · 2 min read
Every few months, a new wave of AI announcements rolls in and the discourse kicks off again: developers are done, designers are obsolete, just prompt your way to a product. I've been building software for a few years now. And honestly? I'm not scared. Here's why.
Read more
Engineering · February 20, 2025 · 1 min read
I resisted TanStack Query for longer than I should have. I had useEffect + useState patterns that worked. Why add a dependency? Then I used it on a real project and understood immediately why people rave about it.
Read more
Engineering · January 15, 2025 · 1 min read
It started as a simple data table. Filter, sort, paginate. Should've been a two-day job. It turned into a two-week experiment — and I'm glad it did.
Read more