Skip to main content
Alvin QuachFull Stack Developer
HomeProjectsExperienceBlog
HomeProjectsExperienceBlog
alvinquach

Full Stack Developer building systems that respect complexity.

Open to opportunities

AQ

Projects

  • All Projects
  • Hoparc Physical Therapy
  • OpportunIQ
  • Hoop Almanac
  • SculptQL

Knowledge

  • Blog
  • Experience
  • Interview Prep

Connect

  • Contact
  • LinkedIn
  • GitHub
  • X

Resources

  • Resume
© 2026All rights reserved.
Back to Blogs
Decision
Featured
Depth: ●●○○○

Why GraphQL Over REST for This Portfolio

Tradeoff analysis: type safety, bundle size, and the portfolio signal of using GraphQL.

Published January 10, 20261 min readImportance: ★★★☆☆
Share:

When building this portfolio, I had a choice: use Sanity's native GROQ queries or implement a GraphQL layer. I chose GraphQL, and here's why.

The Tradeoffs

GraphQL adds complexity - codegen, schema management, additional build steps. But it also provides end-to-end type safety and signals to recruiters that I can work with modern data fetching patterns.