Have you ever wondered what makes someone want to become a web developer?
For me, it's the pleasure of turning an idea into a concrete project through code.
Main technologies
The stack I use daily
Front-end
HTML5

JavaScript

TypeScript

CSS

Tailwind

Database
MySQL

SQLite

Oracle

Back-end
PHP 7.4 - 8.5

Versioning
GitHub

Design
Figma

Other stacks & tools
Technologies I've used in projects
Symfony

Laravel

Yii

NodeJS

BunJS

React

Electron

NextJS

ThreeJS

Python

Django

C#

Skript

Godot

Microsoft Graph API

Laserfiche

ChatGPT

Bubble Plan

Trello

Notion

How I work
Business applications & users
I like working on internal applications and business tools. These projects require understanding how users work every day. Before thinking about the technical solution, I first try to identify habits, constraints, and steps that can be simplified.
Being close to users helps build features that really fit their needs, instead of starting from assumptions. That is also what I enjoy in this kind of project: a sometimes simple improvement can save time, make information easier to access, or improve daily comfort.
Continuous learning
The development world moves quickly, so I take time to stay up to date by following changes in tools, practices, and technologies almost every day.
I complete that monitoring with personal projects, small or more ambitious. They let me test an idea, discover a tool I know less, or experiment with another way of doing things. Even when a project does not reach a final version, it remains useful if it taught me something I can reuse later in another context.
This way of learning also helps me regularly step outside my habits and gradually broaden the way I approach technical problems.
User experience
User experience is not only about how an interface looks. It mainly depends on how easy it is to understand and use every day.
I put a lot of importance on discussions with users, mockups, and feedback during development. I try to design clear interfaces that are easy to understand and adapted to their context of use.
I also pay attention to accessibility and performance, especially page weight and loading times. An interface that is pleasant to use should stay that way even on a low-bandwidth internet connection. My Opquast certification gave me a broader frame for these subjects and web quality in general.
Professionalism
Readable, structured, and documented code remains easier to understand and maintain over time. Reliability, security, and privacy are also considered from the design stage.
Beyond code, I keep a broader view of the project: priorities, deadlines, constraints, and the value being delivered. When something unexpected or urgent happens, I can reorganize my work, review my priorities, and adapt the solution without losing sight of the original goal.
A project also depends on clear communication, owned decisions, and enough follow-up to know where the project stands and what still needs to be done.
