Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Working as a pogrammer

Name: Anonymous 2010-02-21 16:59

I need to rant and I've got no other outlet, so here it goes.

At work, there is a QA lady who only has her position because she is married to one of the managers. She has NO FUCKING CLUE what she is doing and it pisses me the fuck off.

First off, I work for a software company. This lady has absolutely NO software background other than probably using Microsoft Word, but somehow she thinks she's more qualified to make QA decisions than other people because her husband gave her that position. She keeps insisting that "Oh every time we make a change we need to test EVERYTHING! You know those programmers, they might make a change and not realize that it affects something else. They only test the things they think it affect. We should test everything before we send the patch out!"

Now, we write custom software for a lot of customers. We update the software constantly. Probably at least once a week. This is completely different than writing say, a video game, where you spend years on a project and have one release; maybe two if you fuck up real bad.

No, we do not need to test every single feature any time we make a change, because this would take forever and chances are in most cases it has nothing to do with the change we made. With every possible configuration of OS, Server OS, networking software, hardware, firewall, backend database version, etc, etc etc, along with all the features we offer in the software, who knows how long testing all these cases would take? I can tell you by the time we were done testing them, there would have been at least 10 more changes made that would all need testing again. We would bury ourselves in needless work and never get anything done. THIS IS NOT THE SOLUTION, GOD DAMN I JUST WANT TO SLAP HER SILLY WHENEVER SHE GOES ON ABOUT THAT SHIT.

The solution is a streamlined bug tracking and response system. A highly efficient pipeline that goes from point A (bug received) to point Z (bug patched). If the customers receive a fix for the big in a timely manner they will be just as satisfied as if the bug had never happened, because they will feel like their voice is heard and important to us.

And yes, I've brought this up before  BUT NOBODY LISTENS TO ME BECAUSE I'M JUST A LOWLY PROGRAMMER. A GRUNT. WHAT WOULD I KNOW? FFUUUU SHIT IS FRUSTRATING AS ALL FUCK.

Name: Anonymous 2010-02-21 17:42

>>5
By asking for each value separately. For example, first ask for the month in MM format. Then, if the input is >12, we know the user fucked up!

______
If you believe in Anus Haxing and are 100% proud of it put this as your signature.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List