From TFA:...“one would need to consume a caffeine equivalent of about 50 cups per day, almost close to a lethal dose”, she says. “Exercising is far easier if you ask me.”
Clearly, she doesn't know about the secret Mountain Dew IV that hackers use whilst lurking in their parents' basements...
Wow. Sounds like some test engineers out there with sucky jobs.
My last job was as a development engineer. We tested our own code while in development, then turned it over (along with any relevant and useful test cases) to the QA team.
I recently took a position as a Software Test Engineer at a different company. Our philosophy here is that we own the quality of the product. Granted, it takes a little more creativity to write tests to break an OS than an application, but my job here is quite challenging, with very little of the "run script, make checkmark" drudgery so many others seem to endure.
To the OP: ask lots of questions about what you'll be expected to test and how. Nobody likes drudgery, and being given a certain amount of leeway and ownership makes the job much better.
It matters to the swarms of new "iPhone programmers" dealing with memory management for the first time. I've seen lots of questions on StackOverflow dealing with memory management from people migrating from other languages.
Slashdot Mirror
Quite possibly the dumbest article I've ever seen.
From TFA: ...“one would need to consume a caffeine equivalent of about 50 cups per day, almost close to a lethal dose”, she says. “Exercising is far easier if you ask me.”
Clearly, she doesn't know about the secret Mountain Dew IV that hackers use whilst lurking in their parents' basements...
Wow. Sounds like some test engineers out there with sucky jobs.
My last job was as a development engineer. We tested our own code while in development, then turned it over (along with any relevant and useful test cases) to the QA team.
I recently took a position as a Software Test Engineer at a different company. Our philosophy here is that we own the quality of the product. Granted, it takes a little more creativity to write tests to break an OS than an application, but my job here is quite challenging, with very little of the "run script, make checkmark" drudgery so many others seem to endure.
To the OP: ask lots of questions about what you'll be expected to test and how. Nobody likes drudgery, and being given a certain amount of leeway and ownership makes the job much better.
Am I the only one who thought of laying explosives, not extracting minerals, when he saw the word "mines?"
Nope.
It matters to the swarms of new "iPhone programmers" dealing with memory management for the first time. I've seen lots of questions on StackOverflow dealing with memory management from people migrating from other languages.
You think Congress will help? Who do you think passed the DMCA in the first place? Fairies?
yup...