Trajectory
Three trajectories. One path.
My personal trajectory is tied to my professional trajectory, which is itself tied to my technological trajectory. Separating them would lose the meaning of the path.
Synchronized reading
The person, the profession, the technology.
Each period can be read in three directions: who I was becoming, what I was learning to see, and what I was building.
Intern, then developer
I had just taught myself web development. I built first to learn and become more autonomous.
Code as a craft
Integration, XML, Java, PHP, early internal systems and automation.
Functions, data, synchronization
The first primitives were very concrete tools for avoiding the same work twice.
Master's degree in software architecture
I start looking at systems above the feature level.
From developer to architect
The question becomes as much about structure as implementation.
Rainbow-PHP
A public repository of reusable primitives for faster POCs and technical assembly.
Changing the level of abstraction
I no longer only want to build faster. I want to understand how systems carry behavior.
Technical and solution architecture
Integrations, middleware, processes, platform choices and the link between business need and system.
Replication, BDI, IFML, BPMN
State, intents, models and flows appear in public code long before their current convergence.
A less visible period
I publish little. The work becomes deeper and more solitary.
BPM expertise
Processes, decisions and models become a meeting point between business, architecture and execution.
Going beneath notations
Qubit takes shape during a period when much of the code and experimentation is not public.
Writing again
I put more words around questions long explored through code.
From architecture to the enterprise
Capabilities, patrimony and governance become as important as the technical stack.
Qubit, Geometric Memory, Priostack
Older threads converge into a more coherent search around meaning, trajectory and execution.
Rising abstraction
The level of the problem changed with me.
Why Flow of Meaning
I spent my career moving upstream through the flow.
At first I saw the result and the code. Then systems, processes, capabilities and finally intentions. Qubit and Priostack now try to make the journey in the other direction without losing meaning along the way.