About me
Early development basics, a long detour through infrastructure, and a deliberate return to code
My journey
Development did not arrive by chance in my career. I already had the basics before starting work: algorithms, databases, a bit of web. Nothing professional at the time, but enough to know I enjoyed the subject.
Then I joined DigiBOX and infrastructure took over. System technician, support at Redvise, a BTS SIO degree (SISR option), then two years as a systems and network administrator at ITIC, earning the CCNA and MTCNA along the way. Five years in the field that taught me how to diagnose a failure without going in every direction.
The CDA and AIS double bachelor's degree was the moment to take development seriously again, this time in depth. Since the fundamentals were already there, I could move quickly to what really matters: architecture, code quality and testing. I went on to a full stack Master's degree, and today I build business applications on a work-study programme at the Valophis group.
This detour through infrastructure remains my greatest asset as a developer. When I write code, I know where it will run. I think about file permissions, open ports, and what happens to an environment variable in production. It avoids a lot of bad surprises at deployment time.
Understand before coding
Before opening the editor, I take the time to pin down the real need, list the edge cases and compare existing solutions. A clear design from the start avoids redoing everything three weeks later.
Security from day one
On my projects I handle passwords, tokens and access rights from the very first lines. Catching up afterwards always costs more than planning for it.
Revisit and go deeper
Coming back to a concept I have already met lets me go further the second time. Microservices on RestoBook, containerisation on Butterfly, the markdown editor on this site. I then write down what I learned.
Outside class and the office
I tinker with a homelab to test configurations I cannot try in production, I write scripts to automate what bores me, and I write articles about the topics I have just explored. Explaining a concept is still the best way to check that you have understood it.
Shall we talk?
A question about an article, an opportunity or simply the urge to talk tech. That is what the form is for.
Contact me