Build for people
Technology exists to solve real problems.
About
Engineering with purpose.
I build software because it is the most direct way I know to turn a messy, real problem into something people can actually use. Most of my work starts the same way: understanding how a business or a person really operates, then finding the smallest system that makes that work better.
I work across the whole stack — interfaces, APIs, business logic, databases and the infrastructure that carries them. I care about how a schema is modelled as much as how a button feels, because both decide whether a product still makes sense a year later.
Outside of feature work, I spend time on the parts that quietly matter: authentication and permissions, offline behaviour, performance on modest devices, and a codebase the next engineer can read without a tour.
- Software engineering
- Full-stack development
- Product development
- System architecture
- UI / UX
- Backend systems
- Databases
- APIs
- Performance
- Developer experience
- Business problems
Yasin Husen
Software Engineer · Full-Stack Developer
Philosophy
How I think about building software.
Four principles that shape the decisions behind every project.
Keep it simple
Good engineering reduces unnecessary complexity.
Think in systems
Frontend, backend, database, infrastructure, and users are connected.
Ship and improve
Build, measure, learn, iterate.
How I build
One system, five architectural tiers.
A product is only as good as the weakest layer beneath it. Click any tier to inspect the design rationale.
01
Frontend
Interfaces, state, accessibility, performance
- React
- Next.js
- TypeScript
- Tailwind CSS
- shadcn/ui
02
API / Backend
REST endpoints, validation, authentication
- Node.js
- Express
- Spring Boot
- REST
- JWT
03
Business Logic
Domain rules, permissions, workflows
- Service layers
- RBAC
- Zod
- Testing
04
Database
Modelling, queries, migrations, integrity
- PostgreSQL
- MySQL
- MongoDB
- Supabase
05
Infrastructure
Delivery, environments, observability
- Docker
- Git
- Vercel
- Netlify
- Firebase
Skills
The toolkit, grouped by what it's for.
Not a checklist — these are the areas I work in regularly and can reason about under pressure.
Frontend
Interfaces that stay fast, accessible and maintainable as they grow.
- React
- Next.js
- TypeScript
- JavaScript
- HTML
- CSS
- Tailwind CSS
- shadcn/ui
Backend
APIs and services designed around clear contracts and predictable behaviour.
- Node.js
- Express.js
- Spring Boot
- Python
- REST APIs
Databases
Schemas modelled for integrity first, then for query performance.
- PostgreSQL
- MySQL
- MariaDB
- MongoDB
- Supabase
Cloud & Tools
The delivery pipeline from local environment to production.
- Firebase
- Supabase
- Docker
- Git
- GitHub
- Vercel
- Netlify
Engineering
The decisions that determine whether a system survives its second year.
- System Design
- API Design
- Authentication
- RBAC
- Database Design
- PWA
- Offline-first Architecture
Services
Ways I can help.
From a single interface to a complete product system, delivered end to end.
Full-Stack Development
End-to-end web application development.
SaaS Development
Building scalable SaaS products from concept to production.
Frontend Engineering
Modern, responsive, accessible interfaces.
Backend Development
Secure APIs, business logic, authentication, and integrations.
System Architecture
Designing maintainable and scalable application architectures.
Business Software
ERP, management systems, dashboards, and internal tools.
Have an idea? Let's build it.
Whether you're building a product, solving a business problem, or looking for an engineer to bring an idea to life, I'd love to hear about it.
Start a conversation