@matsos/expected-wins/General Information.md

A simple javascript library based on a formula developed by baseball statistician Bill James. It attempts to determine the number of games a team should have won, by comparing the total number of runs a team has scored to the number of runs it has allowed

# CareerHack Format

## Who this Hackathon is for:

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.

## Prize

See [Readme](./Readme.md#prize)

## Schedule & Channels:

Links:

* [Twitch](https://www.twitch.tv/mintbeancareerhack)
* [Slack](https://join.slack.com/t/mintbeanhackathons/shared_invite/zt-cyxqi3jo-dXg1sw3RcZ07andai~Bhww)
* [Github](https://github.com/MintbeanHackathons)

| 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) Hireside Chat with Guest, OR Q&A with Monarch |

## Your responsibilities as a participant

1. You must be logged onto Slack at all times during the Hackathon.
1. You must let us know, on Slack, when you've started.
1. You must let us know, on Slack, when you've finished coding.
1. You must let us know, on Slack, when you've finished code review.

## Getting started.

Steps to get started:
1. Fork this repo.
1. Write code.
1. Push.

## Submitting your code

When done:

1. create a pull request against the original repo's `master`. This is your end product. [Here are some examples](https://github.com/MintbeanHackathons/ResumeBuilder/pulls).
1. Make sure you have finished the requirements in the `How to get points for Aesthetic Appeal` section.

## Scoring

* 33% Code Quality
* 33% Aesthetic Appeal
* 33% Code Review

## How to get points for Code Quality

1. Write code that is bug-free
1. Write code that other people can easily understand
1. Write code that other people can change without breaking things
1. Write code that is in-line with current best practices

## How to get points for Aesthetic Appeal

The best way to get points for aesthetic appeal is to deploy your project to a server.

Suggested methods:

* Codepen
* Repl.it
* Heroku
* Github Pages

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.

## How to get points for Code Review

Code review means leaving constructive comments on other people's code.

Code review is assessed based on things like:
1. Valid points about the author's architecture.
1. Constructive criticism on the author's code quality.
1. Pointing out logical errors in the author's code (but being nice about it).
1. Suggestions for better ways to do things.
1. Last but not least: common courtesy and being nice. Don't be a jerk.

No points are awarded for things like:
1. Nitpicks on non-functional aspects like syntax, indentation, etc.
1. Positive comments like "Awesome!" or "Great job!" or "I like this!"
1. Harrassing, abusive or sarcastic comments (these could disqualify you and possibly get you banned)
1. Other obviously low-value comments