Programming
C and C++ are part of my toolkit; Rust is a language I follow and enjoy exploring without presenting myself as a specialist.
Technology / Experimentation
Technology
Tools exist to solve problems.
I see technology as the ability to solve problems in simpler, faster, more accessible and more precise ways. First a tool has to work; then I want to understand how it works and what can still be tuned.
01 / GNU/Linux
It became home before it became a philosophy.
My contact with GNU/Linux began around 2000. What won me over at the time was practical: a distribution already included a huge collection of useful tools, without the hunt for media, keys and copied software that came with other systems.
It was also an environment that challenged me to learn and allowed real customization. Today the relationship is simpler: I am used to it, comfortable in it and find everything I need there.
02 / Method
Solve, understand, tune.
My sequence is usually direct: first I check whether a tool solves the problem. If it does, I want to understand the mechanism and find where I can simplify, adapt or improve it.
If an existing solution only covers part of what I need and I am able to build something else, I often end up making my own. I prefer small tools, clear documentation and systems that can be understood from end to end.
03 / Test bench
Software meets the physical world.
Electronics
Components, sensors, microcontrollers and small circuits enter as a technical hobby and a constant learning space.
Automation
It becomes valuable when it removes repetitive work, gathers better data or makes it possible to monitor something that once required constant presence.
Open source
I like being able to read, study and modify code when needed. It is a preference for use and technical freedom, not a demand on how other people should work.
04 / Projects
I usually start because I was missing something.
My personal projects rarely begin with the desire to “have a project”. They appear when a tool does not exist, does not fit what I need, or when I want to be genuinely involved in building the solution.
I enjoy the process more than the showcase: study, test, document, correct and come back later to properly rebuild what started as a good temporary fix.