About This Website
To get in touch easily, message me on twitter.
More about me
I grew up in the 80s, tech gadgets were still rare: no mobile phones, personal computers were still a bizarre concept and few people had actually gotten their hands on one.
Yet I was one of the happy few, thanks to the PC/AT my father brought home. The amazement, the feeling of power from learning a new language, one that could express processes and concepts in a way an inanimate objet could put them to life swept me away.
System programming, 68k assembly, networking, embedded systems, 3D graphics kept me up at night until I got an engineer's degree in computing.
I then took a job in IT architecture. That is, understanding, evaluating and designing large-scale infrastructures for banks and large retailers. It was thrilling to build processes and tools enabling diverse teams to communicate, tackling the operational challenges of ongoing business.
But curiosity never rests. I chose to put this life aside, sell my belongings and fulfill an old dream: go see the world, on foot. I spent 6 years on the road, working here and there, learning languages and customs.
And back I am, reconnecting with the joys of technology. Blockchain, Arduinos,
embedded µcontrollers everywhere, and
— isn't now the best time to create?
Why the website?
This website is my way to show my work and share the excitement of creating things, playing with technology and solving problems.
Along the way, I will insist on two ideas that matter to me:
Formal education lacks a sense of purpose. Often, I talk to young graduates, and realize teachers only hand them the tools, not how, why and when to use them.
- I want to showcase techniques I know from experience are not well understood by novices.
- I want to show them in actual projects, detailing the thought process behind.
Software is more than a patchwork of tools. It lives in an ecosystem. It builds upon one. And I believe in the value of seeing the whole picture.
- I want to encourage fellow developers to think beyond their code. In terms of people, relations and risks.
- I want to encourage fellow developers to see through abstractions and understand their design.