Lessons from a Minecraft City Build

On September 8, 2026, Mike Tomlin told TODAY anchor Craig Melvin something unexpected in the football world. “I’m a big Minecrafter,” the former Pittsburgh Steelers head coach said, describing how he had spent about 12 years building a single city in Minecraft’s creative mode. On September 30, 2026, that city was shared publicly on YouTube as “My 12 Year Minecraft City Build.”

The Origins of a 12-Year Build

Tomlin did not plan to build a metropolis. He started playing Minecraft to bond with his children. In the September 8 interview with Melvin, he said: “I started playing Minecraft, man, when my kids were young.” Over time, his kids lost interest and moved on to high school and then college, while his own involvement increased. “At different times over the course of the 12-month calendar, I would have different levels of fixation on this,” he said, describing a hobby that came and went.

The Reveal and the Social Media Response

That irregular pattern explains how a 12-year project stayed alive. Tomlin did not play every day. He returned to the same world in bursts, adding to it when his schedule allowed and pausing when the season demanded his attention. The consistency came from never starting over, not from never stopping.

The Scale and Detail of the City

The first episode, “ROOFTOPS, PENTHOUSES, AND URBAN LIVING,” focused on the downtown district and its high-rise interiors. The tour included a boutique hotel, restaurants, a CVS pharmacy, and multiple stadiums, plus the apartment and penthouse interiors that opened the series.

Tomlin described the design choices as a responsibility to the fictional residents. “I was always really conscious of appropriate amenities,” he said in the video. Instead of building monuments to himself, he created the infrastructure a functioning city requires, down to a chain pharmacy. The focus on realistic amenities rather than spectacle distinguishes a long-term world-building project from a simple toy layout.

The scale required a practical production choice. Dino, who filmed the tour at his father’s request, said the full tour had to be divided into sections because showing everything at once would have taken about two hours. A single-sitting walkthrough of that length suggests a world measured in neighborhoods, not just individual buildings. The series format, one district at a time, reflects that size.

The Playoff Splits Fans Could Not Ignore

The most shared angle was not the build but its timing. Tomlin said he started playing around 2014, placing the hobby’s start near when Pittsburgh’s postseason success began to decline. Fans compared the two timelines, and the split is clear.

Stat	Pre-2014	2014-25
Regular season record	71-41 (.634)	122-73-2 (.619)
Playoff record	5-3 (.625)	3-9 (.250)
Super Bowl wins (appearances)	1 (2)	0 (0)

Before he started playing the game, Tomlin led Pittsburgh to both of his Super Bowl appearances and the Lombardi Trophy. After 2014, the team won three playoff games in 12 tries and did not return to the title game. The numbers come from The Sporting News via Yahoo Sports, which detailed the splits after fans examined the timeline.

No one seriously claims a coach’s evening hobby caused his team’s January results. The correlation is a coincidence that happened to be amusing, and the framing is a joke, not a serious argument. But the split is the kind of statistic football fans enjoy debating, and it gave the reveal attention beyond the gaming press.

The regular-season numbers provide balance. Tomlin’s regular-season winning percentage changed little, from .634 before 2014 to .619 after. The decline was limited to the postseason, a narrower issue than the joke about distraction by a video game suggests, and the part of the split often left out of the meme.

The Reveal and the Social Media Response

Tomlin’s reveal followed a clear sequence: a brief mention on live television in early September, then a full YouTube launch on September 30 at 8 p.m. ET. The first episode’s thumbnail showed him holding a PlayStation DualSense controller in front of the skyline he had built.

The wider fan response divided predictably. Many admired the dedication to a single detailed project over 12 years. Others, especially Steelers fans frustrated by the late-career playoff drought, turned the timeline into the “splits” meme above. Both reactions reflect the same surprise: a figure known for emotional restraint had been running a personal creative project the entire time, and nobody outside his family knew.

Save-File Continuity Across Three Consoles

