Every developer community has a handful of people who show up early, keep showing up, and quietly become the reason the community exists at all in a given city. In Freiburg, Germany, that person is Mohammad-Ali A'râbi, a software engineer, author, and Docker Captain whose path into containers started, like a lot of good origin stories, with a week of pure frustration.
Back in 2015, working as a backend engineer at Cafe Bazaar in Iran, Mohammad-Ali spent an entire week fighting dependency hell trying to get a Django project running locally. A colleague mentioned, almost as an aside, that the team used something called Docker in their CI pipeline. Docker was barely two years old at the time, and Mohammad-Ali had never heard of it. He disappeared for a week to learn it properly, and came out the other side building CI pipelines for other projects across the company.
A stint in Amsterdam between 2018 and 2019 gave him a taste for the tech meetup scene there, and when he moved back to Freiburg, he found there wasn't one. Colleagues kept coming to him with git and Docker questions often enough that he started writing the answers down on a blog, initially just as a reference for himself, though it turned out other people found the posts useful too. Then the pandemic hit, and in his own words, he got depressed, which became the push he needed to finally start a Freiburg meetup group himself, since none existed.
The first meetup, in November 2022, drew exactly one outside attendee, who'd traveled all the way from Strasbourg, France, to be there. Counting Mohammad-Ali, his wife, one of the venue's founders and her boyfriend, and an engineer from the host company, that's five people total in the room. The second meetup was a watch party for Docker's Community All Hands, and by that point Mohammad-Ali already had two blog posts published on Docker's own site and a talk lined up for the event, work that earned him the title of best Docker Community Leader. By early 2023, when he applied to become a Docker Captain, plenty of people at Docker already knew who he was.
That trajectory, from one confused week fighting a Django setup to an officially recognized community leader, tracks a pattern common among the most effective advocates in any technical community: they didn't set out to build an audience, they solved their own problem loudly enough, in public, that an audience found them.
Mohammad-Ali's more recent work includes a fantasy story set in 1865 Freiburg that teaches container security concepts through narrative rather than a conventional tutorial, part of a broader interest in making dense DevOps material memorable through story and character rather than another wall of bullet points. He's also working on the second edition of his book on Docker and Kubernetes security, and on growing the Freiburg meetup, already recognized as a CNCF chapter, into something with more regular cadence, while quietly weighing whether to start a separate Java User Group to pull in a wider crowd.
Asked what he'd be doing if not this, he doesn't hesitate toward anything predictable. Mathematics, specifically logic, was where his unfinished master's research sat before he moved into computer science, and he mentions an interest in ancient languages, including the ability to read Old Persian cuneiform, as a path he might have chased instead. It's a reminder that a lot of the people building the infrastructure the rest of us rely on came in sideways, through logic and language rather than a straight line from "I always wanted to write software."
On the practical side, his advice for anyone building a new microservice reads like hard-won scar tissue rather than theory: don't lock into a database decision before you have to, pick one way to run the project locally instead of three that will inevitably drift out of sync, and automate deployment rather than SSHing into a box and hoping. He's candid, too, about the limits of leaning on an AI coding assistant, noting that he corrects Claude Code's suggestions roughly half the time and treating that correction step as non-negotiable rather than an annoyance, pointing to research suggesting a meaningful share of AI-generated code carries security issues if nobody's checking.
Asked, finally, what non-technical object he'd containerize if he could, he goes for something almost poetic: snapshots of the world itself, so he could choose which version to live in. It's a strange, oddly moving answer from someone whose day job is making sure software runs the same way everywhere it's deployed, and it's the kind of answer that only makes sense once you've heard the rest of the story.