4 ms·
There are two reasons for this. The first is that the 1/10th-as-good people shouldn't even have jobs. Their cubicle, chair, and the electricity to heat their
by jrockway 16y ago
There are two reasons for this. The first is that the 1/10th-as-good people shouldn't even have jobs. Their cubicle, chair, and the electricity to heat their work area are not worth paying for. But, good programmers are nearly impossible to hire, and you need someone to sit around and look busy while they are on vacation. Hence, bad programmers that are not worth paying for become worth paying for ... not to write computer programs, but to look like they're writing computer programs. Naturally they open an IDE and pretend to work, and may even create an app once in a while. But that's not programming, that's chair warming combined with some code monkeying. (Most 100,000 LOC "applications" created by people like this could be rewritten as five lines of Perl in fifteen minutes. I know because I've done it.)
The second great equalizer is the corporate world itself. Drawing from my own experience, 90% of the work done there is unnecessary. If Team A can't give me an API for their app that works, I have to redo their work. So now two people wrote that API. If the sysadmins can't figure out how to "yum install gcc", I have to install my own mini Linux distribution in my homedir. So now two people are the sysadmin. This all takes time and does not actually result in real work being done. Combine this with broken tools like Windows and Exchange, and your entire week is suddenly gone with nothing to show for it. (But that's OK, nobody expects anything.) If your actual job was to program computers, then you would be 10x as productive. But since your job actually is to redo other people's work, it's hard to be productive. Then there are other issues, like how nobody at a big company can read or write, so even the simplest problems have to be resolved with phone calls. Don't get me started on being able to read code...
So this is why people don't get paid 10x as much. The people that know that the work they're supposed to build on is inadequate for actually doing that spend that "9x time" redoing that work so that they can actually build on it. Or they have meetings.
At the end of the day, the guy who didn't write any code and just read Facebook all day is actually the productive one. At least he didn't make any work for anyone else.
(I should also mention that a lot of productivity comes from thinking beyond the current problem. The "YAGNI" attitude that is so popular these days is the cause of a lot of problems. Complex problems are really just very special one-offs of a more general but simpler problem. Solving the complex problem today leaves you with nothing for solving a very similar problem tomorrow, killing your productivity. Imagine the world before logic gates -- 10 transistors just to output 1 if the two inputs were 1? Imagine the world before programmable computers -- 100 electrical engineers working for a few years just to calculate a few prime numbers? Any problem is hard if you want it to be. "Professional programmers" want everything to be hard, so they feel like they are earning their money. They then code accordingly. And that is the real problem.)
- techiferous 16y agoIt sounds like you've worked at some very inefficient companies.
- wazoox 16y agoMost big companies are incredibly inefficient bureaucracies. Contrary to popular belief, big companies aren't any better than government agencies from an efficiency point of view (probably worse, actually).
- pasbesoin 16y agoI have to say this matches my personal experience, at a number of companies. A few highly productive people, and a fair number basically growing their arses (literally, or, I suddenly realize, figuratively). I worry about coming across as excessively bitter (and so useless, myself). But I've done some of the "productivity enhancing work" myself, including in Perl (lack of budget turned out, in this instance, to be a fortuitous gift in disguise). At one point, I basically replaced a five person department with myself, in the face of attrition both voluntary and forced. (This was before I learned to be one of the first rats off the sinking ship.) Throughout all of this, my biggest hindrance has been non- and especially counter- productive coworkers. Even management's asinine budget restrictions and decisions were nothing compared to the disruption causes by the more self-serving, ignorant buffoons. Too bitter, again. On the other hand, I had some great coworkers with whom I really enjoyed working, a great deal. It didn't matter what department or division you were in. As you met these people, there tended to be mutual recognition and understanding. In the future, you could pick up the phone or send and email, and get what you needed, no matter how many layers of management above might be opposed to the idea (whether on some sort of "principle", e.g. the latest management guru book they read; or due to ambition and empire building; due to personal animosity; blah blah blah). In several roles, I've set precedent as a result of this cooperation. People learned I didn't fuck things up, and I made their lives easier. In turn, I could e.g. bounce the server, despite not being in Ops. It was a lot more efficient. Gradually, they realized they could let some other people do that, as well -- often after I trained them. It's not arrogance, either. One of my replacements had some trouble with some concepts, but actually stuck in the job with a really good will to master it and do the best she could. So, when my lazy management wanted to can her and try the fourth friggin' hire in a year -- because she wasn't "quick enough" -- I told them where to get off. And she kept her job. It's not just about being the biggest brain. It's about trying and doing your best. A lot of people in corporate America only do enough to stay in the seat. And often, they get in the way of the people actually trying to get stuff done. (As to why I stayed long enough to accumulate this experience? It's complicated, in my case. I hope that, in sharing it, some others may recognize it a bit sooner in their own lives. And realize that some of these same obstructions are the ones who are self-serving enough to jump ship early and often, frequently ironically ending up better off and sparing themselves some of the misery of a downturn in the company. That is, if the economy is doing well enough and if their BS is good enough.)