Mentorship Guidelines

  1. Take time to think about the problems that your specific track faces with the distribution, analysis and visualization of information.
  2. Check out our blog, the challenges that the community of Durham have worked together to create and the datasets available!
  3. Get excited!

Location, Parking & Schedule?

Arrive at 10:30am on Saturday to help your recruiter set up the table. 11:00am is when lunch starts and students will be walking around and getting to know you. This will go on for an hour until we will start ushering people to walk over to Griffith Auditorium for the opening ceremony. If you are not a software engineering mentor associated with a company, I would suggest you go to the Code for Durham table.

The exact location, where to park and detailed Google maps directions can all be found here. The schedule can be found here.

How do I best engage with the participants?

Join the HackDuke 2014 Participants Facebook Page! Typically, day of, hackers will be posting on the Facebook group or Tweeting to find the mentors who will be able to help them out if they can't immediately find you in person, so check back! Most of the hacking will be taking place in either the atrium of CIEMAS or Schiciano Auditorium.

Don't be afraid to approach the participants, and don't stay at your company table 24/7. We strongly encourage you to walk around, talk to the hackers, ask them questions and help them out with their hacks. We will be encouraging them to come and interact with you, but remember, it takes two to tango (and create some awesome hacks!).

Novices?

We do have a track specifically for novices, and a space (Schiciano Auditorium) specifically for them as well. If you've marked that you want to help out novices, please make it a point to visit Schiciano Auditorium every once in a while. You are free to help them with their hacks to your best judgement. This means if a group is having trouble with their dev environment, or having trouble setting up your API and this is their first time at a hackathon or this is their first exposure to computer science, it is not against the rules to give them a little boost.

Opening Ceremony API Flash talks and Tech talks?

The lineup for the opening ceremony API flash talks is here, under the Opening Ceremony tab. All companies have a maximum of 3 minutes to demo. Please format your presentation to that time constraint. If we run over time, this will negatively impact our schedule for tech talks.

Those mentors who are giving a tech talk should be checking here to find out where and when they are talking.

Judging & Prizes?

We hope all of you will be able to make it back on Sunday for the expo and judging. The judging for our hackathon will be a little bit different. We will be deciding a winner and one runner up for each track during the expo. There will not be a special judging portion to decide the final winners during the closing ceremony. We will be using ChallengePost to do our hack submissions.

The expo will be split into 2 sections. Poverty & Inequality and Education will be the first segment. Health & Wellness and Energy & Environment will be the second. For companies who have API prizes, we will give you a list of all hacks related to your prize track, but we also expect you to help us judge the Grand Prize winners and the Novice winner after you've done that. We will be giving the rest of the mentors table numbers a few at a time to check out and indicators of whether these hacks are also novice hacks.

Judge the hacks based off of:

  • Problem
    Understanding of the community the hack is aimed at, Understanding of the problem attempting to be solved, Extent to which the problem is solved or mediated
  • Technical
    Technical ingenuity and ambition, Project difficulty
  • Viability
    Ability for the hack to be utilized in the real world, Long term usefulness of the hack