Skip to main content

Start your own coding adventure with GitHub Copilot

Imagine learning programming concepts not through dry textbooks or boring exercises, but by embarking on epic quests in mystical realms. Doesn't sound that appealing to you? Yes? Join Copilot Adventures, Microsoft's innovative approach to coding education that transforms programming practice into an engaging, story-driven experience.

What is Copilot Adventures?

Copilot Adventures is an open-source educational project that combines the power of GitHub Copilot with immersive storytelling to teach programming concepts. Instead of solving abstract problems, you work through coding challenges embedded in rich fantasy narratives—from mechanical clockwork towns to enchanted forests where mystical creatures perform sacred dances.

The project leverages GitHub Copilot, Microsoft's AI-powered coding assistant, to help learners write code while exploring these fictional worlds. It's essentially a "choose your own adventure" for programmers, where each story presents unique coding challenges that must be solved to progress through the narrative.

The adventures are structured across three difficulty levels:

Beginner Adventures

  • The Clockwork Town of Tempora: Learn time calculations and synchronization
  • The Magical Forest of Algora: Master algorithms through mystical creature interactions

Intermediate Adventures

  • The Celestial Alignment of Lumoria: Dive into complex mathematical calculations
  • The Legendary Duel of Stonevale: Implement game logic and strategy systems
  • The Scrolls of Eldoria: Work with data processing and text manipulation

Advanced Adventures

  • The Gridlock Arena of Mythos: Build sophisticated game engines and AI systems

Starting your adventure

Ready to start your own adventure? The only thing you need to do is to Create a new codespace to get started.

https://codespaces.new/microsoft/CopilotAdventures

Remark: It is also possible to clone and run the repo locally if you really want:

git clone https://github.com/microsoft/copilotadventures

Have fun!

More information

microsoft/CopilotAdventures: Copilot coding adventures

https://codespaces.new/microsoft/CopilotAdventures

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more