Tuesday He ccs me on the tail end of an E-Mail chain, the bit where he volunteers me to start programming some ill-defined event-driven horseshirt fired up by a piece of software everyone hates. I point out that the script to be run from the time-based scheduler is simple and moreover, done, although I haven't actually been asked by the aforementioned boss to do the job, that I have no wish to become entwined in the ongoing trainwreck of the software he wants me to start looking at and perhaps I'll just hand off he script to the user department and let them worry the details.
Wednesday another e-mail claiming that whhat is equired is much more complex than a simple script. We do the pantomime "Oh yes/no it is/isn't" thing for a bit. He tells me that he wants a different filesystem cleaning than the one he asked for, and that since it is part of a system I help manage I should just do it.
I refer him to the original mail, point out that the filesystem he's now talking about *is* auto-managed by the software and that the filesystem that keeps filling up with crap and that the users cannot keep down to a managable size is external to our software, was set up by the user for some arcane purpose that even they don't really understand or have any sort of plan for and that's what I was asked to fix and what I have actually, indeed, fixed.
I tell him if he really wants to do what he's asking for today (as opposed to what he wanted on Monday) that the lead time will likely be months and moreover I'll need a proper requirements document stating definitively what needs doing to what for which reason. However, if he really needs his disk to stop overflowing because Irving cannot clean up the crap his team creates, I have a script to do that which has been running in emulation since Monday and even incorporates a bullshirt mail requirement that was snuck in Tuesday.
I'm out tomorrow so a doctor can electrocute me in the name of science. I wonder what Friday will bring?