Yeah, since I work in the field, I think I know the difference. That's probably the reason for my post, in fact, huh?
If you think it's not due to not hiring people, you're mistaken. A QA professional, with say, 5 or 10 years experience in software testing, probably even with a BS or higher in computer science or engineering or a similar field, has a *bit* more know-how when it comes to finding and identifying problems (and in more than a "bug vs. not bug" nature - also problems with design, with approach, with marketing... it's called Quality Assurance, not "bug finder") than a kid out of high school who was turned down by Wendy's, and wants to brag to his friends that he "works for a game company" when he's not busy smoking pot or "just hangin out, dude."
Also, to assume it's so much an issue of time is also a fallacy, any more than it's an issue of time for the developers. QA is not some process to be tacked on at the end of the development cycle. It's an ongoing process which is engaged since day one. Read up on the software development life cycle and you'll see how it goes in companies that deal with things other than laser rifles.
"Dude. I was like, firing this gun or something? And it liked, crashed. Whoa."
This comment was edited on Jun 17, 11:13.