I want to thank everyone for their responses. What really strikes me about the whole endeavor is it never once occurred to me to quit. Well, it did, once. But it should have occurred to me long before I bothered any of you with this insanity.

So, thank you for the help. When I did provide his properly formatted TPS reports, I was given Yet Another Requirement. He couldn't possibly be a perl hacker; rather I think he was just trying to push limits of what can be generated automatically in less time than it would take to do manually – which was his goal all along.

Sad, that. My own personal advice would be, if you find yourself in a position where your supervisor finds more and more complicated ways for your to waste your time on his behalf, to just leave. If you're of the skill level that you can write tools to automate your mundane responsibilities, you won't be looking for long, and the supervisor in question is obviously one of those pieces of human effluvia floating about the toilet bowl that is the workplace.

brother dep

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.