Learn the words, then come build them

Builder

Anyone who makes things work, with whatever it takes. Not a job title, an invitation.

No-code

Building software through visual tools instead of writing code by hand. Same outcome, fewer barriers.

Debated: Some argue it does not scale to complex systems and can lock you into one platform. Others see it as how most software will be built. The truth is usually: it depends on the job.

Low-code

Mostly visual building, with a little custom code where it helps. The pragmatic middle.

Debated: Critics ask where visual building ends and real engineering begins, and warn about hidden complexity. Supporters value the speed. Both can be right on the same project.

Vibe coding

Building by describing what you want to an AI and steering as it goes. New, fast, still needs a human in the loop.

Debated: A genuinely contested term: critics point to quality, security and maintainability of code you did not fully read. Advocates point to the speed of getting to a working draft. Worth understanding before relying on it.

Agents

Software that can take steps on your behalf toward a goal, not just answer once. Useful, and worth understanding before you trust them.

Debated: Debated because autonomy raises real questions: reliability, what they are allowed to do, and who is accountable when they act. Promising, not magic.

Generative AI

Software that produces new text, code, images or audio from a prompt. The engine behind much of today's building.

Debated: Among the most contested topics: accuracy and made-up answers, copyright and training data, energy use, and the effect on jobs. Powerful, and not settled.

Sovereign stack

The idea of a European layer of digital tools, infrastructure and standards you can actually build on, instead of depending on a handful of foreign platforms.

Debated: Debated: some warn it can slide into digital protectionism or fragmentation, others see it as basic resilience. The line between independence and isolation is the whole conversation.

Digital sovereignty

Keeping real control over your data, tools and choices, instead of renting them from somewhere you can't reach. The result we're after.

Debated: Contested in practice: full independence is rarely realistic, and the term is used to mean very different things. Useful as a direction, slippery as a slogan.

Resilience

Being able to keep running when something breaks or changes. The practice that makes sovereignty possible, not a synonym for it.

Open source

Software whose code is open to read, run and adapt. Transparent by design, harder to lock you in.

Debated: Debated mostly on sustainability: who pays the maintainers, and what "open" really means when a company controls the project. Open by design still needs a viable model.

Self-hosting

Running a tool on infrastructure you control, rather than on someone else's terms. One concrete way to take sovereignty back.

Debated: The trade-off is real: more control, but also the maintenance, security and uptime become yours. Freedom with a bill attached.

Lock-in

When leaving a tool costs so much you effectively can't. The thing sovereignty is meant to avoid.

Data residency

Where your data physically lives, and which laws apply to it. Often the first sovereignty question worth asking.