You get what you pay for.
trenchescomic.com
trenchescomic.com
Put it another way. He's the only person in the organization who knows what they're doing when it comes to testing. He's in a position where he can have a tremendous positive effect on his organization. If instead of complaining that his fellow testers are incompetent, he could bring a benefit to the organization and pocket part of it.
Here's the script: "Hello Mr. Suit. Notice how I've discovered ten times as many bugs as my compatriots combined in the same amount of time. Why don't you fire ten of them and bump me up to fifty an hour. You'll be saving ninety dollars an hour at the cost of an extra forty-one going to me." Every business-minded manager would at least consider this. Naturally the numbers need to be adjusted, but anyone with a significantly higher output than their colleagues has the opportunity to make this sort of case.
Here's another potential script: "Lemme level with you, Mr. Suit, these guys are all kids who like playing games, while I've got years of experience as a professional tester under my belt. Why don't you replace their manager with me, and I'll train them myself. Ill whip them into shape, their overall bug detection rate will double, and you won't have to pay a penny. Just replace their ineffective manager with me."
Lesson learned: this situation isn't cause for bitching and moaning, it's an opportunity to cut throats.
Go read the archives; the quality of management in publishing is rather crap.
It smacks more of "we know that software must be tested, and this looks like testing so this is what we must do" - a recognition of a requirement, but not one which has been adequately implemented and fulfilled. There may have genuinely been nobody there who knew any better.
Because they can get kids to do it virtually for free, and it isn't completely without value.
What if one is not a cut-throat, but simply a competent person who wants to be surrounded by people of equal or greater skill so that he or she can learn from them?
Out of my experience with great QA in the past the two significant things they bring which poor QA does not are: 1) they create a detailed testing plan that allows them to 'checkbox' off things rather than simply throw time at randomly fucking around. 2) they have very rigorous reporting of issues including detailed repro steps, environment information, issue categorization, and (if the technology is provided) stack dumps.
Perhaps a company that provides this service specifically would work? Especially if the company had a technology aspect that allowed them to automate their own testing. Testing as a partnership service sounds like a business idea that makes great sense to me yet would be a difficult sell. It's rare to acknowledge that defects are guaranteed to exist, that a systematic plan to discover them can be created, that the earlier the discovery is found the lower the cost (exponentially) is to fix.
On the other hand those great QA of my past also had very strong domain knowledge of what they were testing. The audit step to create the plan would be important: the best QA really need to know the intended results for everything inside and out.
It all feels like a pipe dream to me, unfortunately. The norm seems to be "we don't want to invest in Quality Assurance, but we want Assured Quality, so just don't make mistakes!"
It looks like this is just another example of management believing these positions are unskilled labor that a certain type of folk likes to do versus an actual profession.
Now, having low-paying starter jobs isn't a bad thing in general. The local fast food joint probably has a fair number of high school students with no skills that are there for some spending money. People learn job skills by having a job.
Unfortunately, there seems to be quite a few business people unable to distinguish between I need professionals and unskilled labor. Ask any graphic designer about this one. I am amazed about how this is so common across multiple professions and roles. I honestly think the business schools in this country need to be overhauled because they are teaching people to make bad decisions.
I told him he was getting shafted hard, and convinced him to go demand a raise. Sure enough, the next day he told me his boss doubled his pay as soon as he asked. He just never had the confidence to ask before.
I clued up about 2 years ago, and have been asking for more and more money on a regular basis. The breaking point was when I asked for a certain amount and they literally laughed at me. I immediately started making plans to leave. Next monday I start a new job where I will finally be making more than my age in dollars per hour.
1. Don't have my head up my ass.
It can be hard. I can totally imagine myself being your flatmate in a parallel universe.
This should be required reading for each of us at least once a year: http://www.kalzumeus.com/2012/01/23/salary-negotiation/
Is that the case where you live?
But yes, I know a person. He has full time, surprisingly, but he refused health care BECAUSE he wouldn't be able to survive, and he is making more than minimum wage.
Definitely valuable to know what you're actually worth on the market, I didn't learn that until I got involved in the NYC startup scene.
I was really impressed by the guys who had been there for a while--they actually understood what they were doing, like the author of the linked article. If they looked over your shoulder for even a few seconds, it felt like you learned something.
One day the higher-ups noticed that I knew how to use a particular kind of software and within an hour I had a raise and a desk inside an air-conditioned office. No chance of doing warehouse work anymore. It was like the feeling you get when you go from a parking garage into a hotel lobby. That put the testing conditions into stark relief--it wasn't really as fun or interesting as I thought it would be. Putting it on my resume afterwards attracted some really boring job offers. But lots of places want cheap QA.
The people on top at the testing firm had it pretty much figured out. If their clients wanted to pay for really high-quality testing, they could do that. The resources are there. On the other hand, if they are just getting their software out the door, they can pay weak rates for summer job kids, and tell their developers to yell and scream until they get the more interesting-sounding bugs narrowed down to something actionable. I remember a few irritated emails: "I don't really care that the button is out of alignment," or "I'm not paying for grammar advice," etc. My bad, buddy. Why don't you talk to management about the conditions of your testing contract, and they'll get one of those veterans on the job? So yeah, the customers got what they paid for, too.
Yes, you are. Read the archives to learn more.
The temporary solution is to refuse to work for such companies and to compete with them until they go out of business, despite their capital advantages.
Often times this is hypocritical. Warren Buffet has a folksy demeanor, but his IQ is off the charts and he reads more than several hundred pages per day of challenging material and makes numerous critical decisions besides. But he knows that affecting a down-home-average-man persona is the way to sway Americans who distrust eggheads who show off their expertise.
The negative effect of this in the workplace is that American pretenses to egalitarianism result in a lack of respect for skill, acumen, and intelligence. It's not quite the 'tall poppy' effect you might see in other countries, but it can have some similar effects.
The kind of places that view software test/dev as labor or "resources" really are missing the point. Owing to work styles, tools, experience, and knowledge, the best people in this field (software) can do things that less talented/experienced people simply can't. Not "I can get it done 2x as fast as the next guy", but "I can find issues, bugs, and defects others wouldn't find, AND I can do it more quickly."
Coming back to reality, a lot of software doesn't need to be the best. For every blockbuster game, or operating system kernel, or billion-user social network, there are hundreds of CRUD apps, Wordpress sites, etc. that are more rote. But to compete in the winner-take-all kind of markets, you have to pay for the best.
I think the point is, buyers and sellers of talent need to be realistic about what they need and what they're willing to pay for it. To the guy who wrote the article, find a place that (1) NEEDS your skills (frankly a lot of places don't) and (2) is well-funded enough to pay market rate for them.
Broadly speaking, I think there are two major classes of software.
"Class 1" software is produced under tight budget constraints, often for a cost center. These are the payroll systems, the receivables tracking apps, employee training websites, admin portals, etc. Big consultancies write a lot of this stuff (Deloitte, IBM, etc.) This kind of software is tremendously important, but isn't seen as differentiating by management. "Success" here means (1) it works "well enough" and more importantly, (2) we didn't blow the budget writing it. Cost is always a factor.
"Class 2" software contributes directly to the bottom line of the company. It's produced by expensive, in-house developers who take their craft seriously and want to deliver the best product possible. Budget is defined by P&L and success means "the project will generate a lot of revenue". Note that cost control isn't as big a concern here.
Now, having worked in the industry, I've realized probably 90% (99%?) of all software produced in the world is "Class 1" software. But you really, really want to be working on "Class 2" software; it's better in every way, including attention to quality, willingness to pay developers, etc. For developers, the experience of making Class 2 software strictly dominates Class 1.
As for the article, I've noticed how when management crosses over from one class to the other, there's a lot of conflict. Beware of "operations"-type people working as project managers. You really want line management to be former developers who "get it". It might take moving to a different geo, or working remotely, but just don't work on crap.
Note: as I write this, I realize I'm reiterating a stack exchange answer I saw a while back -- great reading for all developers. http://programmers.stackexchange.com/questions/45776/why-do-...
The management is completely incompetent (no clue how a sw project works), so even though they blow millions every year, the project setup, architecture, separation of teams, is all abysmal. The different teams cause everybody to no longer give a damn, because if something is broken, you are guaranteed to never be able to fix it - you'd need to call in lots of meetings first. So we all build up little fortresses that call the other module's services.
I'd differentiate projects as: those where people in charge care about the underlying build quality (call it technical debt, but that's not nearly all of it), and those where people in charge don't give a damn for anything except their current deadline/objectives (doesn't matter if anything of value makes it into the current build).
After a few years if they figure out it's not worth it, the company just have to hire again in the endless stream of youngsters.
You need to really re-examine how you deal with people going forward.
I'd recommend we form a trade group and boycott working for the industry, but there are lots of people for which its "one of their passions" who would (as is their right) break ranks and still do it, so it would be an exercise in futility.
In any industry in which lots of people pursue it with little regard for compensation, salaries are going to be in the toilet.
Kid, there are people in this world putting rockets in space, making self-driving cars and making lasers that can shoot flying mortars out of the sky. Maybe one day you will actually have something legitimate to be cocky about, but until then I suggest you wind your neck in a little and take pause for some perspective.
He was actually polite about the people he worked with an identified the issue as been at a more senior level, the guy also has the experience to back up his claims.
Now I could say "I suggest you wind your neck in a little and take pause for a little perspective" but then I'd be the condescending douche.
Also that there are people making self-driving cars and lasers that can shoot mortars out the sky devalues other peoples work not at all, indeed I suspect the mortar shooting out the sky laser is rigorously tested by Q&A.
It is empirically of no value whether or not this person is "sticking their chest out" over "bettering a few teenagers at a shitty job." What's valuable is understanding that relegating something this crucial to such a position can harm the long term prospects of a company and this article brings that issue to light.
That said, all accomplishments are relative as is the emotional pride someone feels over them. Sebastian Thrun can be bested at even his best by von Neumann at his worst, does that mean Thrun shouldn't take pride in his work? Nope. Life is complicated. Feel happy about what you can and let the rest be.
The obvious choice is to hire one 18 dollar an hour tester and 4 9 dollar an hour testers. After a training period (probably < a month), you'll have 2 quitters and 3 good testers at 2/3rds the price.
The simple answer is to run your own finances like a business. Know what you need to earn to be profitable to your level of satisfaction and turn down offers that don't meet that requirement. I've been in manys a job interview when the inevitable awkward question about salary expectations arose and I simply put out my number and didn't hear from them again. Fine, they made their decision on my value and I made mine and I move along without wasting anybody's time. I didn't blast the other employees at the companies or proclaim myself as an expert in the field.
I would say stop taking things so personally and if the company isn't willing to pay what you believe yourself to be worth, find one that will.
I read it more as a "look how stupid this company is" piece, rather than a "look how smart I am" boast. If he were really smart, he would have kept his flappy mouth shut at $9/hour, then offered to consult for the company about their quality assurance efficiency at ten times the hourly rate after quitting.
A business so clueless as to cheap out on quality control probably values advice by how much they had to pay for it.
And if he were really smart and evil, he would have used his skill to sell all bugs found beyond his quota to the other "testers". If all it takes to not be fired is to find one new bug every two hours, you find maybe six for yourself in the morning, and sell the rest at $10 each just before the management metrics get compiled.