Original reporting by TechRepublic. This article summarises lessons and observations from the Deserted Island DevOps conference, a virtual event streamed on Twitch in spring 2020.
What Was Deserted Island DevOps?
Deserted Island DevOps was a virtual conference held inside Animal Crossing: New Horizons on the Nintendo Switch and streamed live on Twitch. Organizers built a classroom-style island space inside the game, and speakers — including developer advocates and engineers from HashiCorp, Heroku, IBM, and Red Hat — attended as in-game avatars to deliver real technical and cultural talks. More than 10,000 people watched the stream, making it one of the more unusual and well-attended virtual tech events of the COVID-19 lockdown period.
The conference covered topics ranging from mob programming and platform security to psychological safety and resilience engineering. Recorded sessions were made available on Twitch after the event, and conversations ran in parallel across the event’s Discord server and on Twitter under the hashtag #DIDevOps.
1. Timing and Context Matter Enormously for Community Events
A DevOps conference set inside a cheerful, pastel-coloured game about building a small island community turned out to be exactly the right format for a moment when much of the world was in COVID-19 lockdown. Twitch chat was overwhelmingly positive throughout the event, and audience Q&A at the end of every session — always a reliable signal of genuine engagement — was active and substantive.
Audience reactions on Twitter reinforced the point:
“I’m not even on Animal Crossing and I still think this is genius.”
“Nobody’s here to flex. Not a single person has said, ‘Hey look at this cool thing I built!’ It’s all about the team, the culture, and building empathy.”
“Not only did I learn heaps about cloud stuff, it was a genuinely enjoyable experience.”
The lesson for DevOps teams organising internal or community events: the format should reflect the emotional context of the audience, not just the technical agenda.
2. Unconventional Formats Can Produce Genuine Engagement
Up to eight players can share an Animal Crossing island simultaneously. The organiser built a classroom within the game, complete with a podium, a screen for slides, and seats for a live audience of speakers. Presenters flew their avatars into the island and sat in the audience when not speaking — a surprisingly effective way to create a sense of shared presence.
The format layered three communication channels on top of the game stream:
- Twitch chat — live commentary and reactions during sessions
- Discord — a hallway track, speaker Q&A threads, and general networking
- Twitter (#DIDevOps) — broader public conversation and speaker follow-up
Speakers were also connected to each other via a shared Zoom call, solving the “talking into the void” problem that plagues most webinar-style online conferences. This gave presenters a human audience to react to, even if that audience consisted only of other speakers.
Developer Jessica Joy Kerr, who attended the event, captured the contrast bluntly: “Any other online format I’ve tried, you’d have to pay me to do again.”
3. Developer Advocates Bring a Unique Creative Lens to Technical Problems
Eight of the twelve speakers were developer advocates — practitioners who bridge engineering teams and the broader developer community. The conference highlighted how that role combines technical depth with communication skills and creative problem-solving.
A notable example: Jacquie Grindrod, a developer advocate at HashiCorp, built a game called Spack Hack to illustrate Raft, a Go library used to manage a replicated log — a foundational concept in distributed systems consensus. The game didn’t ship, but that wasn’t the point. Grindrod applied core DevOps principles to the side project itself: scalable infrastructure design, infrastructure as code, and consistent build and deployment pipelines.
Her takeaway applied as much to DevOps culture as to game development:
“The heart of building good DevOps culture is bringing systems and people together in a community that collaborates to solve problems. We’re all here solving this problem together.”
Jacquie Grindrod, Developer Advocate, HashiCorp
4. Resilient Communities Are Built Deliberately — and in Advance
Multiple sessions focused on the human and cultural dimensions of DevOps rather than tooling or infrastructure — and the depth of those conversations surprised many attendees. As one Twitch viewer commented: “This talk is way deeper than I was expecting.”
Key sessions included:
- Ian Coldwater (Lead Platform Security Engineer, Heroku) discussed practical approaches to DevOps and security teams working together rather than in opposition.
- Adrienne Tacke (Software Engineer and Developer Advocate, MongoDB) explored failure — using wasp stings in Animal Crossing as a metaphor — and how teams respond when things go wrong.
- Matt Stratton (Transformation Specialist, Red Hat) delivered a talk titled “Kick ’em or Keep ’em: Collaborating on our own deserted islands,” drawing on Google’s research into high-performing teams to explain how to build psychological safety. His practical recommendations included:
- De-escalating conflict before it becomes entrenched
- Running blameless postmortems
- Creating conditions where people feel safe to participate
- Replacing blame with curiosity
- Modelling vulnerability as a leader
Aaron Aldrich, a developer advocate at LaunchDarkly, connected community building directly to resilience engineering — a discipline more commonly applied to systems than to people:
“Community building is resilience engineering, and that’s why developer relations is always thinking about that.”
Aaron Aldrich, Developer Advocate, LaunchDarkly
Aldrich’s core argument: resilience is not reactive. Teams and communities that handle adversity well have invested in shared common ground long before a crisis hits. Diverse teams with high psychological safety are better positioned to sustain and repair themselves under pressure.
5. Novel Formats Come With Novel Logistics Challenges
Running a professional conference inside a Nintendo Switch game introduced some genuinely new presenter challenges. Speakers had to control their Animal Crossing avatar with a game controller while simultaneously managing slide transitions — a coordination task with no real precedent in traditional conference presenting. There is no equivalent of “make eye contact with the front row” when your audience is a grid of cartoon islanders.
On the other hand, the format eliminated at least one classic conference hazard: no speaker accidentally walked away from the podium with the only laptop running their presentation.
For DevOps practitioners who are less familiar with streaming platforms, the event also served as an accidental crash course in how Twitch, Discord, and Animal Crossing work as community spaces — a useful orientation given how much developer community activity now runs through those channels.
Why This Matters Beyond the Novelty
Deserted Island DevOps was more than a curiosity. It demonstrated that the format of a technical event shapes the culture of the conversation. By choosing a playful, low-stakes visual environment and deliberately layering in multiple participation channels, the organisers created conditions where attendees focused on collaboration and learning rather than personal branding. That outcome doesn’t happen by accident — it’s the product of intentional community design, which is itself a DevOps skill.
The recorded sessions are available on Twitch via the Deserted Island DevOps channel.