A universal language for global trade

This article by Ryan Petersen is a good history lesson on how shipping containers came to be. Here is an excerpt:

The idea for containerization came from a trucker, not a shipper. Malcolm McLean started out hauling empty tobacco barrels with his family in North Carolina in 1935. At that time, entire trucks would drive onto ships, wasting both a ton of potential cargo space, plus a chassis that could be on the road moving goods. McLean developed plans to use the so-called trailerships for travel from North Carolina to New York, but U.S. regulations didn’t allow one person to own both a trucking and a shipping company at the same time. So McLean did what any innovation-minded entrepreneur would do: He dumped the trucking company, took out a $22 million loan, and, in January 1956, bought two World War II T-2 tankers.

The magic of shipping containers is that they created a standard. Now all of a sudden you had standardized boxes that were intermodal. They could fit on ships, rail, and trucks. Ryan refers to containers as the "unsung hero of logistics."

He also likens them to the HTTP standard that helped give us the internet that we know today. Before HTTP, computers could only communicate with each other if they were on the same local network. Now we are, of course, connected globally.

But while containers standardized a part of our physical infrastructure, there's a lot that remains fragmented and manual:

The same way data passes between devices via the internet, goods pass between ocean ports, airports, warehouses, and other entities to reach their final destination. Without a logistics standard to act as a request-response protocol, all the players — suppliers, drayage, ports, warehouses, buyers — have to stitch their networks together manually.

Information gets lost; layers of redundancy, designed as backups given low visibility, slow the exchange: connections end up being very brittle. Let’s say there’s a shipment scheduled to arrive in Long Beach on Tuesday. But which terminal exactly and what pier number? What time is pickup? How long before late charges are incurred? Finding these answers is labor-intensive and imprecise. Logistics managers end up consulting different sources on websites, via email, or in person.

More from Brandon Donnelly

Cover image for Canada must become a global superpower

Brandon Donnelly

Mar 17

Canada must become a global superpower

The silver lining to the US starting a trade war with Canada and regularly threatening annexation is that it has forced this country out of complacency. Indeed, I'm hard pressed to remember a time, at least in my lifetime, when patriotism and nationalism has united so much of Canada. According to a recent survey by Angus Reid, the percentage of Canadians expressing a "deep emotional attachment" to the country jumped from 49% in December 2024 to 59% in February 2025. And as further evidence of...

Cover image for The bank robbery capital of the world

Brandon Donnelly

Dec 22

The bank robbery capital of the world

Between 1985 and 1995, Los Angeles' retail bank branches were robbed some 17,106 times. In 1992, which was the the city's worst year for robberies, the number was 2,641. This roughly translated into about one bank robbery every 45 minutes of each banking day. All of this, according to this CrimeReads piece by Peter Houlahan, gave Los Angeles the dubious title of "The Bank Robbery Capital of the World" during this time period. So what caused this? Well according to Peter it was facil...

Brandon Donnelly

Jun 26

The story behind those pixelated video game mosaics in Paris

If you've ever been to Paris, you've probably noticed the small pixelated art pieces that are scattered all around the city on buildings and various other hard surfaces. Or maybe you haven't seen or noticed them in Paris, but you've seen similarly pixelated mosaics in one of the other 79 cities around the world where they can be found. Or maybe you have no idea what I'm talking about right now. Huh? Here's an example from Bolivia (click here if you can't see...

Subscribe to Brandon Donnelly

>4.2K subscribers

This article by Ryan Petersen is a good history lesson on how shipping containers came to be. Here is an excerpt:

The idea for containerization came from a trucker, not a shipper. Malcolm McLean started out hauling empty tobacco barrels with his family in North Carolina in 1935. At that time, entire trucks would drive onto ships, wasting both a ton of potential cargo space, plus a chassis that could be on the road moving goods. McLean developed plans to use the so-called trailerships for travel from North Carolina to New York, but U.S. regulations didn’t allow one person to own both a trucking and a shipping company at the same time. So McLean did what any innovation-minded entrepreneur would do: He dumped the trucking company, took out a $22 million loan, and, in January 1956, bought two World War II T-2 tankers.

But while containers standardized a part of our physical infrastructure, there's a lot that remains fragmented and manual:

The same way data passes between devices via the internet, goods pass between ocean ports, airports, warehouses, and other entities to reach their final destination. Without a logistics standard to act as a request-response protocol, all the players — suppliers, drayage, ports, warehouses, buyers — have to stitch their networks together manually.

Information gets lost; layers of redundancy, designed as backups given low visibility, slow the exchange: connections end up being very brittle. Let’s say there’s a shipment scheduled to arrive in Long Beach on Tuesday. But which terminal exactly and what pier number? What time is pickup? How long before late charges are incurred? Finding these answers is labor-intensive and imprecise. Logistics managers end up consulting different sources on websites, via email, or in person.

A universal language for global trade

This article by Ryan Petersen is a good history lesson on how shipping containers came to be. Here is an excerpt:

The idea for containerization came from a trucker, not a shipper. Malcolm McLean started out hauling empty tobacco barrels with his family in North Carolina in 1935. At that time, entire trucks would drive onto ships, wasting both a ton of potential cargo space, plus a chassis that could be on the road moving goods. McLean developed plans to use the so-called trailerships for travel from North Carolina to New York, but U.S. regulations didn’t allow one person to own both a trucking and a shipping company at the same time. So McLean did what any innovation-minded entrepreneur would do: He dumped the trucking company, took out a $22 million loan, and, in January 1956, bought two World War II T-2 tankers.

But while containers standardized a part of our physical infrastructure, there's a lot that remains fragmented and manual:

The same way data passes between devices via the internet, goods pass between ocean ports, airports, warehouses, and other entities to reach their final destination. Without a logistics standard to act as a request-response protocol, all the players — suppliers, drayage, ports, warehouses, buyers — have to stitch their networks together manually.

Information gets lost; layers of redundancy, designed as backups given low visibility, slow the exchange: connections end up being very brittle. Let’s say there’s a shipment scheduled to arrive in Long Beach on Tuesday. But which terminal exactly and what pier number? What time is pickup? How long before late charges are incurred? Finding these answers is labor-intensive and imprecise. Logistics managers end up consulting different sources on websites, via email, or in person.