Skip to content
A collection of challenge based hack-a-thons including student guide, proctor guide, lecture presentations, sample/instructional code and templates.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
001-IntroToKubernetes Changed the name of the machine that is built to remove the word "agent" Oct 10, 2018
002-IntroToAzureAI Added a header marker for each Hack's root README Oct 10, 2018
003-DrivingMissData clarification to copy data workaround v2 storage Feb 16, 2019
005-RockPaperScissorsBoom Made the directions for creating a docker host a little more explicit Feb 14, 2019
006-AppModernization Fix to Student Guid Oct 16, 2018
007-AzureMonitoring update to dotnet 2.2 Jan 8, 2019
.gitignore Update .gitignore Oct 16, 2018 Added a Contributing file and modified the README to point to it Oct 15, 2018
LICENSE Initial commit Sep 17, 2018
What The Hack - Event Kickoff.pptx
What The Hack - How To Hack.pptx Added in our deck for how to run a hack. Sep 27, 2018

What, Why and How

  • "What the Hack" is a challenge based hackathon format
  • Challenges describe high-level tasks and goals to be accomplished
  • Challenges are not step-by-step labs
  • Attendees work in teams of 3 to 5 people to solve the challenges
  • Attendees "learn from" and "share with" each other
  • By having to "figure it out", attendee knowledge retention is greater
  • Proctors provide guidance, but not answers to the teams
  • Emcees provide lectures & demos to setup challenges & review solutions
  • What the Hack can be hosted in-person or virtually via MS Teams

How to Add Your Hack

We welcome all new hacks! The process for doing this is:

  • Fork this repo into your own github account
  • Create a new branch for your work
  • Add a new top level folder using the next number in sequence, eg:
    • 011-BigNewHack
  • Within this folder, create two folders, each with two folders with in that looks like this:
    • Host
      • Guides
      • Solutions
    • Student
      • Guides
      • Resources
  • The content of each folder should be:
    • Student/Guides: The Student's Guide
    • Student/Resources: Any template or "starter" files that students may need in challenges
    • Host/Guides: The Proctor's Guide lives here as well as any Lecture slide decks
    • Host/Solutions: Specific files that the proctors might need that have solutions in them.
  • Once your branch and repo have all your content and it formatted correctly, follow the instructions on this page to submit a pull request back to the main repository:


This repository is licensed under MIT license. More info can be found here.


We welcome contributions and suggestions. More info can be found here.

You can’t perform that action at this time.