Quote:
Originally Posted by BrianL99
135,000 Village ID's + Guests. 57 Courses. Approximately 100 different starting holes. Somewhere around 5000? available Tee openings. Most requests, involving various "course/time preferences" and various numbers of players, with varying priority.
Seems like a lot more than 4 variables to me.
|
Most public or semi-private courses have potentially unlimited guests. There's 25 million golfers in the US.
There's only a few variables in deciding YES/NO in whether a booking is fulfilled and that's basically what the points sytem is used for. The points system is their way of providing visibility to their algorithm, which is actually a good thing. The total number of other holes or available bookings on other holes that the person making the request is not a relevant variable. For example if you request to book Mangrove, it's not relevant what other people have booked at other courses on that day. You're just going to be assigned the first available in your preferred timeslot where your point value "wins". Extremely basic algorithm.
I'm done debating an IT problem with someone that doesn't understand basic complexity in the Villages golf reservation system compared to a modern typical application like a travel booking system that is reasonably complex, I've implemented a few.