This hackathon is for developers of all levels who have some experience with HTML, CSS, and JavaScript. If you're a senior developer, this Hackathon provides great mentorship opportunities that can be rewarding for you, as well.
See Readme
Links:
Saturday, March 21, 2020
Start | End | Description |
---|---|---|
12:00pm | 12:30pm | (Optional) Orientation for newcomers and people who need a refresh |
12:30pm | 12:45pm | Introduction, problem set briefing, and initial Q&A |
12:45pm | 3:00pm | Part 1 - Programming (Solo, heads-down) |
3:00pm | 3:30pm | Code Review how-to instructions |
3:30pm | 4:00pm | Part 2 - Code Review (in groups) |
4:00pm | 4:30pm | (Optional) Q&A w/ Monarch |
- You must be logged onto Slack at all times during the Hackathon.
- You must let us know, on Slack, when you've started.
- You must let us know, on Slack, when you've finished coding.
- You must let us know, on Slack, when you've finished code review.
Steps to get started:
- Fork this repo.
- Write code.
- Push.
When done:
- create a pull request against the original repo's
master
. This is your end product. Here are some examples. - Make sure you have finished the requirements in the
How to get points for Aesthetic Appeal
section.
- 33% Code Quality
- 33% Aesthetic Appeal
- 33% Code Review
- Write code that is bug-free
- Write code that other people can easily understand
- Write code that other people can change without breaking things
- Write code that is in-line with current best practices
The best way to get points for aesthetic appeal is to deploy your project to a server.
Suggested methods:
-
Codepen is a great spot for frontend code. You can even add libraries like React and Vue via CDN imports using the menu. Make sure you "Save" your project and leave a link in your project's README.
-
Repl.it is a great way to deploy backend code for an example project, including a full-stack Express application.
If the above are not options for you, you can capture your screen and attach a video with your final push. (including with your cellphone camera, no big deal).
As a last resort, screenshots uploaded in your final push will do.
Code review means leaving constructive comments on other people's code.
Code review is assessed based on things like:
- Valid points about the author's architecture.
- Constructive criticism on the author's code quality.
- Pointing out logical errors in the author's code (but being nice about it).
- Suggestions for better ways to do things.
- Last but not least: common courtesy and being nice. Don't be a jerk.
No points are awarded for things like:
- Nitpicks on non-functional aspects like syntax, indentation, etc.
- Positive comments like "Awesome!" or "Great job!" or "I like this!"
- Harrassing, abusive or sarcastic comments (these could disqualify you and possibly get you banned)
- Other obviously low-value comments