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

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

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         ...