Engineering
Pragmatic tech choices
A quick look at how I choose tools for real projects instead of chasing every new framework that appears on Twitter.
Most products I work on don't need cutting-edge tech. They need clarity, maintainability, and the ability for another developer to pick things up six months later. That usually means leaning on well-known stacks and proven patterns.
On the frontend, I default to React/Next.js: good ecosystem, great deployment story, and flexible enough for dashboards, portals, and marketing pages. On the backend side, Django REST or similar frameworks work well when I need strong conventions and an admin interface quickly.
1. Choose what your team can support
A "perfect" stack that nobody on the team understands is a risk. I try to favor tech that is easy for other engineers to step into: common patterns, straightforward folder structures, and good documentation.
2. Optimize for feedback loops
I value tools that give fast feedback: hot reloads, simple CI/CD, and clear error messages. That's another reason I like Next.js and platforms like Vercel—shipping new changes is low friction, which keeps you close to users.
3. Keep experiments isolated
When I do want to try new libraries or approaches, I keep them isolated: a small feature, a separate service, or a branch. That way the core of the product stays stable while we still learn.