|
1 | 1 | # Hack Days |
| 2 | + |
| 3 | +**Hack Days** are mini-hackathons hosted by the CCSS. They’re designed to give students a focused space and dedicated time to work on projects — whether that’s something we’ve prepared in advance or something entirely self-directed. |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## 🧩 What Happens at a Hack Day? |
| 8 | + |
| 9 | +Hack Days usually follow one of two formats: |
| 10 | + |
| 11 | +- 🛠 **Project-Focused** — We come prepared with specific projects or starter tasks for students to tackle. These might involve: |
| 12 | + |
| 13 | + - Open source contributions |
| 14 | + - Club tech projects |
| 15 | + - Coding challenges or tutorials |
| 16 | + |
| 17 | +- 🎨 **Freeform** — Students show up and work on **whatever personal or group projects** they want — portfolio pieces, games, tools, etc. |
| 18 | + |
| 19 | +No matter the format, Hack Days are about **building, learning, and collaborating** in a chill environment. |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +## 📌 Example: Open Source Work Day (2023–2024) |
| 24 | + |
| 25 | +One example of a Hack Day was our [**Open Source Work Day** (Oct 21, 2023)](https://ccss.carleton.ca/events/2023-2024/2023-10-21-open-source-work-day/). |
| 26 | + |
| 27 | +- 🕙 Ran from **10:00 AM to 5:00 PM** |
| 28 | +- 🍕 **Provided pizza** for attendees |
| 29 | +- ✅ Organized around **two open-source projects** with pre-created issue lists |
| 30 | +- 💬 Students worked in groups or solo and were encouraged to ask for help throughout the day |
| 31 | + |
| 32 | +--- |
| 33 | + |
| 34 | +## ⚠️ Things to Consider |
| 35 | + |
| 36 | +### Have beginner accesible options |
| 37 | + |
| 38 | +Students do not want to waste their entire day on environment setup or struggling through a single task. Make sure you have project options that require extremely minimal setup so everyone has a good time. |
| 39 | + |
| 40 | +### Have a plan or fallback |
| 41 | + |
| 42 | +Even if it's a freeform day, it helps to have some starter ideas or projects in case people need inspiration. |
| 43 | + |
| 44 | +### Make it full-day friendly |
| 45 | + |
| 46 | +Provide **food, water, and space** to take breaks — especially if you’re running a full-day event. |
| 47 | + |
| 48 | +### Start with a brief intro |
| 49 | + |
| 50 | +Set expectations, introduce any projects, and make sure new students feel welcome and comfortable asking questions. |
| 51 | + |
| 52 | +### Encourage collaboration |
| 53 | + |
| 54 | +Hack Days are a great place to meet others and try working in teams — help facilitate that where possible. |
0 commit comments