Mark Zuckerberg

If his name comes up in a clip about building things that get big, it is usually because of the same idea: he treated scale as something you design for from the start, not something that happens to you if the product works. That framing — scale as an engineering and organisational problem rather than a reward — sits underneath most of what he is quoted on.

Born in White Plains, New York, in 1984, he came up as a programmer before he was an entrepreneur, and his early projects were mainly exercises in turning what was technically possible into something that actually ran day to day. The working method was unremarkable in isolation and effective in accumulation: small improvements, repeated, with a fairly high tolerance for risk along the way. Mentors, partners and opponents all pushed back, and that pressure did as much to shape his judgement as any single success.

The mid part of his career was about converting prototypes into platforms and building the teams that could do it. Decisions on architecture, company culture and where to put capital are the ones people still pick apart. Failures were logged as experiments with something to learn from rather than buried, and his memos, interviews and keynotes ended up doing double duty as an explanation of how he worked. Regulatory and ethical questions were folded in as design constraints rather than handled separately.

Later on the emphasis shifted towards mentorship and building institutions that could outlast any one product. His name now functions as shorthand for social platforms and scaled networks, and the record he left — talks, emails, design notes — shows a fairly methodical process behind what can look like instinct. What carried forward was less the products than the habits and the organisations built around them.