By about 2007 (age ~21) he was already the primary author/maintainer of will_paginate, a widely adopted Rails pagination library, and by ~2010 (age ~24) he created and began long-term maintenance of hub, the popular GitHub-oriented git CLI wrapper.
Mislav Marohnić is a Croatian software engineer who became a prominent open-source contributor in the Ruby/Rails community. He authored will_paginate (with early co-credit to PJ Hyett), later created hub, and worked as an engineer at GitHub while living as a remote/traveling developer from Zagreb and elsewhere.
From Croatia (Zagreb associations); family class and parental occupations not documented in reviewed sources.
Current position (2025)
Independent open-source engineer known for hub and will_paginate; formerly a GitHub engineer; continues open-source work and writing from a remote/traveling base.
Where the conditions came from
Three sources, read side by side
Each is placed on a −1 to 3 scale from documented evidence, and the three are never added together. A combined total would rank Mislav Marohnić 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
What they brought
+2Tailwind
-10+1+2+3
What capability, drive, or early skill is documented in the person rather than their surroundings?
Prolific open-source contributor from an early age; authored will_paginate by ~21 and hub by ~24, both widely adopted in the Ruby/Rails ecosystem. Self-taught with deep systems and front-end skills, working remotely from Croatia.
Where it was dropped
What they were handed
0Neither way
-10+1+2+3
What money, family standing, network, or permission was already in place before the work began?
Based in Zagreb, Croatia with no documented family wealth or domain connections. No evidence of inherited capital or professional networks; his advantages were self-created through open-source work.
The shape of the track
What surrounded them
+1Tailwind
-10+1+2+3
What place, timing, institution, or peer group made the next step available?
Rails open-source community and GitHub provided distribution and eventually employment, but he was remote from Croatia without frontier geography or elite institutional access. The Rails ecosystem was a modest but real platform for compounding.
A −1 is a documented headwind, not a missing value; a 0 means the sources record nothing notable either way. Annotation confidence: Low. 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
Perseverance and luck stay visible—not scored.
Documented perseveranceNot documented in the reviewed biographical summaries.
Silence in a biography is not evidence that perseverance was absent.
Structural luckCreated hub and began long-term maintenance of the GitHub-oriented git CLI wrapper.
This is an unchosen opening or condition in the record, not an estimate of how much luck caused the outcome.
Open the legacy 22-field research annotation
How this path compounded
01 Starting advantages
4/24 starting-position score
Strongest documented signals: Early online platform, Exceptional peer / cofounder, Direct domain exposure.
Describes the starting position, not what the person later made of it.
Measures what was present, not whether it was inherited, earned, self-built, external, or mixed.
Cohort percentile: 37
03 Compounding trajectory
4 documented steps
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.
Milestone at age 21
04 Observed career standing
T4 · Specialist-known
Notable, but primarily known within a niche. The tier summarizes documented career recognition through the data cutoff—not Mislav Marohnić's worth or future potential.
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.
Prior reps2/3
Advantage-enabledmedium confidence
One or more documented starting advantages plausibly enabled this lever.
Early online platform (2/2)
Scarce skill depth2/3
Advantage-enabledmedium confidence
One or more documented starting advantages plausibly enabled this lever.
Early online platform (2/2)
Native distribution2/3
Advantage-enabledmedium confidence
One or more documented starting advantages plausibly enabled this lever.
Early online platform (2/2)
Structural wave / timing2/3
Externalmedium confidence
A structural wave is external to the person, even when their position improved access to it.
Early online platform (2/2)
Complementary team1/2
Advantage-enabledmedium confidence
One or more documented starting advantages plausibly enabled this lever.
One or more documented starting advantages plausibly enabled this lever.
Direct domain exposure (1/2)
Elite ecosystem network1/3
Advantage-enabledmedium confidence
One or more documented starting advantages plausibly enabled this lever.
Exceptional peer / cofounder (1/2)
Concentration intensity1/3
Unresolvedlow confidence
No current annotation distinguishes self-built, enabled, or earned origins for this lever.
No decisive linked signal
This is a bounded inference from the current annotations—not a claim about private effort, merit, or the percentage of Mislav Marohnić's outcome attributable to any origin.
Luck is not a leftover score.
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.
Within Researchers / independent engineers, Mislav Marohnić's starting-advantage total is at the 9th percentile. Separately, their built or converted leverage total is at the 37th percentile. Other T4 profiles average 5.9 / 24 starting advantage and 10.4 / 25 leverage. Similar scores appear in other tiers, so these figures describe positioning—not a cause.
Trajectory
2007 · age 21
will_paginate was already in active Rails community use
His major pagination library contribution.
2010 · age 24
Created hub and began long-term maintenance of the GitHub-oriented git CLI wrapper.
2014 · age 28
Active in the Zagreb developer community
Building a remote open-source/GitHub career.
2020 · age 34
Published a retrospective on a decade of hub maintenance
GitHub's official gh CLI matured.
Primary leverage engine
Technical depth / open-source distribution
Scarce technical / intellectual depth
Secondary engine
Platform-native compounding (GitHub/Rails)
Built/converted leverage
12 / 25
evidence: Medium
Built or converted leverage
Multiplying capacity documented later in the path. Measures what was present, not whether it was inherited, earned, self-built, external, or mixed.
Started serious reps before 20
0/1
Prior reps
2/3
Scarce skill depth
2/3
Native distribution
2/3
Elite ecosystem network
1/3
Complementary team
1/2
Structural wave / timing
2/3
Concentration intensity
1/3
Capital safety
0/2
Domain proximity
1/2
Starting-advantage scores (0–2 each)
Access or conditions documented near the beginning of the path. Zero means "no clear evidence in reviewed sources," not "advantage was absent."
Family financial platform
0/2
Parent / family domain
0/2
Inherited audience / network
0/2
Elite institution pipeline
0/2
Frontier geography
0/2
Rare early tools
0/2
Dedicated mentor / coach
0/2
Exceptional peer / cofounder
1/2
Early online platform
2/2
Direct domain exposure
1/2
Prodigy / innate ability
0/2
Adversity / constraint catalyst
0/2
Family context
Not documented in reviewed sources. He is from Croatia (Zagreb area associations).
Parent / family domain
Not documented in reviewed sources.
Archetype & tags
Platform-native compoundingRails ecosystemGitHubwill_paginatehubopen sourceCroatia remote work
Evidence summary
Batch data and self-description as an '80s kid support a ~1986 birth year. By the mid/late 2000s he shipped will_paginate into the core Rails toolbox and then built hub, which he maintained for a decade-plus and which became a defining GitHub CLI tool before official gh. Early advantages were primarily platform-native: deep Rails/GitHub open-source distribution and collaboration (including with PJ Hyett), not documented family capital or elite institutions.