22 October 2026 · Journal

From component to patrimony.

In 2010, I mainly wanted to avoid solving the same problem twice. Today I understand that this intuition never really disappeared. It only changed scale.

At first, reuse was personal.

Functions, then modules, then primitives. It was a way to capitalize my own work as a developer.

Architecture changed the object.

With software architecture, technical architecture, solution architecture and BPM, what I wanted to reuse became broader: patterns, systems, models, processes, decisions and then capabilities.

The question is no longer only: how do I avoid recoding? It becomes: how do I avoid rediscovering?

Today.

I see Priostack as a way to explore this question at enterprise scale. Qubit remains fundamental technological patrimony. Priostack is a broader expression of it. And my family reminds me that patrimony is never only technical.

This formulation is dated. It may change. The journal exists to keep that change visible.