What is Hack Your Learning?
Hack your Learning is an organization within the University of Calgary that strives to allow students of all experience levels to gain an insight into hackathons, with several small-scale prep sessions as well as larger Hackathons hosted. Our main goal is to make sure all participants are comfortable and have an enjoyable experience at any Hack Your Learning events, big or small. We expect that if you would like to attend any events hosted by Hack Your Learning, you are going to adhere to the code of conduct displayed below. We hope that everyone who attends an event is treated with both fairness as well as respect!
In order to be eligible to participate in this hackathon, you must be an undergraduate post-secondary student currently studying at a Canadian University.
If you are a current ENSF409 student at the University of Calgary, you may join the ENSF409 Stream or the General Stream. If you do decide to join the ENSF409 Stream, your team for this hackathon must be the same as your Project Team (3-4 members). If you decide to participate in the General Stream, your team may consist of non ENSF409 students.
If you are a non ENSF409 student, you are unable to participate in the ENSF409 Stream and are only able to compete in the General Stream.
Participants in the General Stream can have a team constisting of 1-4 members.
A DevPost submission is mandatory in order to submit your project to this hackathon so please allocate time appropriate to your DevPost submission. Only one of your team members will need to create the submission (It will prompt you to add the rest of your team members on DevPost).
Judging will be based solely on your DevPost submission so it is important to put sufficient work into the submission itself. Judges will select advancing teams based on DevPost submissions and only advancing teams will be invited to attend a live-judging session to determine the final winners. Please ensure that all your team members are registered on your DevPost submission.
The project must have been made between the allocated Hackathon time. (March 27th, 10:00am MDT - March 28th, 11:00am MDT) Projects that are not made between this time will be disqualified.
In your DevPost submission, you are required to submit:
3-minute video showcasing your project and/or pitch.
Markdown file describing your project and any relevant information to the project.
Link to your GitHub repository.
Note: For the ENSF409 category, you are required to upload your UML diagrams to the github repo that your team is submitting.
The submission deadline will not be extended, so please submit the DevPost before the deadline at 11:00am MDT on Sunday, March 28th.
$CAD800 in prizes
1st Place - ENSF409 Category
First place in the ENSF409 Stream. (Please read the Eligibility section for more details on the ENSF409 Stream)
1st Place - General Category
First place in the General Stream. (Please read the Eligibility section for more details on the General Stream)
2nd Place - ENSF409 Category
Second place in the ENSF409 Stream. (Please read the Eligibility section for more details on the ENSF409 Stream)
2nd Place - General Category
Second place in the General Stream. (Please read the Eligibility section for more details on the General Stream)
3rd Place - ENSF409 Category
Third place in the ENSF409 Stream.(Please read the Eligibility section for more details on the ENSF409 Stream)
Submitting to this hackathon could earn you:
Hack Your Learning Industry Judges
User Interface Design (UI/UX)
40% | How does the design work? How does the user interact with the program (GUI/Command Line/UI) Does the solution come with appropriate documentation on how to use it?
30% | How efficient does your solution address the problem? How many cases can it handle? How modular or scalable is it if the problem is modified?
10% | Did all the members of the team work well? Is it evident that all members contributed to the problem-solving process? How professional is the presentation of the solution? (DevPost) Was the team used appropriately?
10% | How well is the code documented and written? Is the code architecture explained and were the benefits and principles of the team's design noted? Was the code programmed in a systematic method?
Code Scalability and Maintainability
10% | Did the team consider scalability and maintainability properly with the project? How was this implemented and was it properly demonstrated? Did the team flow industry-level coding architecture to facilitate future use?