The Bucknuts' mission is to be the official source for [Major League Baseball] in Northeast Ohio. They create the most daily written articles and offer the largest database of professional and collegiate baseball related content, exclusively written by Northeast Ohio's top journalists.


I found this app at the beginning of the golf season. It has saved me money overall, as the "Hot Deals" are hard to beat. I've paid as little as $14 to as much as $54 for a hot deal, depending on how long I hold out to book my round. I, like many, share the frustration of having to book 3 days out to use your "Bonus". Sometimes I don't know if I'll be able to play until the day before, and by then it's too late to use it. I understand GolfNow wants to make as much money on the tee time as they can, but you are also making money from the course that uses the system. I only have 3 courses in my area that use it, one of them being my "Home" course, so for that I am lucky. (Source:

This weekend I had a tee time registered at a local golf course at 830 am…. Are area was hit by very bad storms the night before over 5 inches of rain in 30 hours governor actually issued a state of emergency for the day freeways were flooded higher then car roofs. I proceeded to wake up at 730 am and call the course and received no answer. I assumed with all the rain and no answer course was obviously closed. At some point the course opened that day and told Golfnow to bill me for a no show or cancellation. I’m an avid golfer never once missed a tee time or forgot to cancel a tee time it’s the respectful thing to do. But no answer at course and 5 inches of rain I thought seemed obvious. Needless to say I contacted customer service talked to employee who said the course said charge was valid and could do nothing about it. I asked to speak to a manager after about 20 minutes on hold they came back and said he would call within 24 hours it’s going on about 4 days. No attempt at calling me back at all. (Source: apps.apple.com)


GolfNow's dev team ran an "internal, low-key" proof of concept and were won over. "We really liked how easy it was to be able to pass containers around to each other and have them up and running in no time, exactly the way it was running on my machine," says Sheriff. "Because that is always the biggest gripe that Ops has with developers, right? 'It worked on my machine!' But then we started getting to the point of, 'How do we make sure that these things stay up and running?'" (Source:

At the time there was nothing in the community to help them get Kafka and MongoDB clusters running within a Kubernetes and Docker environment, so Sheriff and Josh figured it out on their own, taking a full month to get it right. "Everything started rolling from there," Sheriff says. "We were able to get all our applications connected, and we finished our side of the proof of concept a month in advance. My VP was like, 'Alright, it's over. Kubernetes wins.'" (Source: kubernetes.io)


Related Articles