The main difference between GitHub Codespaces and a local development environment lies in where and how your development environment is hosted.
• Performance: Codespaces runs on cloud-powered machines, which can sometimes outperform local setups (especially if your local device has limited resources). That said, local development may feel faster for smaller projects where hardware isn’t a bottleneck.
• Customization: Both allow customization, but Codespaces leverages devcontainers to ensure consistent environments across a team, whereas local setups often vary from one developer to another.
• Collaboration: Codespaces shines here—every developer can instantly launch an identical environment without setup issues. This avoids the classic “works on my machine” problem.
• Security & Reliability: Since Codespaces runs in isolated containers, it provides strong security boundaries. It also integrates tightly with GitHub’s ecosystem, making it reliable for modern workflows.

When to choose what:
• Use Codespaces when collaborating with teams, onboarding new members quickly, or working from devices that aren’t very powerful.
• Stick to local development when you need complete offline access, fine-grained control over your setup, or if you prefer direct access to your machine’s resources.

In short, Codespaces complements local development rather than replacing it—giving developers flexibility depending on the project and context.

GitHub Codespaces improves team collaboration by giving everyone the same development environment. This removes common issues like different tool versions, missing dependencies, or configuration errors.

It also makes onboarding much easier. New team members can start coding immediately without spending time setting up the project locally.

Since it’s fully integrated with GitHub, developers can test branches, review pull requests, and fix bugs directly in the cloud. Overall, it helps teams work more smoothly and reduces setup-related problems.

To configure a GitHub Codespace with the right development environment, you’ll need to create a .devcontainer folder in your repository, which will contain the necessary configuration for setting up the container. You can define a devcontainer.json file to specify the image, extensions, and tools you want included. Here's a simple example:

{
  "name": "Node.js & MongoDB Dev Environment",
  "image": "mcr.microsoft.com/vscode/devcontainers/javascript-node:0-14",
  "features": {
    "mongodb": "latest"
  },
  "extensions": [
    "dbaeumer.vscode-eslint",
    "ms-vscode.vscode-node-azure-pack"
  ]
}

This configuration will ensure that when anyone opens the repository in Codespaces, they'll have a Node.js environment with MongoDB and the necessary VS Code extensions automatically installed. If you need to include additional dependencies, you can also add a Dockerfile to further customize the environment.

Hey @fpvandoorn, excited to hear that you'll be using Codespaces for the tutorial!

GitHub uses a number of systems both automated and manual to detect abuse on the platform. While we can’t promise nobody will run into one or more of these systems when creating an account during the event it’s unlikely that genuine people adhering to our Acceptable Use Policies and ToS will run into trouble here.