Services

1

Frontend

For me, a good interface is one users don't have to think about. I care about how every screen looks and feels: clear layouts, smooth interactions, and flows with as few steps as possible. Under the hood, nothing is hardcoded unless it has to be. Content, colors, spacing and themes come from data and design tokens, so the whole UI can change from one place. Components work like plugs: add one where it's needed or remove it, and the rest of the page keeps working.

2

Backend

I build backends as a set of plugins. Each domain (auth, users, files, mail, jobs) is its own NestJS module with one responsibility and a clear boundary, built on OOP principles and dependency injection. Plug a module in when the system needs it, unplug it when it doesn't, and the rest keeps running. That independence also makes each module ready to become its own microservice. Behavior comes from configuration instead of hardcoded values, and everything is exposed through versioned, Swagger-documented REST APIs.

3

Database

The same principles apply to data. I split the domain into small, focused tables, each representing one concept and linked by explicit relations. Anything that might change, such as categories, types or settings, is stored as data instead of written into the code, so the system can adapt without a redeploy. I design the schema from the real workflow: the entities, the states they move through, and who can change them. I use Prisma with PostgreSQL for relational data, or MongoDB when the shape really varies.

Libraries & Frameworks I Usually Use

A curated stack I use day-to-day for building reliable, scalable web apps.