Beat them 17 out of 18 innings for sure. 1 inning got us. Hope this is the spark we need
Beat them 17 out of 18 innings for sure. 1 inning got us. Hope this is the spark we need
Great win! Really good to see the bats waking up. Still waiting to see this team hit a Friday or Saturday arm.
Has anyone ever tried calling into Jay’s show to politely let him know that his text message alert can be heard on the air? I have emailed him about it with no response.
I would also like to hear his comments about the 3+ year issue with post game interviews that has yet to be addressed. When it happened last night he said “I can assure you that will be corrected for tomorrow night’s game.” Then it happened again.
Does it embarrass Jay that he is part of this clown show that continues to fail to complete a simple post game interview?
Is he aware that KPEL is the ONLY Station in D1 baseball to have this many issues for such an extended period of time?
If he was a listener to a station that continued to fail at such a high rate for so many years would he be frustrated or just accept that “it’s nobody’s fault?
Yep - even with a losing record RPI is 81. IF they could string some wins together, this team could easily get into at-large consideration with RPI in the 30-40's... But, they gotta string together some wins and have yet to prove they can do that - even against inferior competition.
A sweep this weekend would be a great start. But, lets win the Friday game first...
We are getting the engineer to look at all of the equipment today and hopefully he can figure out what’s going on and why some equipment like the broadcast equipment works while the postgame equipment doesn’t, but for your next to last question. The Cajuns are one of the few baseball teams that has had every game on the radio even if it’s on a different station because of scheduling conflicts the last several years and softball as well. I’m hoping that when the engineer looks at it we can get it fixed and make it better.
Time for a "root cause analysis". Would highly suggest you get everyone involved together and have them walk through the whole process and just observe. Often times something like this ends up being human error. You can ask someone a 100 times to tell you exactly how they are doing something and won't figure out the problem until you observe them doing it because they left out some detail they didn't think was important but ultimately proved to be the cause of the problem.
Example: Had a client with a software issue on an industrial control system. Engineers are troubleshooting this over the phone half way around the world for two full days. Walking the client through it time and time again. Finally one of the engineers picks up on something the client said. He had moved a folder from one location on the computer to his "desktop" so that it would be easier and quicker to get to it. He did not realize the location of the folder was critical and never told the engineers he had moved the folder. Thirty seconds later the problem was solved.
There are currently 2 users browsing this thread. (0 members and 2 guests)