This README would normally document whatever steps are necessary to get the application up and running.
-
Player registers.
-
Player fills out initial survey on their current game levels.
-
Player must fill out opponent survey ONE ONLY per match-week.
notes: the survey informs the profile
*can d/l relevant events from USTA.api
*A todo module
*Journal your matches.
*game plan laboratory
*Tournament Tough items
-
Ruby version 2.4.2
-
System dependencies Rails
-
Configuration
-
Database creation SQLite3 Player model has_a profile;
identify another player-instance as an "Opponent" object;
the two profiles compile to deliver a game plan for that weekend/evening/dayoff.
(has-a Opponent :through: :profile?)
What's a profile? Player User inputs changes to values for strokes and competitive attitude via spinners incrementing the assigned integer.
Real change happens slowly
Player User could have say a 5 forehand at start of season, to make it a reliable 8 forehand during championships, would increment slowly the real change.
The goal is to win matches by making the other guy lose, as much as it looks like art, it really is boring and repetitive. Champions can be very boring and self-serving. Thoughtful practice of good habits; breaking old habits over time.
Think about finding ways to get this Opponent to give me the game.
Much more effective than stroke honing.
Stamina is what the pros use to separate the ladies from the girls.
-
Database initialization
-
How to run the test suite
-
Services (job queues, cache servers, search engines, etc.)
-
Deployment instructions https://devcenter.heroku.com/articles/preparing-a-codebase-for-heroku-deployment
-
...