Encryption
http://trenchescomic.com/comic/post/encryption
Knowledge is dangerous
AnonymousI did QA for a summer job one year for an independent testing firm. This was exceedingly different from doing it in a studio as far as I understood. There’s all the hard work and crunch-time and none of the light-hearted atmosphere during the better times. The schedule was fairly grueling but we were all gamers and with grim determination we kept going at it just for 10 bucks an hour and for making our industry better.
At least that was my thought until I worked on a reasonably big project. A licensed RTS. We were put on this project with only 30 bugs logged by the devteam. By the time it was over we logged several thousand, ranging from game-crashers to spelling errors. But my favorite one took the cake. If you pressed B it would instantly crash the game to the desktop.
Now that was interesting, I filed the bug, told my testing lead… But then I did a bit of digging in their files. I found out that the company had been cribbing their engine from another popular RTS from a few years before. Namely Warcraft 3. Pressing B would try to call up part of the engine code to open a building menu. This particular game didn’t have a building menu and so the engine would divide-by-zero and crash.
I added an addendum to my bug report saying “Bug most likely tied to engine issues”. Innocent enough, helpful even. But it showed them I knew too much. The next week we recieved a notice from the publisher that they cancelled our contract.
Ah well, knowledge is a dangerous thing.
Posts
I don't think so, none of the initials line up.
Nusquam Findi Factionis
My Digital Pin Lanyard
Nusquam Findi Factionis
My Digital Pin Lanyard
Exactly. What if the developer saw thousands of bugs, decided that in its current state, it didn't warrant tens of thousands of dollars a month in testing, and they should just finish the damn game first? Or maybe the rest of the thousands of bugs were of low quality, and the devs were getting overwhelmed in duplicates? So many possibilities.
Dude tells a story about how his entire team was fired after he let on that he'd figured out they were cribbing the warcraft III engine, and folks still manage to find a way to side with the employer. It's possible there was, coincidentally, an alternate explanation for why they decided to sack the QA team, but I'm not inclined to put too much weight on the diligence of guys whose game crashes whenever someone presses the "B" key.
If I were onto speculation, I would say a certain early DOTA game comes to mind.
I = Isaac. 'I' is his spy acronym. Pretty clever, really...anyone intercepting the message is going to assume 'I' must be somebody whose name does not start with I, (Cf. The Cheat's birthday) hence removing him from suspicion. At least, it worked for me.
It's extremely bad pay for someone with a college degree (which is often required for QA work.)
I make a lot less now as a tester about to start year 4 than I did day 1 as an administrative assistant at a construction firm in a poorer area.