The only devices that can't upgrade to it are the iPhone 3GS and below, the equivalent iPod touch, and the first generation iPad. There aren't many people using these devices any more.
I recently saw an iOS app update that listed a bug fix for the first generation iPad. O_o
I was a tester for three years. When I became a lead tester for three years, I went back to school to learn computer programming and get my technicial certifications. Since I didn't want to become an associate producer and relocate to New York City from Silicon Valley, I had to make a career change to avoid being in dead end job. After being at the same company for six years, I was ready to leave.
During my six years as a video game tester, I did nothing but black box (manual) testing. None of the 50+ video games I worked on supported any kind of testing automation. That was ten years ago. But I doubt that has changed since none of job listings I looked at since has ever required white box (scriptable) testing for gameplay automation.
Microsoft can afford to do that can of physical automation of their consoles. Developers cannot and must rely upon human testers to push the buttons, observe the gameplay, and bug problems that automation can't catch (i.e., character is naked, item inventory incorrect, black screen, etc.).
As a lead tester with responsibility for ten titles over three years, I had more than my fair share of arguments with programmers, developers and producers over bugs in the final weeks towards code release. Two things were consistent: my estimated code release schedule was always correct (+/- two weeks), which meant that everyone else kissed their bonuses goodbye (testers don't get bonuses), and the first party (Microsoft/Nintendo/Sony) always flagged the bugs that I designated as must fixed.
vanished - having passed out of existence; "vanished civilizations"; nonexistent - not having existence or being or actuality; "chimeras are nonexistent"
I'm not talking about code testing. The video game programmers I worked with were too lazy to write their unit tests for their code, much less figure out why crossing starting line in reverse causes the game to crash. Unless things have changed in the last ten years, functionality (i.e., gameplay) testing isn't automated.
When I worked as a video game tester for Accolade/Infogrames/Atari (same company, different owners, multiple identity crisis), I drove the programmers nuts on a racing title. Most video game players will play a race from beginning to end. Not an experienced video game testers. I would stopped the vehicle just before the finished line, turn around or drive in reverse, and crash the game by crossing the starting line. The programmers will complain that no one plays a racing game that way, try to wiggle out from fixing their code, and fix the bug only when its prevent them from going to code release. This is why testing automation is never used in the video game industry.
I did a stint at Cisco where I had to manually compile the numbers into a spreadsheet to have a nice graph to paste in email to manager who could flash it around to the other managers. The hardware-based reporting system wasn't yet updated to collect data from the new 11AC wireless access points I was working on.
Didn't John Carmack of ID Software vanished voxel-based engines back in the 1990's as being technically inferior -- or maybe impractical -- with the video cards of the day?
The professor at San Jose State University who gave my intro chemistry class a tour of the nuclear lab reassured us that a Three Mile Island chain reaction wasn't possible if an earthquake compromised the research reactor.
If the university has a nuclear science department, it probably has a nuclear research reactor in the basement. Although not big enough to trigger a nuclear chain reaction, they still have enough radioactive material for a dirty bomb.
I was recently unemployed for eight months, had 60+ interviews, and had three job offers on the same day towards the end. That's better than when I was unemployed for two years (2009-2010), where I had 20 interviews and filed for Chapter Seven bankruptcy before I got another job. The job market is improving.
A variation of that question is why do you prefer contracting over a permanent position?
This question always pisses me off. I didn't become a contractor by choice. I got laid off from last "permanent" position ten years ago and found nothing but contract work since then. Do I want to be contractor? Oh, hell no. I would love to have a permanent job and stay put for at least three years, which was what I did before.
The flip side side of being a contractor is that I have worked at many Fortune 500 companies in Silicon Valley. Each year I get a bigger bump as I moved from company to company. I recently ran into a old coworker from nine years, who still has the same job and makes the same amount of money. I'm making 80% more money than him because I'm a contractor.
I had a roommate who got laid off from his QA job that he had for seven years since graduating as a software engineer from college, took a six-month vacation while drawing unemployment benefits, and discovered that no one wanted to hire him since he did nothing to maintain his programming skills. Needless to say, he had a young midlife crisis. Last I heard he was still working at the local drug store.
I'm doing the clean slate approach by using only the exported database from the WordPress blog and programming the static website from scratch. In some ways I'm completing the circle. This particular blog started off as a programming project while in school in 2002, converted into a Joomla website in 2008, converted into a WordPress blog in 2011, and now into a static website. I need to remove a lot of crud that accumulated over the years.
I was playing around with vacuum tubes as a six-year-old, pulling them out of old car radios in the garage and the TV in the living room. Scared the crap out of my mother whenever she saw me poking around the back of the TV.
In other words, if you're never going to tell someone you have it, what in the FUCK is the point in obtaining it.
The classic response for any college student facing dismal job prospects during a recession is to stay in school.
I got my B.S. degree and no job lined up, I'll get my M.S. degree.
I got my M.S. degree and no job lined up, I'll get my Ph.D degree.
I got my Ph.D degree and no job lined up, I'll ask Slashdot for a miracle!
The only acceptable response is to drop out of college, join a startup, and make a few billion dollars. If you haven't done that, better hide the Ph.D degree.
Slashdot Mirror
The only devices that can't upgrade to it are the iPhone 3GS and below, the equivalent iPod touch, and the first generation iPad. There aren't many people using these devices any more.
I recently saw an iOS app update that listed a bug fix for the first generation iPad. O_o
I was a tester for three years. When I became a lead tester for three years, I went back to school to learn computer programming and get my technicial certifications. Since I didn't want to become an associate producer and relocate to New York City from Silicon Valley, I had to make a career change to avoid being in dead end job. After being at the same company for six years, I was ready to leave.
I'm sure the Gorn loved being fingered by a Vulcan.
IE
The sooner that corporate IT can abandon Internet Explorer (especially IE6), the better off everyone will be.
Unless you're playing a fighting game, button smashing doesn't count. :)
During my six years as a video game tester, I did nothing but black box (manual) testing. None of the 50+ video games I worked on supported any kind of testing automation. That was ten years ago. But I doubt that has changed since none of job listings I looked at since has ever required white box (scriptable) testing for gameplay automation.
Microsoft can afford to do that can of physical automation of their consoles. Developers cannot and must rely upon human testers to push the buttons, observe the gameplay, and bug problems that automation can't catch (i.e., character is naked, item inventory incorrect, black screen, etc.).
As a lead tester with responsibility for ten titles over three years, I had more than my fair share of arguments with programmers, developers and producers over bugs in the final weeks towards code release. Two things were consistent: my estimated code release schedule was always correct (+/- two weeks), which meant that everyone else kissed their bonuses goodbye (testers don't get bonuses), and the first party (Microsoft/Nintendo/Sony) always flagged the bugs that I designated as must fixed.
vanished - having passed out of existence; "vanished civilizations"; nonexistent - not having existence or being or actuality; "chimeras are nonexistent"
Do you speak English, motherhumper?!
I'm not talking about code testing. The video game programmers I worked with were too lazy to write their unit tests for their code, much less figure out why crossing starting line in reverse causes the game to crash. Unless things have changed in the last ten years, functionality (i.e., gameplay) testing isn't automated.
When I worked as a video game tester for Accolade/Infogrames/Atari (same company, different owners, multiple identity crisis), I drove the programmers nuts on a racing title. Most video game players will play a race from beginning to end. Not an experienced video game testers. I would stopped the vehicle just before the finished line, turn around or drive in reverse, and crash the game by crossing the starting line. The programmers will complain that no one plays a racing game that way, try to wiggle out from fixing their code, and fix the bug only when its prevent them from going to code release. This is why testing automation is never used in the video game industry.
I did a stint at Cisco where I had to manually compile the numbers into a spreadsheet to have a nice graph to paste in email to manager who could flash it around to the other managers. The hardware-based reporting system wasn't yet updated to collect data from the new 11AC wireless access points I was working on.
Didn't John Carmack of ID Software vanished voxel-based engines back in the 1990's as being technically inferior -- or maybe impractical -- with the video cards of the day?
How many atoms must we split over the definition of a chain reaction?
The professor at San Jose State University who gave my intro chemistry class a tour of the nuclear lab reassured us that a Three Mile Island chain reaction wasn't possible if an earthquake compromised the research reactor.
If the university has a nuclear science department, it probably has a nuclear research reactor in the basement. Although not big enough to trigger a nuclear chain reaction, they still have enough radioactive material for a dirty bomb.
I was recently unemployed for eight months, had 60+ interviews, and had three job offers on the same day towards the end. That's better than when I was unemployed for two years (2009-2010), where I had 20 interviews and filed for Chapter Seven bankruptcy before I got another job. The job market is improving.
Why did you quit contracting to go back to perm ?
A variation of that question is why do you prefer contracting over a permanent position?
This question always pisses me off. I didn't become a contractor by choice. I got laid off from last "permanent" position ten years ago and found nothing but contract work since then. Do I want to be contractor? Oh, hell no. I would love to have a permanent job and stay put for at least three years, which was what I did before.
The flip side side of being a contractor is that I have worked at many Fortune 500 companies in Silicon Valley. Each year I get a bigger bump as I moved from company to company. I recently ran into a old coworker from nine years, who still has the same job and makes the same amount of money. I'm making 80% more money than him because I'm a contractor.
Midlife crisis.
I had a roommate who got laid off from his QA job that he had for seven years since graduating as a software engineer from college, took a six-month vacation while drawing unemployment benefits, and discovered that no one wanted to hire him since he did nothing to maintain his programming skills. Needless to say, he had a young midlife crisis. Last I heard he was still working at the local drug store.
How do you then explain the 6 year gap in your resume?
Great Recession
The recent Dilbert comic strip summed up the hiring process quite nicely.
I'm doing the clean slate approach by using only the exported database from the WordPress blog and programming the static website from scratch. In some ways I'm completing the circle. This particular blog started off as a programming project while in school in 2002, converted into a Joomla website in 2008, converted into a WordPress blog in 2011, and now into a static website. I need to remove a lot of crud that accumulated over the years.
Or you could just use "wget -m" or something similar.
To do what exactly? BTW, '-m' doesn't appear to be valid wget command switch.
I was playing around with vacuum tubes as a six-year-old, pulling them out of old car radios in the garage and the TV in the living room. Scared the crap out of my mother whenever she saw me poking around the back of the TV.
In other words, if you're never going to tell someone you have it, what in the FUCK is the point in obtaining it.
The classic response for any college student facing dismal job prospects during a recession is to stay in school.
The only acceptable response is to drop out of college, join a startup, and make a few billion dollars. If you haven't done that, better hide the Ph.D degree.