# Week 1 Day 2: Start Hacking

## Hackathons

We do hackathons at the start of osoc to...

* *...really* get to know each other. It's your time to shine, show what you can do and see how your other team members can bring a project to the next level ✨
* ...run through a first *cycle* together; from defining what you're going to build, to building, to delivering a first valuable *thing*, which you will define during the scoping session.
* ...make mistakes. Please make a lot of mistakes and learn, to do better in the next cycle 🔥

### Examples

We want you to learn as much as possible from this hackathon, and it depends on the type of project you have what you're going to do.

* Refine the story; create a vision
* Create your wireframes/mockups
* A first prototype
* Try out a new technology
* Implement a first dataset
* ... Surprise us

### How

Not sure how to get started on this hackathon? Try a [**brainstorm**](https://help.osoc.be/global/coaches/the-coaching-job/how-to-manage-a-team#3-brainstorm-ideas-2-bonus-adaptions) to get the creative juices flowing, or do a [**scoping session**](https://help.osoc.be/global/coaches/the-coaching-job/how-to-manage-a-team#how-to-do-a-scoping-session) to narrow down what you're going to do. Take the time you need, the team decides when they are to start hacking! 

You're definitely free to do it *your way!* As long as the team is working together.

{% hint style="info" %}
Oh and remember the rule of **π** ([pi](https://twitter.com/pietercolpaert))... When doing an estimation of a task, let's say, for an hour, it's most likely to take about 3.14 times longer. Thank us later.
{% endhint %}