Architecture
- Clear responsibilities, no mixing layers just because.
- Low coupling between modules, services, and components.
- Manageable changes without rewriting half the system.
Full-stack with Next.js and TypeScript. I design architecture, product and interfaces with a focus on clarity, performance, and real maintainability.
Restrained systems. Considered decisions.
From the first model to a stable deployment.

Quietly steady


Quietly steady
Clarity to build better.
I'm a full-stack developer with a way of working built on judgment, structure, and continuous improvement. I'm drawn to building systems that are understandable on the inside and pleasant on the outside: clean architectures, coherent data models, and interfaces that walk alongside the user.
I see development as a craft: listening, ordering, deciding, shipping, iterating. Without dramatizing the process. Without adding unnecessary complexity.
My design system for web applications.
Real trade-offs, not theory.
Some recent projects.

B2B platform for pharmacies: training, updates, analytics.
Context: A single place to educate, launch, and support pharmacy partners.
Constraints: B2B clarity, fast content updates, reliable delivery.
Role: End-to-end ownership: build, ship, iterate.
What I did

Design system and component library focused on consistency and accessibility.
Context: Shared UI base across multiple ISDIN products.
Constraints: Pixel-accurate UI, a11y, performance, smooth DX.
Role: UI components, architecture, and integration support.
What I did

Web3 funding for artists with ERC-20 tokens and perks.
Context: Direct fan-to-artist funding with on-chain ownership.
Constraints: Low-friction UX, wallet auth, reliable contract reads.
Role: Frontend, Web3 auth, contract integration.
What I did

B2B self-service portal for lines, subscriptions, and usage insights.
Context: Customers needed control without dependence on support.
Constraints: Dense data, predictable UX, maintainable UI at scale.
Role: Frontend delivery, shared libraries, platform stability.
What I did
The tools I work with.
Notes on code and product.
A practical pattern to revalidate pages while keeping the editorial flow intact.
Constraints and ownership rules as part of the product — not an afterthought.
Scale workloads by separating cheap orchestration from heavy compute workers.
Drop me a line.