Stuff to do:
- Lots of clean up, I'm rusty and not making the best structural decisions ATM
- Add "roster" entity -- so users can create rosters and have quick access to their players
- This would be best served by having users/auth
- distinguish between split seasons/full seasons on player index
- Supplement player database with additional/external data (e.g. Games Played!)
- currently Batters and pitchers are completely separate entities -- find way to share better, e.g. have Player object they each inherit from