Ask HN: Is software engineering a meritocracy?
It's discouraging to know that no matter how hard one works, or how much more skilled one might be than another worker has nothing to do with career success. Frowned upon are things like working extra, going above and beyond, and trying to do a "good job". For example: A colleague was recently baffled by my attempt to save resources by working efficiently, and "I don't get paid enough to..." is often overheard. It's a generally negative environment with a persistent adversarial relationship between labor and management. The message from labor leaders is often irrational and borderline propaganda.
From the outside looking in, software engineering seems like a pure meritocracy, where one's skill is constantly on display, and something that's rewarded. I often think that I'd rather be a crappy software engineer who's earned my place than excel without reward in my current job. Unfortunately, my earning potential is probably higher if I stay the course. Money isn't everything, though, and I'm nearing an ability level that would allow me to find an entry-level software job. Just wondering what others' thoughts are on the meritocracy idea.
6 comments
[ 5.1 ms ] story [ 28.4 ms ] threadThe good news is that the industry is young, California has a giant pool of VC money, and also doesn't have non-competes.
It is relatively easy to put companies that reward incompetence out of business: They aren't going to innovate enough to hold market share for long, and they also won't retain the talent competitors need to poach from them. This means that, on average, you'll walk into a pretty good situation (Put another way, companies with bad environments have shorter half lives than in other industries).
It's a meritocracy in the sense that the Software Engineering community values skill and output more than "years of experience." As far as what's valued by idiot middle management, it's largely the same as everywhere else (though maybe not as bad).