The most relevant detail for developers is the migration. A world that survives moving from PS3 to PS4 to PS5 only lasts because someone treated the save file as an asset worth preserving. Tomlin’s sons handled the maintenance he could not, a clear example of a problem every long-running project faces: the person who builds is not always the person who can keep it going.

For a software team, the equivalent is a system that outlives its creator. The practical question is whether the project’s state is recorded somewhere beyond one person’s memory. Here is a simple way to log the state of an incremental build so it can be handed off, written in Python and ready to run.

import json
from datetime import date

# Note: production use should add file locking and validate the schema on load.
def log_build_session(log_path, district, blocks_added, note):
 try:
 with open(log_path, "r") as f:
 sessions = json.load(f)
 except FileNotFoundError:
 sessions = []
 sessions.append({
 "date": date.today().isoformat(),
 "district": district,
 "blocks_added": blocks_added,
 "note": note,
 })
 with open(log_path, "w") as f:
 json.dump(sessions, f, indent=2)
 return len(sessions)

count = log_build_session("city_log.json", "downtown", 2400, "Finished penthouse roofs")
print(count) # Expected output: 1 on first run, incrementing after

This is a simple logger, but the point is the same one the console migration illustrates. A project that spans years and multiple people needs a written record of what changed and when, or the next person to work on it has to reconstruct the history from scratch. Tomlin’s sons could move the file because it existed as a discrete artifact. A build stored only in his memory would not have survived the first console swap.

The same idea applies to tracking the scope of a large build over time. The two-hour tour suggests the city is large enough that no single session covers it, so the natural unit of work is a district rather than the whole world. A small function that sums progress by district makes that visible.

def progress_by_district(sessions):
 # Note: production use should handle missing keys and non-numeric values.
 totals = {}
 for s in sessions:
 district = s["district"]
 totals[district] = totals.get(district, 0) + s["blocks_added"]
 return totals

sample = [
 {"district": "downtown", "blocks_added": 2400},
 {"district": "downtown", "blocks_added": 800},
 {"district": "stadiums", "blocks_added": 1500},
]
print(progress_by_district(sample))
# Expected output: {'downtown': 3200, 'stadiums': 1500}

Neither snippet models Minecraft itself. They address the bookkeeping challenge a 12-year, multi-person project creates, the part of Tomlin’s story that applies directly to software development.

What a Decade-Long Build Teaches Builders

Removing the football context, the story is an example of sustained, incremental creation. Tomlin did not build the city in one burst. He added to it over a 12-year period, working in creative mode with “different levels of fixation” at different times, returning to the same world rather than starting over. That approach explains why the result feels like a coherent place rather than a collection of experiments.

There is a practical design lesson in his “appropriate amenities” comment. He built a pharmacy and restaurants because a city needs them, not because they were the most impressive structures he could make. That is the same instinct that keeps a software project focused: decide what the project is for, then build what that purpose requires. A city for fictional residents needs a pharmacy. A tool for a specific user needs the features that user actually uses, not the ones that look good in a demo.

The comparison that fits best is a long-running open-source project maintained by one person and kept alive by a small group of helpers. The maintainer has the vision and persistence. The helpers handle migrations, upgrades, and tasks the maintainer cannot do. Tomlin and his sons divided the work that way, and the city exists because both roles were fulfilled for 12 years. This is the same pattern behind an open source 3D printable desktop robot, where one person holds the vision while contributors keep hardware revisions and firmware builds current.

For builders and developers, the takeaway is not to “play more Minecraft.” It is that a project you return to over years, even in small increments, grows into something a one-time effort cannot produce. Tomlin’s city is the example: a downtown, a pharmacy, and multiple stadiums assembled one block at a time, mostly during the margins of a 19-season NFL coaching career.

Tomlin’s September 8 interview with Craig Melvin on TODAY first revealed the story, and Awful Announcing collected the key quotes, including the PS3-to-PS5 migration. The playoff splits come from The Sporting News via Yahoo Sports, and the details of the city’s contents and Bell’s reaction are covered in Yahoo’s report on the reveal.

More in-depth coverage from this blog on closely related topics:

Sources and References

Sources cited while researching and writing this article: