Documented path
Born/raised Leuven, Belgium (~1971). Learned BASIC from TV then Commodore 64/Amiga assembler; entered Linux via Amiga 4000. By 23 (1994) deeply involved in m68k port and student networking (Kotnet at KU Leuven); later PhD in wavelets (defended 1999) while remaining a long-term kernel maintainer; day job embedded systems (e.g., Sony SDCE).
Born and raised in Leuven, Belgium; self-taught programmer via Belgian TV BASIC, Commodore 64, then Amiga systems that led into Linux.
Long-time Linux kernel contributor/maintainer (m68k and related areas); embedded Linux technologist (Glider / industry roles); active for 30+ years in the kernel community.
Where the conditions came from
Each is placed on a −1 to 3 scale from documented evidence, and the three are never added together. A combined total would rank Geert Uytterhoeven against other people. Held apart, they explain why this path ran differently from another one—which is the only comparison this project supports.
The marble itself
+2Tailwind
What capability, drive, or early skill is documented in the person rather than their surroundings?
Learned BASIC from a Belgian TV show, then Commodore 64/Amiga assembler. Deeply involved in Linux/m68k kernel hacking by age 23 (1994), meeting Linus Torvalds that year. Self-taught programmer with ~10 years of experience by his early 20s. Exceptional early domain immersion.
Where it was dropped
0Neither way
What money, family standing, network, or permission was already in place before the work began?
No family background documented. Raised in Leuven, Belgium. Belgian public education system. No wealth or domain-specific family connections evident.
The shape of the track
+2Tailwind
What place, timing, institution, or peer group made the next step available?
KU Leuven provided university access. The Linux/m68k port (first non-Intel Linux port) and meeting Torvalds at a Belgian conference provided a rare frontier position in open-source kernel development. Early home computer access (C64, Amiga) was catalytic for building scarce architecture expertise.
A −1 is a documented headwind, not a missing value; a 0 means the sources record nothing notable either way. Annotation confidence: Medium. These are analyst readings of what the sources record, not measurements of merit, talent, or effort. The twenty-two scored dimensions remain available inside the deeper research detail.
What moved through the conditions
This records repeated behaviour or recovery described by sources; it is not a grit or merit score.
This is an unchosen opening or condition in the record, not an estimate of how much luck caused the outcome.
Strongest documented signals: Early online platform, Elite institution pipeline, Rare early tools.
Describes the starting position, not what the person later made of it.
Strongest observed levers: Domain proximity, Started serious reps before 20, Prior reps.
Measures what was present, not whether it was inherited, earned, self-built, external, or mixed.
The timeline below shows the sequence of work and transitions around the selected early milestone. It is evidence of a path, not proof that every step was necessary.
Notable and widely recognized within the domain. The tier summarizes documented career recognition through the data cutoff—not Geert Uytterhoeven's worth or future potential.
Question four · where did the leverage come from?
Each non-zero lever gets a best-supported origin, evidence signals, and confidence. Unresolved is the honest default when the biography cannot distinguish self-built, advantage-enabled, earned, external, or mixed.
Mapped starting advantages and self-directed-building language are both documented.
One or more documented starting advantages plausibly enabled this lever.
Mapped starting advantages and self-directed-building language are both documented.
Mapped starting advantages and self-directed-building language are both documented.
One or more documented starting advantages plausibly enabled this lever.
A structural wave is external to the person, even when their position improved access to it.
The biography uses self-directed-building language, but the origin was not independently annotated.
One or more documented starting advantages plausibly enabled this lever.
Mapped starting advantages and self-directed-building language are both documented.
This is a bounded inference from the current annotations—not a claim about private effort, merit, or the percentage of Geert Uytterhoeven's outcome attributable to any origin.
Structural luck, Encounter luck, Event luck, Outcome variance can change every arrow in the path. This successful-only dataset cannot observe the near-identical paths that did not break through, so luck stays visible and unscored.
Multiplying capacity documented later in the path. Measures what was present, not whether it was inherited, earned, self-built, external, or mixed.
Access or conditions documented near the beginning of the path. Zero means "no clear evidence in reviewed sources," not "advantage was absent."
Born, raised, and based in Leuven, Belgium; used parents’ car to pick up Torvalds in 1994—family supportive but not a tech dynasty in reviewed sources.
Not documented as kernel/software professionals.
Linux.com profile (2001) states he was 23 in 1994 and already a multi-year programmer deeply in Linux/m68k, meeting Torvalds that year—corroborated by LinkedIn linux-m68k.org activity from Mar 1994. Early home computers plus open-source email culture created scarce architecture skill on the first non-x86 Linux port. Career sustained as long-term maintainer and embedded engineer rather than celebrity founder (tier-3 specialist).
advantage confidence: Medium · source count: 3 · audit: partial_source_verification · status: subagent_researched_beta