Tools & technologies I master.
I pick tools to fit the problem. This page explains what I use, why, and how I decide.
Connected, end to end.
- Next.js
- React.js
- JavaScript
- TypeScript
- Node.js
- MongoDB
- SQL
- Docker
- Git
My engineering stack focuses on developer productivity, code reliability, and user experience. From type-safe frontend architecture with Next.js 16, React 19, and TypeScript 5.9 to secure server infrastructure with Node.js, Express, Laravel, MongoDB, and MySQL, each tool is chosen to deliver fast, maintainable, and SEO-friendly software.
01 / Frontend
02 / API
03 / Database
Frontend
I use Next.js 16 for sites that need fast first loads and good search visibility, and React 19 for interactive applications such as dashboards; Server Components keep pages light by sending less JavaScript to the browser. TypeScript catches mistakes while I write code, not after users find them, and Tailwind CSS keeps styling consistent and quick to change.
- Next.js
- 95%
- React
- 98%
- JavaScript
- 98%
- TypeScript
- 90%
- Tailwind CSS
- 95%
- Framer Motion
- 85%
Backend
Laravel is a mature framework with built-in authentication, validation, queues and database tools; I use it for business platforms where structure and speed of development matter, as in VettedPool and NutriLeft. Node.js with Express fits when the frontend and backend share one language or I need flexible, lightweight APIs, as in HSFin.
- Node.js
- 90%
- Laravel
- 88%
- Express.js
- 92%
- REST APIs
- 95%
Database
MySQL for structured data with clear relationships, such as users, roles and hiring pipelines. MongoDB for flexible data, such as financial transactions and settings that change shape over time.
- MongoDB
- 85%
- MySQL
- 88%
DevOps & tools
Containers, version control and delivery pipelines.
- AI tools
- 95%
- Docker
- 85%
- Git
- 95%
- CI/CD
- 85%
- Linux
- 88%
Mobile & design
Interface design in Figma and responsive layouts for every screen.
- Figma
- 90%
- UI/UX Design
- 88%
- Responsive Design
- 95%
My approach to building.
Start simple. I use the fewest tools that solve the problem. Extra technology means extra maintenance.
Keep code modular. Small components and services are easier to test and change.
Validate everything. Every input is checked on the server, not just in the browser.
Measure performance. I check page weight, load time and Core Web Vitals before launch.
Write things down. Setup steps and decisions go into short documentation so others can continue the work.
AI tools in my workflow.
I use AI coding tools such as Claude Code, Cursor and GitHub Copilot to speed up routine work like boilerplate, refactoring and test drafts. I review everything they produce, because they can be wrong.
Read my AI tool comparisons →How I choose a stack.
- Content-heavy or SEO-driven site
- Next.js
- Complex dashboard or internal tool
- React with a clear API
- Business platform with roles and workflows
- Laravel + React
- Real-time or flexible data
- Node.js + MongoDB
Not sure what you need? Describe your project and I'll recommend a stack and explain why.
Describe your project →