My Tech Stack and Why I Use It

React framework with routing, server rendering, and API routes built in. The most productive way to build React apps in 2026.

Why I use it:

• Server-side rendering for SEO and fast initial loads
• API routes built in—no separate backend needed for simple things
• File-based routing is intuitive
• Great developer experience with fast refresh
• App Router (v14+) makes complex layouts easy

When I'd use something else:

• Simple static site → Plain HTML/CSS or Astro
• Complex backend logic → Separate Node.js/Python backend
• Mobile app → React Native or Flutter

Component-based UI library. Still the industry standard for building interactive interfaces.

Why I use it:

• Huge ecosystem—components, libraries, solutions for everything
• Easy to find developers who know it
• Component model maps well to how UIs actually work
• Great debugging tools (React DevTools)

When I'd use something else:

• Maximum performance critical → Svelte or Solid
• Very simple site → Plain JavaScript or Alpine.js

JavaScript with types. Catches bugs before they reach users.

Why I use it:

• Catches entire categories of bugs at build time
• Better autocomplete and documentation in editor
• Refactoring is safer—the compiler tells you what broke
• Self-documenting code—types explain what data looks like

When I'd skip it:

• Quick prototype or proof of concept
• Very small script

The upfront cost is worth it for anything that will be maintained.

PostgreSQL database with instant APIs, auth, and real-time subscriptions. Firebase alternative that doesn't lock you in.

Why I use it:

• Real PostgreSQL—not proprietary, you can migrate out
• Auth built in (email, social, magic links)
• Real-time subscriptions for live updates
• Storage for files and images
• Generous free tier (500MB, 50k users)
• Hosted in Singapore—low latency for Thailand

When I'd use something else:

• Complex backend logic → Custom Node.js/Python backend
• Non-relational data → MongoDB or Firebase
• Enterprise requirements → AWS RDS or managed Postgres

Utility-first CSS framework. Write styles directly in HTML with classes like p-4 and flex.

Why I use it:

• Fastest way to style components—no context switching
• Responsive design built in (md:flex-row)
• Consistent spacing/color system
• Small production CSS (only includes what you use)
• No naming debates—classes describe what they do

When I'd use something else:

• Existing design system → Their CSS framework
• Very complex theming → CSS-in-JS like Styled Components

Hosting platform built for Next.js. Push to GitHub, site deploys automatically.

Why I use it:

• Zero-config deployments for Next.js
• Edge network—fast globally
• Preview deployments for every PR
• Generous free tier (100GB bandwidth)
• Analytics, monitoring built in

When I'd use something else:

• Cost-sensitive at scale → Cloudflare Pages
• More control needed → DigitalOcean/AWS
• Static site → Cloudflare Pages or Netlify