Schedule

  • Registration, Meet and Greet, and Coffee

  • Welcome, Introductions, and Pitch

  • Design and Code

  • Lunch

  • More Design and Code

  • Presentation, Judging and Awards

Sponsors

Prizes

TBA

Judges

  • TBA

Come join us, March 25!

Love creating stuff on your computer and LOVE baseball? Come hack with us on March 25 at General Assembly Boston, 125 Summer St (13th Floor), Boston, MA 02110!

The fifth annual Baseball Hack Day is a fun, friendly one-day hacking competition (also known as hackathon, hackfest or codefest) for baseball fans.

It is the day where area baseball minds come together and see what cool projects can be created within a limited time. The project could be (but is not limited to) a tool, app, website, or data visualization. Baseball Hack Day is a free event thanks to our generous sponsors. The event is based on the principal of the Hack Day Manifesto.

New to hack days? Have no fear. See to get an idea. See our resources in github wiki, check out our inspiraton blog on tumblr, and follow us on Twitter @BaseballHackDay

Registration will open soon.

Guidelines & Rules

First and foremost, this event will be a success if everyone has a good time. That is why we have a Code of Conduct. All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with it. TLDR; Basically, please don't do anything that would detract from the fairness or fun of the event. Respect your fellow hackers.

We are using a hack submission service called DevPost. In order to win, you need to submit the hacks through it. It helps organizers keep track of the teams and the projects they create.

Hacks could be (but are not limited to) a tool, application, software, website, or data visualization and may be built using any programming language and platform that you choose. Teams can be of any size, but awards are only given to up to four individuals. Hacks will be judged for 1) Creativity/Originality, 2) Design/Presentation, and 3) Execution/Functionality.

The majority of your coding must happen during the event. Some work done prior to the event is allowed, but it should be disclosed at your demo. Ideas that are compact and executable in one-day format are encouraged, and we will reward teams that recognize this time constraint.

When time is up, you will have short show-and-tell and demo time (3 to 5 minutes, depending on how many projects there are). Judges also will come around during the event and you are encouraged to tell them about your projects at that time.

Prototypes/mockups for demo are OK, but working websites or mobile apps are strongly encouraged.