Fedi Dayeg, full-stack developer in France

I start by understanding the constraint that actually matters: the deadline, the legacy system nobody wants to touch, the traffic peak that breaks things. Architecture decisions follow from that, not from a preference for a particular framework.

In practice, that means I write code that the next developer can read, I keep the data model honest, and I make the failure modes visible instead of hiding them behind a catch block. Most of the value I add on a long project comes from the second half — when the code has to keep changing without breaking.

Next.js and React with TypeScript are my default stack, and I have shipped production interfaces in Angular and Vue.js as well. I care about the parts users feel: how fast the first screen paints, whether the interface responds while data loads, and whether it works with a keyboard and a screen reader.

NestJS and Spring Boot for services, MongoDB and MySQL for storage, REST and GraphQL depending on what the clients of the API actually need. I use message queues such as RabbitMQ when a workload should be decoupled rather than made synchronous and fragile.

I containerise with Docker, deploy on Kubernetes, and automate releases with GitHub Actions so shipping is boring and repeatable. Sentry and Datadog go in early, because an error you never see is an error you never fix.

A fast site and a findable site are the same engineering problem seen from two angles: real server rendering, restrained payloads, clean semantic markup, and structured data. I treat Core Web Vitals as a build constraint rather than a post-launch clean-up task.