24344

I would like to paraphrase an issue from our issue tracking system:

Them: There was a problem with your shit over the weekend. Our stuff is inexplicably wrong and we did not change anything to affect it. We believe this is your fault. 
Us: Actually, everything looks to be ok. Can we get some additional information to help figure out what happened? 
Them: Bull-honkey! If nothing is wrong with your shit, why is our shit wrong? We didn't change anything! Plus, we check our stuff all the time wrong and it started this weekend. Here is a pile of information you have never seen before in no particular order, please sift through it and fix the problem. 
Them: Fixing this is urgent to us, hop to it. 
Them: Our group found the wrongness of our stuff is isolated to a small sub-section of data. Here it is. We did not change anything, so have you figure out why your shit broke yet?
Us: Are you sure nothing changed? We double checked, but both our stuff and your stuff looks like it is actually correct. Here is how we checked. Could you let me know how you checked? We don't know how you are arriving at the conclusion that something is wrong, that is why we asked for your help initially.  
Them: Nothing changed.
Them: Here is the information on why we believe something is wrong. 
Them: It turns out we did make a change this weekend. We will back out the change. 
Us: So everything is ok. 
Them: Everything is fixed now. 

Now, while I did paraphrase the issue, I did not change out the number of times they blamed us.

How is this teamwork? Why would anyone want to work with them?


Comments

Post a Comment

Popular posts from this blog

Integrated Windows Authentication with Chrome and Firefox

Image
A few days ago, the Powers That Be at my institution rolled out a change to our web authentication scheme. Previously, we were using a proprietary system that somehow played nice with Active Directory. The changed made Active Directory Federation Services play nice with our proprietary system - making ADFS do the real work. Now, we live in the world of Integrated Windows Authentication. I'm all for that, mainly because the proprietary system was a PITA in a lot of cases. This new change makes a lot of thing easier. Plus, now logging onto your workstation logs you into our webapps! Well, not for me. I use a Chrome and Firefox. Well, not yet anyway .... It works great for Safari users on a Mac. However, I use Chrome mostly and Firefox for development testing.  How on earth do I tell Chrome what servers are okay to do Microsoft Integrated Login with? I guessed there was a way to configure Chrome and Firefox to do this, and it turns out there is! However...
Read more

Planned System Downtime

I have some thoughts on planned downtime. Ultimately it boils down to this: is the planned downtime caused by urgent, impending, and guaranteed doom? If yes, then by all means have the downtime whenever you can. If not, affected as few customers as possible, by the numbers. Planned system downtime should minimize impact to system usage - period. By "System Usage" I mean real customers using the system. I recently had a discussion with the systems group about a necessary outage on a system I support. Something important, but not urgent had the possibility to cause downtime on the system. However, if something went wrong and we had to restart a server, the server might not come up. This was deemed as needing pretty serious attention (which I agreed with). They found a fix and wanted to put it into production, as an emergency, planned downtime. We had a downtime window coming up, but this should probably happen before the window. They suggested an evening. Google Anal...
Read more

Error Handling

Image
I found this actual error message today while working with a vendor application: Okay, it wasn't that exact error message. And that's my code. BUT, the first part is verbatim. This is a server-side, vendor-provided, and above all, released product. This is not a beta; we paid someone to give us that error message. What am I supposed to do with that message. My code called your code and it told me "Unable to get resources." Guess I'll just take a nap till those resources can be gotten. Over the years I have seen both vendor applications and custom code where programmers are throwing away valuable information by not properly sending errors up the stack.   You should always, always, ALWAYS send your errors up the stack! * The error above could easily have been something like this: See, now I know something! This is a java.lang.NullPointerException exception in the file MeaningfulError.java - on line 11. That's an informativ...
Read more