The Architect Who Never Laid a Brick...

…and How AI Made Him a Mason

My psychological profile is INTJ¹, also known as the Architect, and I spent a good part of my life proving that this label fit… in the worst possible way.

Years of having a multitude of ideas

• on analysis systems (Blockchain, Productivity)
• on personal development methods (Memory, Discipline, Learning)
• on algorithms (routing, metacompression, encryption)
• on tools (format conversion, project management, system administration)

Years of producing hundreds of ideas in a row, for nothing, or worse, only to see some of them realized by others years later.

In retrospect, I believe this is one of the most underestimated effects of AI: it does not only serve to produce faster. For certain profiles, it serves above all to bridge the gap between idea and action.

The Forgotten Link

Like many, I had forgotten the link that must exist between idea and action.

Today, the Silicon Valley mantra is “Execution beats ideas”, but Seneca already said, nearly 2000 years ago: “Philosophy is not a matter of words, but of facts.”²

Because an idea without any action has no value. An idea without any action is in fact indistinguishable from the absence of an idea.

I had forgotten the value of action, at a time when the value of ideas is glorified.

For if action must come first for an idea to materialize, for that action to be effective, the underlying idea must be as well.

Action comes first, but it is not enough. I paradoxically spent a great deal of energy coding tools that solved a problem only I had.

The question of whether those tools were actually relevant would undoubtedly have deserved more attention.

No, action does not do everything.

For me, effective action is inspired action: action that efficiently serves a meaningful goal.

The 2 Archetypes

Most of us oscillate between two archetypes:

• The Architect (the thinker)
• The Mason (the doer)

Neither is superior to the other. It is not a hierarchy, but a dynamic: one conceives, the other builds. Without a plan, bricks pile up at random. Without bricks, the plan remains fiction.

You find Architects among laborers and Masons among CEOs. It is not a question of profession, but rather a preferred mode of operating. Two archetypes that are neither mutually exclusive, nor immutable over time. Just two ends of an axis.

On this axis, we oscillate between two risks: the inertia of pure thought and the agitation of directionless action.

We can in turn embody

• The Architect
  • One who has a vision, a sense of elegance and structure.
  • But who can find himself paralyzed in a form of intellectual procrastination.
  • He then produces brilliant algorithms that never leave the whiteboard, or systems so complex they are never implemented. It is intelligence spinning in neutral, a paper cathedral that will never house anyone.
• The Mason
  • Full of energy, he excels at execution and immediate materialization.
  • But he can sometimes lose the sense of the why and sink into agitation.
  • He then produces lines of code in succession, robust but useless tools, or features nobody asked for. It is the Sisyphus syndrome: a great deal of sweat for a result with no impact.

The problem is therefore not being an Architect or a Mason. The problem is staying stuck at a single end of the axis.

And what if AI allowed us to recreate this forgotten link: uniting action and reflection in inspired action?

AI for the Architect

For an Architect, AI is a delicious trap: a tool for manipulating ideas, creating new ones, and discussing them endlessly. It is exactly what he is looking for, and that is the danger.

Badly used, AI becomes an echo and amplification chamber: it helps refine an idea that perhaps did not need refining. It produces plans, variants, frameworks, systems, architectures. In short: it allows the Architect to procrastinate with industrial elegance.

But well used, it does exactly the opposite: vague ideas or those disconnected from context collapse under the first questions. Solid ideas, on the other hand, sharpen, refine, and take on an increasingly effective final form. Each interaction refines and materializes the idea a little more, making it increasingly concrete in the code and documents produced.

Be careful, however: AI amplifies what you express, not necessarily the value of an idea. This is the trap of confirmation bias. A bad idea well articulated comes out of the exchange reinforced, not corrected.

For the Architect, the true power of AI is therefore not to think more, but to facilitate the materialization of ideas into action.

AI for the Mason

For the Mason, AI first looks like a blessing.

Everything goes faster. The report that used to take half a day is out in ten minutes. The API planned for two days appears in one hour. The translation, the benchmark, the script, the email, the presentation: everything becomes doable, almost immediately.

It is exhilarating.

But producing faster does not mean producing better.

The Mason’s risk with AI is not laziness. It is assisted dispersion. He can now fill his days with deliverables, commits, documents, automations, and checked-off tasks, without ever asking whether any of it is truly building something.

AI does not correct the absence of direction. It accelerates it.

It can transform a poorly thought-out to-do list into a fatigue factory. It can give the impression of moving forward because many things are being produced, while nothing essential is progressing.

By laying bricks faster than his shadow, the Mason is no longer building a house: he is building a labyrinth.

Well used, however, AI can also become his counterweight.

It can challenge the why before the how. It can ask: “What goal does this task serve?”, “What measurable result do you expect?”, “What should absolutely not be done?”

For the Mason, the true power of AI is therefore not to produce more.

It is to produce less of what is useless.

AI as a Bridge

AI guarantees neither right thinking nor effective action.

Badly used, it amplifies our flaws: the Architect produces more sterile ideas, the Mason builds useless things faster.

Well used, it becomes a bridge: it helps the Architect to lay bricks, and the Mason to build works that have meaning.

It replaces neither direction nor effort.

It reduces the distance between the right idea and concrete action.

That is where inspired action is born: action that efficiently serves a meaningful goal.

Finally Laying the Right Bricks

At first, I mostly asked:

Is this idea good?

It was a bad question. It invited AI to validate, rephrase, embellish.

Today, I ask instead:

What is the flaw in this idea?

Then, if nothing disqualifying emerges:

How to start implementing it as efficiently as possible?

This simple change of question transforms AI: from a flattering mirror for the Architect, it becomes a filter, then a lever for the Mason.

This is how I now use it to produce more inspired actions:

• By delegating, supervising, and personalizing work I used to shy away from (frontend, marketing…)
• By helping me organize priority tasks independently of my biases and preferences
• By automating tasks for which I have formalized my best practices (skills)

AI has not made me less of an Architect.

It has above all forced me to become a little bit of a Mason: turning my plans into walls, my ideas into deliverables, my intuitions into proof.

For ten years, metacompression remained an elegant idea in my notes. In one weekend with AI, it became a prototype, an experiment, and above all measurable results.

And that is perhaps its true power: not to produce in our place, but to reduce the distance between what we understand and what we dare to build.

And you: does AI help you mostly to think better, to act better, or finally to connect the two?

Translated from French by AI