About
A “bonus” page to give some context about my background and how I work.
I work in a direct and incremental way.
Everything starts with a first conversation to understand the real need, the context, and to confirm the project makes sense for both sides.
I do not start from a pre-made theme or an imposed platform. The starting point is always your activity, your content, and the expected usage — not a template to fill.
You talk directly with the person who designs and builds the project, from start to finish.
Once the quote is approved, we work together on the structure of the website or application.
This can be done via async messages, calls, or video sessions with screen sharing to draft simple wireframes and validate the structure of pages or features.
Existing references are welcome: websites, specific elements, features, visual references. They are a discussion baseline, not a copy target.
Development starts next. Depending on the project, I can move independently or ask for frequent feedback to stay aligned with your activity and communication style.
Before delivery, everything is tested. A short period for minor adjustments is included after launch.
Timelines depend on scope and on how fast we can iterate together.
As an indication, a simple brochure website can be delivered in 5 to 10 business days, spread across multiple weeks if needed.
The pace adapts to your schedule: some projects move quickly, others take more time to validate content or decisions.
Text copy and media preparation are ideally handled on the client side. When that is not possible, we plan it upfront to avoid timeline drift.
My goal is to deliver something functional, clear, and maintainable — without unnecessary rush.
I’m a web developer, 80% self-taught, with 10% formal training and 10% mentorship.
No degree.
No “traditional” professional experience (consulting firms, agencies, software vendors).
No internship or apprenticeship.
Just 4 to 5 years of real-world practice.
Fullstack Developer — Ruby / React
Out of 550 participants, only 13 obtained the certification.
Among those 13, some had already been coding for 3 to 5 years.
I was starting from scratch.
It wasn’t easy.
But I was clearly the most persistent in the group.
Never give up.
In the end, I had learned the basics, had a roadmap — but I knew I was still bad at it.
Fullstack Developer — Ruby / React
This period was dedicated to consistent, autonomous practice in web development.
The goal was simple: code often, understand what I was doing, and improve through real projects.
On the frontend side, I worked on React interfaces: components, state and data rendering, user interactions, and API communication with the backend.
I also made significant progress in UI / UX.
My early interfaces were messy; over time, I learned how to structure pages, clarify user flows, and avoid overengineering.
On the backend, I mainly worked with Ruby and PostgreSQL.
APIs, business logic, authentication, email delivery, data management, and code organization.
This phase helped me truly understand how a web project works end-to-end: frontend, backend, and database.
I also practiced algorithmic exercises.
Technically interesting, but with little real-world impact outside interview contexts.
At that point, I had a solid enough technical level to work on real projects.
But the market was tough: Ruby + React in Toulouse, and very few junior opportunities in 2023.
I realized I needed to learn a more in-demand backend language (Node, Java, or Python).
Java / Angular
I chose Java.
Simply because I found a motivated mentor to guide me — an engineer recently hired at Rolex.
The goal was straightforward:learn by building a complete, production-like project.
I had never worked with Java or Angular before.
So I first had to learn the fundamentals on my own before starting the project.
We built a match planning tool for Dota 2 teams.
Advanced security: OpenID, JWT, refresh tokens, http-only cookies.
Sortable tables, team management, match scheduling, time zone handling, and even some SSR and WebSockets.
Every line of code went through code reviews.
Until reaching a solid junior-level standard, ready for industry work.
Java / React
Today, it’s common for hundreds of developers to apply for a single job posting. For junior profiles, landing a first role at a consulting firm or software company has become extremely difficult.
Many degree holders struggle to find a position. For self-taught developers, market access is even more limited.
Freelancing became a realistic alternative: finding projects independently, working directly with end clients, and staying close to hands-on development.
This is not a “freelance dream”. It’s a pragmatic choice — to move forward, gain experience, and see where this path leads.
A simple inventory: tech, what I think about it, and my hands-on experience.
| Tech | Description | Experience |
|---|---|---|
| HTML / CSS | Strong focus on HTML semantics and component-scoped CSS, kept readable, maintainable, and easy to tweak over time. | 4 years |
| JavaScript | Used for application logic, user interactions, and API calls. Solid vanilla JS foundations, now mostly used through React and Angular. | 3 years |
| TypeScript | Used daily on Angular and Next.js projects to type data and make code safer, mostly with simple types and interfaces. | 2 years |
| React | Component-based UI development for websites and frontend apps. Comfortable with state management and UI logic, with attention to rendering and user experience. | 4 years |
| Next.js | Used to structure React projects with SSR and a performance / SEO-oriented approach. | 1 year |
| Redux | Good understanding of global state management principles, with past hands-on experience (less used recently). | 1 year |
| Angular | Used in a mentored project context: components, services, routing, and HTTP interceptors. | 1 year |
| NgRx | Redux-inspired state management used with Angular, understood and applied in real projects. | 1 year |
| Tech | Description | Experience |
|---|---|---|
| Java | Backend language mainly used through Spring Boot. Solid OOP foundations and collections handling, with a pragmatic production-oriented approach. | 2 years |
| Spring Boot | Framework used to build stable REST APIs with JPA, Spring Security, Maven dependency management, and a service-oriented architecture. | 2 years |
| PostgreSQL | Relational database used to store and query data, including migrations and table relationships. | 4 years |
| Ruby | First backend language I learned, used to understand OOP basics and write simple scripts and logic. | 2 years |
| Ruby on Rails | Backend framework used to quickly build APIs, handle authentication, databases, and CRUD operations. | 2 years |
| Tech | Description | Experience |
|---|---|---|
| CI / CD (VPS + Nginx) | Simple pipeline to auto-deploy a Spring Boot backend on a VPS on Git push, with Nginx serving the application. | 1 year |
| Netlify | Platform used to deploy frontend projects to production, manage domains/subdomains, and handle redirects. My go-to frontend hosting. | 4 years |
| AWS S3 | Used to host static files (images, media) when the volume isn’t suitable for a Git repository. | 2 years |
| Heroku | Used in early backend projects to deploy quickly, manage environment variables, and schedule automated tasks. | 2–3 years |
| Tech | Description | Experience |
|---|---|---|
| Git (GitHub / GitLab) | Used daily for version control. Comfortable with team workflows, conflict resolution, rebase, and squash. | 4 years |
| Postman | Used to test REST APIs, handle requests, headers, and auth tokens. | 4 years |
| DBeaver | Used to inspect and debug PostgreSQL databases, both locally and in production. | 2 years |
| Docker | Used to quickly run local services (especially databases) via Docker Desktop. Basic knowledge of the Docker ecosystem. | 1 year |
| Termius | SSH client used to access a VPS, manage server configuration, and monitor deployments. | 1 year |
| Figma | Used to create mockups, wireframes, and visual supports for web projects. | 2–3 years |
| IDE (VS Code / IntelliJ) | Daily development environments for frontend and backend work. | 4 years |
