Frustrating

Today has been one of those days.  You know. The days you wish would just end.  I have been in a bad mood all day.  Hard to believe I know.  But I have.  It hasn't helped that I keep having to deal with stupid people and people that do stupid things when they know better. It just makes for a bad day.  It really doesn't help when people here at work do things that make my life even harder.  For example, we have a new credit union using our shared branching software.  They just started using it Monday.  Well, there was a new screen that was pushed out to them that was just finished like the night before. I have received zero training on this new screen.  Heck, I hadn't even seen it.  So I get a call at 5:00 from a teller at this credit union that is trying to close her teller drawer.  Well she goes to this new teller balancing screen and clicks on the close button. She gets a message saying that she can't close the drawer because it hasn't been balanced yet.  Now keep in mind that this teller has had more training on this screen than I have.  So here I am trying to figure out how to get this screen to let her balance her drawer so she can close it and go home.  Well, after about 15 minutes I finally figure it out.  So I help her balance her drawer and then she hits the close button.  It pops up the confirmation screen and she hits close again.  Does the drawer close?  Of course not.  It pops up with an error message saying there is a problem. So we can't close her teller drawer.  What is really frustrating about it is now I look like a complete moron because I didn't know how the screen functioned. On top of it the screen didn't even work.  That is a great way to show our newest customer how great our software is.  NOT!!!  See what happens when you try to rush things.  In the programming world rushing something new out the door without proper testing is a bad idea.  And this is why.  Oh well.  I'm sure I will get some crap from the guy who wrote the screen because I must have done something "wrong" to cause the problem in the first place.  But see.  How the heck am I supposed to be able to offer any kind of support on a product I have never seen?  I am good at figuring out software in a hurry.  Give me enough time with a program and I will figure out how it works no matter how complex it is.  But when you have a customer on the phone with you it is generally not a good idea to not know how the stuff they are calling about works.  Which in turn makes me look bad and incompetent.  I have pointed that fact out about a dozen times now in staff meetings.  And they recognized the need for making sure we were properly trained before they release new stuff.  They followed it well with the last module they released.  But I guess this one guy is above that.  He doesn't think we need training on his stuff because it is so self explanatory.  And yet, even when someone has had training on it they don't know how to use it because it is anything but self explanatory.  So I guess you could say that my suggestions about training the support staff on new stuff before it is released has been thrown out the window.  We are back to the old ways of doing things.  Good thing our support staff is good at what we do or we would probably lose customers because of stuff like this.