Software Development

Inside a software developer’s data-driven approach to visiting every MLB ballpark

Mike Mountain is going to 30 baseball cities in 35 days. What started as a side project during a Catalyte training program became MLB Road Trip.

Mike Mountain, before hitting the road. (Courtesy photo)

Like many baseball fans, Mike Mountain often thought about visiting every Major League ballpark.
It’s a bucket list item that takes years for some, but Mountain often thought about completing the trip in a single season. During training to become a software developer, Mountain started experimenting and found that it was possible to complete in just a little more than a month.
After optimizing routes, Mountain set out on July 21 for his MLB Road Trip, aiming to see games at 30 stadiums in about 35 days. He was in the midst of a West Coast swing early this week.


Catalyte, which is based downtown, provides software development teams that work within large businesses. As we’ve reported, the company takes a unique approach to bringing on new workers by using predictive analytics to identify promising candidates who weren’t previously software developers, and training the team members.
For Mountain, who joined Catalyte in 2014 after working at an alarm monitoring company, the training program also offered the chance to work on a side project. Having previously visited 15 stadiums, the idea of completing the baseball trip stood out.
“A lot of the ones I’m missing are on the West Coast or Florida,” he said in an interview a day before departure from Baltimore on July 20. So, when he started to experiment with creating his own algorithms and programs during the training program at Catalyte, he realized he could create new tools to work with routes and schedules. So, he thought, “Let’s try and knock everything else at once.”
In creating Java programs using the MLB schedule and other data from tools like Google Maps, Mountain said time and miles were two of his main considerations. He wanted to identify the schedule that would get back to Baltimore in the quickest fashion, and, within that, the distance between each destination.
He consulted the Harvard Sports Analysis Collective and a supercomputing cluster at the University of Wisconsin, which helped to speed up the process of arranging 2,430 games.
“The number of combinations is quite large and to calculate all that on a home PC or laptop would take about a month or more,” he said.

Tickets to 30 games. (Courtesy photo)

Tickets to 30 games. (Courtesy photo)


There were multiple tweaks over time. An initial version, for instance, didn’t account for sleep. And there were some surprises along the way, as he’ll be seeing the Milwaukee Brewers a number of times along the way. Now leading a team of software developers within a Catalyte client, he decided on this summer to put it into action. He’ll finish in Baltimore on August 24, when his beloved Orioles take on the Yankees.
“It was an opportunity to do something for myself and show myself that I really did know what I needed to know to make this happen,” he said.

Before you go...

Please consider supporting Technical.ly to keep our independent journalism strong. Unlike most business-focused media outlets, we don’t have a paywall. Instead, we count on your personal and organizational support.

Our services Preferred partners The journalism fund
Engagement

Join our growing Slack community

Join 5,000 tech professionals and entrepreneurs in our community Slack today!

Trending

Baltimore is setting a national standard for diversifying its economy

19 tech and entrepreneurship events to check out before the holidays

Tech lab space opening in new 4MLK building, thanks to $2M in public funds

EDA officials are ‘hopeful’ Tech Hubs program will live on under Trump

Technically Media