Comments on: Bad Job Experiences, Number 1 in a Series http://blog.xcski.com/2004/03/31/bad-job-experiences-number-1-in-a-series Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place. Fri, 16 May 2008 12:06:00 +0000 http://wordpress.org/?v=2.5.1 By: J. http://blog.xcski.com/2004/03/31/bad-job-experiences-number-1-in-a-series#comment-161 J. Wed, 31 Dec 1969 19:00:00 +0000 http://xcski.com/wordpress/?p=159#comment-161 That's the first set of comments on Slashdot that I've enjoyed in quite a while. Anderson sounds like hell. That’s the first set of comments on Slashdot that I’ve enjoyed in quite a while.

Anderson sounds like hell.

]]> By: Drakes http://blog.xcski.com/2004/03/31/bad-job-experiences-number-1-in-a-series#comment-162 Drakes Wed, 31 Dec 1969 19:00:00 +0000 http://xcski.com/wordpress/?p=159#comment-162 I work for people that freak out for minor things. I've worked on some big sites.. back end integration etc.. Setup web and app servers.. database tables etc.. I just love it when account folks chastise you for things like: 1. Missing a period on line 4 of the third page. Thanks, you've got your transactional site up and running and you are bugging me about missing a period on what page? 2. A word on a particular page on the site was supposed to be italicized. Keep in mind we were given the "content" from the "account folks" (who are supposed to be providing final copy). Wow .. our team got reprimanded here. 3. Saying that something was going to take approx. 2 hours. Then getting yelled at for taking an hour but telling them it would take 2. This one made all of the team laugh. We got yelled at for finishing early. The client still paid full.. but since my "quote" was so dramatically off, it must of screwed up their books etc. Yep, I guess I should be more to the minute when I quote. 4. One of the QA folks was clicking on an incorrect URL and reporting to us that there was a problem with the page. When someone told the QA person that they were looking at the incorrect URL, the QA staffer didn't like the "tone" of the person and probably filed a complaint. Forget the fact that the QA person had a couple people checking their code, the server setup etc.. because the QA person kept reporting a problem while looking at an incorrect URL. If the complaint was filed, some guy on the tech team who wrote a simple, non-toned email explaining that the QA person was looking at the wrong URL will be reprimanded for his "tone". I should mention they actually solved the problem after QA person clicked on the correct URL. .. There are to many to list... Biz people and IT people have a difficult task.. Because Biz folks don't truly understand what it takes to build any system, and everytime an IT person tries to explain it, the result is usually "that IT person has an attitude". A few months later that IT person will be replaced with a "yes" person for another few months until they get a better gig. Our market is really messed up. Cheers.. /D I work for people that freak out for minor things. I’ve worked on some big sites.. back end integration etc.. Setup web and app servers.. database tables etc..

I just love it when account folks chastise you for things like:

1. Missing a period on line 4 of the third page. Thanks, you’ve got your transactional site up and running and you are bugging me about missing a period on what page?

2. A word on a particular page on the site was supposed to be italicized. Keep in mind we were given the “content” from the “account folks” (who are supposed to be providing final copy). Wow .. our team got reprimanded here.

3. Saying that something was going to take approx. 2 hours. Then getting yelled at for taking an hour but telling them it would take 2. This one made all of the team laugh. We got yelled at for finishing early. The client still paid full.. but since my “quote” was so dramatically off, it must of screwed up their books etc. Yep, I guess I should be more to the minute when I quote.

4. One of the QA folks was clicking on an incorrect URL and reporting to us that there was a problem with the page. When someone told the QA person that they were looking at the incorrect URL, the QA staffer didn’t like the “tone” of the person and probably filed a complaint. Forget the fact that the QA person had a couple people checking their code, the server setup etc.. because the QA person kept reporting a problem while looking at an incorrect URL. If the complaint was filed, some guy on the tech team who wrote a simple, non-toned email explaining that the QA person was looking at the wrong URL will be reprimanded for his “tone”. I should mention they actually solved the problem after QA person clicked on the correct URL.

.. There are to many to list…

Biz people and IT people have a difficult task.. Because Biz folks don’t truly understand what it takes to build any system, and everytime an IT person tries to explain it, the result is usually “that IT person has an attitude”. A few months later that IT person will be replaced with a “yes” person for another few months until they get a better gig.

Our market is really messed up.

Cheers..

/D

]]>