- We’ll start with a warm up round for 15 minutes to let teams coordinate and learn a bit about tonight’s secret ingredient.
- We’ll then enter Stage 1 for 60 minutes, where teams can start on the most important features for tonight’s hackathon.
- At the end of Stage 1, we’ll make an announcement about Stage 2’s secret ingredient and turn you loose.
- Teams can continue work on Stage 1 throughout Stage 2, as it’s weighted higher on the grading.
- A working POC with both stages is a tall order but will be heavily favored.
- We’ll do demos and judging. All code must be PR’d to the team’s open source Repository on GitHub at the time of judgement – because sharing is caring.
We’re going to work with Twilio tonight, so go get free credit by doing the Twilio Quest Getting Started and earning $20. It’s super quick and easy, and you’ll be able to use the free credit to win cash tonight.
We’ll also provide $25 AWS credit, so you can open an account there as needed. You might end up needing it, especially for Stage 2, so now would be a good time to register a fresh account (if you don’t want to muddy up your personal one)
The “secret ingredient” for tonight is Twilio Flex. The first challenge is fairly open ended: build a Twilio Support Center integrating Flex with anything else you deem interesting / exciting / what-have-you. This could include things like:
- Your own system’s custom metrics or logic
- Ops tools ( VictorOps, OpsGenie, CloudWatch, etc )
- Monitoring Tools ( Sentry.io, Grafana, etc )
It’s always going to be subjective. That being said, tonight’s judges will be looking at how creative, integrated, and extensible solutions will be. Projects will be demo’d from your machine, with breadth of interesting possibilities trumping bullet proof solutions. Bugs and hard coded place holders are fairly novice, assuming it’s not all just smoke and mirrors.
Good goals to shoot for include:
- Carving out reusable pieces that others can share & learn from
- Being able to clone & start your project easily
- Fairly self-documented code that can be grok’d by someone of decent familiarity
Our timing was off on how long the Twilio trial would take, and given that both teams had some polish to finish out, we're going to let the PRs roll in and decide a winner next time!