Front end
- React
- Next.js
- TypeScript
- JavaScript (ES2023+)
- HTML5 & CSS3
- Tailwind CSS
- Responsive UI
Toolbox
Technologies I build with
The stack I reach for across front end, back end, data, and commerce — grounded in the languages, frameworks, and tools I use on client work.
Back end
- Node.js
- Express.js
- Django
- Python
- REST API design
- Authentication & sessions
Data
- PostgreSQL
- Supabase
- MongoDB
- Schema design
- Query & index tuning
Commerce
- Shopify
- Liquid templating
- Theme development
- Product & checkout UX
Tools & workflow
- Git & GitHub
- VS Code
- Vercel
- Postman
- Figma (design handoff)
Practices
- Technical SEO
- Core Web Vitals
- Accessibility
- Performance budgets
- Clean architecture
Approach
Right tool, right job
I don't pick technology for its own sake. The stack is chosen to fit the product: how it will grow, who will maintain it, and what it needs to do on day one versus year three.
A content-heavy marketing site might call for a static or Next.js build; a data-heavy internal tool for Django and PostgreSQL; a storefront for Shopify and Liquid. I care more about the fit than the logo.
- Primary stack
- React · Next.js · Node.js
- Secondary
- Django · Python
- Databases
- PostgreSQL · Supabase · MongoDB
- Commerce
- Shopify · Liquid
Need help choosing a stack?
Tell me what you're building and I'll suggest a pragmatic path — even if it's not the one I'd normally reach for.