Welcome back to A Little Wiser. This edition features a guest piece from Ian Roth, the founder of Own The Watch. Ian is one of our favorite writers in the newsletter space. He publishes everything from honest watch reviews to data-backed takes on spending and saving that we’d highly recommend checking out. Today's wisdom explores:

  • The Civilization That Vanished Into the Jungle

  • Feature: A Brief History of Rolex

  • How We Almost Missed the Moon

Grab your coffee and let’s dive in.

HISTORY
🛕 The Civilization That Vanished Into the Jungle

In 802 AD, a Khmer king named Jayavarman II stood on a hill in what is now northern Cambodia and declared himself a god-king, founding what would become one of the most extraordinary civilizations the world has ever produced. The Khmer Empire that grew from that moment eventually controlled a territory stretching from the southern tip of Vietnam to the borders of modern Myanmar. At its heart it built a city that no other pre-industrial society on Earth came close to matching in scale. Angkor, which served as the imperial capital from roughly the ninth century to the fifteenth, covered an area of at least 1,000 square kilometers. It housed a population estimated by researchers from the University of Sydney at somewhere between 700,000 and one million people at its peak making it larger than medieval London, Paris, and Rome combined.

The temple complex of Angkor Wat, built over approximately three decades, remains the largest religious monument ever constructed. It covers an area of 400 acres and is aligned with such astronomical precision that on the spring equinox the sun rises directly over its central tower when viewed from the main entrance causeway. What made Angkor genuinely remarkable was the invisible infrastructure beneath and around the temples. The Khmer engineers built a hydraulic system of extraordinary sophistication with a network of reservoirs called barays. These were connected by canals, moats, and distribution channels that spread monsoon rainfall across hundreds of kilometers of agricultural land. LiDAR surveys conducted by archaeologist Damian Evans revealed the full extent of this system for the first time and produced results that stunned the archaeological community. The surveys showed an urban grid of residential neighborhoods, roads, ponds, and temples extending far beyond what anyone had previously mapped, connected by a hydraulic network that Evans described as comparable in engineering ambition to the Roman aqueduct system.

The decline of Angkor was a gradual process rather than a single event. Historical records and archaeological evidence indicate that political change, warfare, shifts in trade networks, and environmental pressures all played roles. Research has identified periods of severe drought interspersed with unusually intense monsoon rains during the fourteenth and fifteenth centuries, conditions that may have placed increasing strain on the city's water-management system. In 1431, forces from the Ayutthaya kingdom captured Angkor, but historians generally view this event as one factor among several in the broader transformation of the region. Although many of Angkor's structures became overgrown by vegetation after the city's decline, the monuments were never entirely forgotten by local populations. Modern archaeology has demonstrated that Angkor was the product of Khmer society and one of the most extensive and technologically sophisticated urban and hydraulic systems of the preindustrial world.

An illustrated map of the water around Angkor

FEATURE
A Brief History of Rolex: How One Waterproof Case Changed Everything

Rolex was founded in London in 1905 by Hans Wilsdorf, a German entrepreneur who believed wristwatches could be accurate, reliable, and respectable at a time when most serious watchmakers still considered the pocket watch the only credible timekeeping instrument. Wilsdorf did not invent the wristwatch. He made the argument, through engineering and marketing in equal measure, that it deserved to be taken seriously.

That argument became concrete in 1926 when Rolex introduced the Oyster, the world's first waterproof wristwatch case. The screw-down crown, screw-down caseback, and sealed crystal protected the movement from dust, moisture, and humidity. Rolex showed the world the Oyster's capability in 1927 when Mercedes Gleitze swam the English Channel wearing one. The watch survived. The story ran in newspapers across Europe. The watch still worked.

From the Oyster, everything else followed. The Perpetual self-winding movement arrived in 1931, solving the problem of keeping an automatic watch wound (ticking) through natural wrist movement. The combination of a waterproof case and a self-winding movement produced a watch that required almost no intervention from its owner and would function in conditions that destroyed conventional wristwatches. That combination became the foundation on which every significant Rolex reference was built.

The tool watch era defined Rolex's identity through the 1950s. The Submariner launched in 1953 as a purpose-built dive watch for professional divers. The Explorer launched the same year, developed alongside the expedition that first summited Everest. The GMT-Master arrived in 1955, built in partnership with Pan American World Airways for pilots tracking two time zones on long-haul international routes. Each reference solved a specific professional problem for people who needed the watch to work where others would fail.

The Datejust and Day-Date ran parallel to the sport references, establishing Rolex as equally credible in a boardroom as on a mountain. The engineering credibility came first. The prestige followed from it.

ASTRONOMY
🚀 How We Almost Missed the Moon

The Saturn V that lifted Neil Armstrong, Buzz Aldrin, and Michael Collins toward the Moon was one of the most complex machines ever built. It contained well over a million individual parts and had come close to being grounded before Apollo 11 ever launched. During the unmanned test flight of Apollo 6 in April 1968, two of the five second-stage engines shut down prematurely with the mission continuing on a timeline that left several senior engineers genuinely uncomfortable. The Apollo 1 fire in January 1967, which killed astronauts Gus Grissom, Ed White, and Roger Chaffee on the launch pad during a routine ground test was another fatal setback. It forced a complete redesign of the command module and an eighteen-month delay that consumed political capital and public confidence in equal measure.

The closest the landing itself came to failing happened in the final twelve minutes of the descent. At around 30,000 feet above the lunar surface, the guidance computer in the lunar module Eagle began displaying an alarm code that neither Armstrong nor Aldrin had encountered in training. The code was 1202, an executive overflow, meaning the computer was being asked to process more tasks than it could handle and was automatically shedding lower-priority functions to keep the critical guidance calculations running. In the back rooms of Mission Control, a 24-year-old software specialist named Jack Garman had prepared a handwritten reference sheet of alarm codes and their implications. Flight controller Steve Bales turned to Garman, received an answer within seconds, and called go. The alarm appeared five more times on the way to the surface and each time Garman confirmed the landing could continue.

What happened next came down to Armstrong alone. With the computer alarms still flickering, he looked through the window and saw that the designated landing site was covered in boulders, took manual control of the spacecraft, and flew it horizontally across the lunar surface searching for clear ground while the fuel gauge dropped toward empty. Eagle touched down at Tranquility Base with somewhere between 15 and 30 seconds of powered flight remaining. The margin was so thin that flight controllers in Houston did not fully process what it meant until after the dust had settled. The most audacious journey in human history had survived engine failures, a catastrophic fire, a software crisis nobody had prepared for, and a last-second navigation decision made by one man at low altitude with almost no fuel.

A genuine thank you to Ian for fitting one of watchmaking's great stories into our short paragraph format — no small ask for a topic he could write about for months, and frequently does. The full archive is at ownthewatch.com and worth losing an afternoon to.

We hope you enjoyed today’s edition! If you did, feel free to share it on social media or forward this email to friends.

Until next time... A Little Wiser Team

Keep Reading