Reminds me of a time when "the team" was asked to stay up late to help with a server upgrade. The upgrade was a wide-awake nightmare! The "admin" decided to upgrade all the software on the production server to the current version; this included major version changes on the OS, database, Apache, Perl, you name it. Perl alone went from 5.00503 to 5.8.3! Of course nothing worked, and everything on the site had to be retested and debugged that evening, er, morning. We're still finding broken site elements to this day.

I worked my usual 9-5, went home and had dinner, then worked from 7-10:30 and went to bed exhausted. I come in early the next day to find (surprise!) that I'm the only developer there. All those "team players" took the morning off! Customer service, marketing, and suits are asking me "WTF happened?"--not a single message had been forwarded to them to let them know what was working, what was borken, anything at all. I try to reproduce from sporadic late night email exchanges what is working and what is not.

That afternoon, PHB gives me a hard time for not burning the midnight oil; looks like I'm "not a team player". Meh, I stopped caring long ago. Oddly enough, the rest of "the team" thought I did the right thing once I explained it to them. And as long as the ladies in customer service still like me, I'm OK. :-)

---

---

• 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.