About the challenge
Durham College’s Faculty of Science, Engineering, and Information Technology (SEIT) is excited to host its first annual hackathon on starting March 22nd @ 9am and finishing March 23rd @ 4pm, 2025. This event aims to empower IT students to solve community challenges with innovative and creative technology solutions. Participants will have the chance to achieve things they may not have thought possible, gaining hands-on experience in coding, design, and problem-solving. Over a 24-hour period you will engage in a marathon of creativity and collaboration, where small teams will work together to develop solutions solutions that have a potential to make a significant impact on the community.
Saturday, March 22, 2025
|
Time |
Event |
|
9:00 AM |
Check-in starts |
|
10:00 am |
Welcome remarks |
|
10:15 am |
Keynote speech |
|
10:45 am |
Durham Region Transit Speaker |
|
11:00 am |
Hackathon begins |
|
12:00 pm |
Lunch Served |
|
1:30 – 2:00 pm |
Workshop: Effective Communication Through Questions with Alex Seeds |
|
6:00 pm |
Dinner served |
|
8:00 pm |
Midnight snacks |
Sunday, March 23, 2025
|
Time |
Event |
|
9:00 am |
Breakfast served |
|
11:00 am |
Hackathon submissions due |
|
12:00 pm |
Lunch served |
|
1:00 – 3:00 pm |
Judging |
|
3:30 pm |
Closing remarks and awards ceremony |
Requirements
What to Build
Any app, website, interface or other technology that you think could improve experience or usability of Durham Region Transit. It is highly suggested that you use Durham Region Transit OpenData in your project in some way.
What to Submit
Submissions must include all of the following information:
- Name of Project
- Project Story (What you set out to achieve)
- Description of how your team stretched themselves.
- Link to a github repository containing the code for your submission.
Prizes
TBD
TBD
TBD
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
A qualified panel of judges will be announced soon
Judging Criteria
-
Completion
Does the hack work? Did the team achieve everything they wanted? -
Learning
Did the team stretch themselves? Did they try to learn something new? What kind of projects have they worked on before? -
Design
Did the team put thought into the user experience? How well designed is the interface? -
Technology
How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique or did it use many different components? Did the technology involved make you go "Wow"?
Questions? Email the hackathon manager
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.