From 8-Year-Old BBS Hacker to Chef Creator: How Adam Jacob Invented Modern Operations

I. The BBS Boy

At age 8, Adam Jacob discovered he could connect to Bulletin Board Systems (BBS) using his family computer. This opened a new world where he discussed politics and military topics with adults and played text-based RPG games — players dialed into a BBS, a Dungeon Master narrated scenarios like "you enter a dark forest," and each player typed their character's actions. This imaginative, improvisational style captivated him for years; no one online knew he was a child.

At 12, the online group decided to meet offline at the Dungeon Master's house. Adam's mother drove him there with dice and chips. He found 20- to 40-year-olds who were stunned: "Who are you?" — "I'm Adam." — "We need to talk to your mom." After some hesitation, they let him join because they had already played together online for years.

II. Drop Out of College

Obsessed with BBS, Adam wanted to run his own. He downloaded BBS software, learned to customize menus and install door games. To support multiple users, he needed a multi-tasking OS — first tried IBM OS/2 Warp (expensive), then discovered Linux. Linux changed his life: he could see all OS source code and found a community of passionate, selfless contributors. He quickly became one of them, fixing a bug in Red Hat's installer that prevented automatic installation on his system, submitting the patch to Red Hat. The patch appeared in Red Hat's errata, and when Red Hat went public, they sent him a gift: "Thanks for your patch."

Because he spent so much time tinkering with computers and software, he neglected school, often skipped classes, and at 16 got a job doing technical support for an ISP (Internet Service Provider). It was the wild-growth era of the internet; ISPs sprang up in garages and dental offices. He worked as a system administrator for these ISPs, setting up modems and maintaining Linux, FreeBSD, Windows NT. He only completed one semester of university — his freshman-year job paid as much as a university graduate's salary, and his advisor said: "Then why go to university? Drop out!" So he did.

After several years he accumulated valuable skills in networking, operating systems, and programming, becoming a sought-after figure in the industry.

III. Starting a Business Out of Frustration

But Adam discovered that system administrators were deeply discriminated against . At one company with 20 sysadmins, they had a "System Administrator Day" where leaders took them out for beer and said: "Happy Sysadmin Day, too bad you weren't smart enough to be developers!" He considered this the ultimate insult.

Worse, at a public company he held stock options but couldn't sell them. The Chief Legal Officer refused to sign, saying: "That would cause me trouble, and other executives too." Adam realized he, as a sysadmin, was on a restricted-trading blacklist. He decided: "Keep the stock, I'll vindicate system administrators!" He immediately left the building, called his best friend: "Let's start a sysadmin consulting company — building automated infrastructure for startups."

They quickly signed a $20,000 contract and automated everything: OS installation, backup, application deployment, monitoring, database management. During consulting, Adam met Jesse Robbins, Amazon's "Master of Disaster," who frequently "created disasters" to train systems and engineers to handle unexpected events — a practice now called chaos engineering .

Adam tried to hire Jesse, but Jesse said: "I won't leave Amazon for your damn consulting company, but if you build a product, call me." So Adam spent months developing a tool to simplify consulting work — Chef .

Chef works like an "automated chef": you write "recipes" and "cookbooks," and Chef configures your servers to ensure every machine runs as expected. For example, to automatically install Nginx and configure it on 100 servers:

Write an nginx recipe

Place it in a cookbook

Upload the cookbook to Chef Server

Each server runs Chef Client, fetches the recipe, and executes it

Nginx installation + configuration completes automatically — no manual per-server work

Chef codified, automated, and standardized operations work, dramatically improving efficiency and reliability. Adam showed Chef to Jesse, who said: "We should fund this, let's go!" Jesse joined as CEO.

While promoting Chef, they met Ezra Zygmuntowicz, a prominent figure in the Ruby and infrastructure community. When Redis first appeared, Ezra built the first Ruby client library and promoted it on Twitter, helping Redis spread rapidly in the Rails community. Ezra was building a PaaS platform and needed automated deployment; seeing Chef, he said: "Great, this is exactly what I want." He used Chef to automate his PaaS and selflessly promoted Chef — without him, they could not have succeeded. Ezra had ample resources, top Ruby talent, and more fame; he could have built a competing Chef and crushed them. Instead, he helped advance the infrastructure automation field — embodying the early internet spirit.

IV. System Administrators Are Programmers

In traditional IT architecture, development and system administration were sharply separated roles. When writing Chef, Adam defined system administrators as programmers — they always were. Both possess the same skills and solve the same problems, only with different focus. Sysadmins write code to define system behavior; systems are no longer manually configured but defined like application code.

This philosophy evolved into the Infrastructure as Code (IaC) movement. It profoundly changed enterprise IT management. Gradually, the "system administrator" role diminished, replaced by a new role: Operations (运维) . One evaluation stated: "If you list five people who truly changed how the IT industry works, Adam Jacob is one of them." Adam considers this extremely high praise.

V. Epilogue

IT moves fast. In 2013, Docker appeared, profoundly changing software deployment and shocking the industry. Then Kubernetes arrived — cooler than Docker — and everyone talked about Docker, k8s, cloud computing. Even their own investors and customers asked: "You're done for, right?"

It was indeed scary. Chef originally focused on "infrastructure automation" (IaC), but as more enterprises moved to the cloud, AWS or Azure began managing that infrastructure, reducing demand for Chef. However, Adam believes DevOps has ceased to be a niche slogan and become standard practice globally. Those once-looked-down-upon system administrators are now called "Platform Engineers," "SREs," "Cloud Architects" in boardrooms — and that is enough.