My go-to starting point for fullstack projects is create-t3-app, which provides a clean foundation and scales well with project complexity.

I use Next.js for its powerful features like routing, code splitting, data fetching, caching, streaming, and server-side rendering. Even for client-heavy apps, having a server-side middleware layer often proves useful before interacting with APIs.

tRPC is the most productive way I’ve found to build APIs in a fullstack TypeScript app. It’s also easy to decouple later if I need to separate the API layer.

I'm a big fan of the TanStack ecosystem and rarely build a project without reaching for tools like Query, Form, Table, or Virtual.

For styling and rapid UI iteration, I use Tailwind CSS, and when building component libraries, I prefer a headless solutions like shadcn/ui or Radix (Keeping an eye on Base UI at the moment).

For fast prototyping and product iteration, I rely on tools like Cursor, V0.dev, and Mobbin.com to guide design and UX decisions.

Modularity and developer experience are core to how I build, and I prioritize technologies that keep me and my teams flexible without sacrificing scalability

I prefer building with a serverless-first mindset because it allows me to move fast, ship features quickly, and scale effortlessly without managing infrastructure.

AWS Lambda and modern frameworks like SST make it easy to focus on scaling products and teams with cost efficiency in mind. That said, I'm pragmatic — for workloads that require persistent compute, such as AI loads, WebSockets, or long-lived background tasks, I'm not afraid to bring in server-based solutions where they make sense.