Tracking Twitch will allow users to track their channels and get valuable instights. It will also provide an overview of the most popular channels / games / streamers over time.
This way Twitch streamers will be able to optimize their streaming to best suit their viewers.
###Rails
- Fabrication Gem for object generation
- RSpec for testing?
- Capybara for UI Testing
- HAML should replace embedded Ruby as the templating language of choice
- Continuous async Api Querying will probably be done using Sidekiq
- Devise for user authentication
- Pundit for authentication if need be
###DB
- DB will be MongoDB for relatively young data
- MySQL data warehouse to keep older data stored
###Frontend
- Visualization might be done using HighCharts. But that depends on the licensing...
- Thin controllers, thin models, reusable layers in between.
- Keep routes clean! If I look at a route, I instantly want to know what's going on!
- Use use_case classes and helper methods with expressive names to keep a route slim.
- DRY out your shit!
- Single responsibility works for methods as well!
- When you got single responsibility methods, you can toss your comments by just giving everything expressive names!