01
06Languages
01
TypeScript / JavaScript
02
Python
03
Go
04
Java
05
SQL
06
HTML / CSS
Capabilities
Knowing a lot of tools is only useful if you know when to use them and how to ship with them. Here's what I work with and how I think about building things.
01
Languages
TypeScript / JavaScript
Python
Go
Java
SQL
HTML / CSS
02
Frameworks & Libraries
React and Next.js
FastAPI
Spring Boot
ExpressJS
Angular
TailwindCSS
Hard skills
Hard skills
End-to-end SDLC
Granular AuthZ
Scalability by design
Service boundaries (DDD)
Large-scale refactoring
Performance tuning
AppSec
Microservices
Soft skills
Soft skills
Turning business requirements into technical plans
Taking ownership and following through
Breaking down problems from first principles
Collaborating without ego
Simplifying things that don't need to be complex
02
06Frameworks & Libraries
01
React and Next.js
02
FastAPI
03
Spring Boot
04
ExpressJS
05
Angular
06
TailwindCSS
Hard skills
Hard skills
01
End-to-end SDLC
02
Granular AuthZ
03
Scalability by design
04
Service boundaries (DDD)
05
Large-scale refactoring
06
Performance tuning
07
AppSec
08
Microservices
Soft skills
Soft skills
01
Turning business requirements into technical plans
02
Taking ownership and following through
03
Breaking down problems from first principles
04
Collaborating without ego
05
Simplifying things that don't need to be complex
How I work
How I work
The stack changes from project to project, but the way I approach work stays the same.
01
Requirements
Understand what we're building and why, then turn that into something concrete enough to start.
02
Architecture
Figure out the services, interfaces, data flow, and security model before things get complicated.
03
Implementation
Write the code across frontend, backend, and infrastructure. Make practical trade-offs, not ideological ones.
04
Release
Set up CI/CD, run the checks, and get the thing to production safely.
05
Maintenance
Refactor, simplify, and tune things so the system stays healthy as the product grows.
How I work
How I work
The stack changes from project to project, but the way I approach work stays the same.
01Requirements
02Architecture
03Implementation
04Release
05Maintenance
01
Requirements
Understand what we're building and why, then turn that into something concrete enough to start.
02
Architecture
Figure out the services, interfaces, data flow, and security model before things get complicated.
03
Implementation
Write the code across frontend, backend, and infrastructure. Make practical trade-offs, not ideological ones.
04
Release
Set up CI/CD, run the checks, and get the thing to production safely.
05
Maintenance
Refactor, simplify, and tune things so the system stays healthy as the product grows.