I want to go home!

[naruki_oni]

Due to poor testing, the bugs in my project are not being detected until the sales guy takes it to the customer. BAD SALES GUY!

I told him this thing would be chock full o bugs given the nature of this change. I told him that it would have to be tested thoroughly before going out the door. And I told him I could only double-check my own work so much, but I don't really know how to use the product (and I can't read any of the comments or screens).

And he doesn't spend much time at all testing until the last minute. Guess what? Bugs Galore! What a surprise.

So here I am at 5:30AM, hopefully seeing enough bugs squashed to allow me to catch the first train home. And Monday is another holiday, so I'll get a nice long weekend.

Basically, I just have to clear up any bugs he could find, and I'll fix the rest once the customer discovers them. BAD DEVELOPER!

Comments

[blackbyrd2.livejournal.com]

It makes my job seem so much better when I hear about yours.


Hope you have a great weekend though!

I got home at 7:30AM.

[naruki-oni.livejournal.com]

Grr.

Sales guy

[framstag.livejournal.com]

Your sales guy is either a former Microsoft guy, or Microsoft is his ideal. "Bring the product to the customer, they'll do the testing."

I know this problem. The developer doesn't know enough about the entire system, so he can test only his changes. It's up to the QA to do the testing. Developers are usually bad testers.

Oh - wow.....

[saminz.livejournal.com]

What you guys go through makes us normal folks cringe in shame for ever bitching about work.

Still. From a user point of view, you writing a "product" without even knowing how it will be used makes it quite transparent why quite some "product" we get handed makes us go "ç&%%&)G!!!?!" so frequently :-D.