9 ms·
Programmers know when they've been more productive because they feel it. This is not the kind of measurement that is accessible to metrics and formal studies, b
by gruseom 18y ago
Programmers know when they've been more productive because they feel it. This is not the kind of measurement that is accessible to metrics and formal studies, but that doesn't mean it isn't real. It does mean that the measurer and the measured have to be the same person, or people working closely together.
- raganwald 18y agoSo... We can't quantify it or inspect it. We can't corroborate it. We can simply ask a programmer whether they are productive or not and trust them to answer for themselves. And if Alice meets Bob on the street and they disagree over what makes them productive, there is really no way to settle the question. If Alice says she is more productive using Ruby than Python, but Bob says the opposite, we must trust that they are both right, and furthermore we can't really draw any conclusion. Because Charles may report that he is more productive with Ruby, or Python, or perhaps Arc, and again he is the only one who knows.
- skawaii 18y agoCould it be that productivity differs for each person? Maybe we can't have a productivity scale that is the same for everyone? Maybe it has to be applied personally? But then again, maybe if we drill down deep enough, we'd find common themes or aspects for why Alice feels more productive with Ruby and Bob with Python.
- gruseom 18y agoYou're jumping to conclusions. I'm not saying this is the only possible measurement, I'm saying it exists and has some properties and not others. The absence of more "objective" measurements does not mean that programmers are talking nonsense when we discuss our own productivity. I think it is probably true, though, that the nonsense ratio tends to go up when we start discussing the productivity of others. That should tell us something.
- prospero 18y agoIt's an unsatisfying conclusion, but is it really all that surprising? To coin a metaphor, a programming language is a shoe; only you know if it fits right. It might stretch out and become more comfortable over time, but it's not a debatable point that it's pinching your toes. Programming isn't a natural mode of thought, and programming languages aren't a natural mode of expression. I think it's unrealistic to expect that we'll ever find a universal best practice.
- raganwald 18y agoYour simile is what disturbs me: Often when programmers describe their productivity they are really describing their comfort level while carrying out programming tasks. However, when we use the word "productivity" in every other aspect of business, we are describing the production of output. We don't measure how the output is produced, or the subjective feelings of the producers. So what output are we discussing when we talk about productivity? Or are we using the word in a special way that has nothing to do with productiviy as it is used elsewhere?
- deleted 18y ago[deleted]
- prospero 18y agoPoint taken on the simile. It's like that like never existed. As to the rest, I dunno. Let's consider the following scenario: every time you wrote something down on paper, there was a chance the paper would spontaneously burst into flame. There are strict, reproducible rules governing when the paper would and would not catch on fire. People go to school to learn these rules, which are varied and subtle. In this world I've described, is the best writer a person who can write the most essays that don't spontaneously combust? I feel like as programmers we think that because we can easily quantify whether something works, we can also quantify whether it's good. Or worse, that everything which doesn't burn away is essentially the same: just words on paper. It's simply not true. The fact that writing a program feels more practical than writing a novel doesn't change that.
- dmoney 18y ago
- harpastum 18y agoI agree that it is impossible to quantify productivity, but I believe it is not only possible, but _essential_ to inspect it. I like to think that most programmers enjoy being productive, and strive for increased productivity (rather than working just for a paycheck). I therefore also believe that programmers expend great effort over the course of their careers optimizing their work habits to maximize productivity. All programmers are different, but none of us is completely different from all others. There is much to be gained from examining what the others have learned in the process of programming. The danger in this is thinking that there is some objective Truth in programming productivity. So, Bob disagrees with Alice over what makes a programmer productive. Assuming both Bob and Alice are effective programmers, what we should really be examining are the ideas they have in common. For me, reading programming blogs from around the Internet gives me a giant mental Venn diagram--the ideas in the center are what I focus on.
- whatusername 18y agosure we can quantify it.* Give Alice and Bob the same task. See who can do it faster / better. (obviously better can apply on multiple levels - but the tasks should clarify that. Performance, errors, scaling, maintenance, etc) At the end (maybe of 12 months to allow for maintenance) you'll have a quantifiable result saying that Bob is more productive than alice.. (for that task - and probably tasks like it) * I didn't say that it was easy or that we should spend that much time on a pissing match.
- gruseom 18y agoIt sounds to me like what you're saying is that it's easy to measure productivity, all we have to do is measure quality. :)
- JesseAldridge 18y agoYes, we do need to measure quality. And maybe a simple metric wouldn't work, but a skilled programmer should be able to hold two results up side by side and judge for himself which is better. Controlled experiments with human judges seem like the best answer.
- jerf 18y agoIt's like intelligence, or obscenity, or justice. The more you try to define it, the further it slips away from you. If you think you've got a universally-agreeable definition, you're wrong. But you know it when you see it. (Even if somebody else might not agree.) What are you gonna do? All the halfway interesting concepts in life work like that.
- biohacker42 18y agoI am not sure that we can't quantify it. Who's really tried? There's been a few research papers here and there, measuring the things that are easy to measure in a corporate environment. But who has both the incentive and the skills to measure a very difficult to quantify subjective experience? It is absolutely a very complex subjective experience, but it ain't magic. It IS very had to measure but it's not impossible just because no one's really tried yet.
- trapper 18y agoSomeone hasn't read the excellent book "how to measure anything".
- access_denied 18y agoI think part of the "feeling" is knowing - internally - how much you have learned during that particular programming session. How much did you produce is one thing, but how much did you improve you capability to produce more another.
- akeefer 18y agoIn my experience, programmers think they know when they're being productive, but they're often wrong: for example, coding for 5 hours straight without realizing the time has passed might feel productive, but if you've been doing the wrong thing, or writing buggy or hacked-up code that will cost you in the long run, you probably haven't been nearly as productive as you think you have. Likewise, I often feel totally unproductive when pair programming, because everything feels slow and I'm not just cranking on something, but if I try to think about it objectively it's often the case that I get more done in that time by avoiding mistakes, finding better ways to do things, and by only doing the minimal necessary work. Similarly, to the point of the article, productivity of a team is a different metric than productivity of an individual: interrupting me might cost me 15 minutes of work, but if it saves someone else two hours of wasted work it's a big net win for the team. That's not to say that programmers have no clue, just that our internal radar isn't exactly infallible. People tend to feel "productive" when they feel like they're "getting a lot done," but real productivity depends on whether you're doing the right things and whether you're doing them well. And, let's face it, most programmers (myself included) really enjoy that feeling of just cranking on something and becoming so engrossed that they don't notice time pass. So I think that people are biased towards thinking that always corresponds with maximum productivity simply because it's enjoyable, and not because it's truly always optimal.
- brianto2010 18y ago> In my experience, programmers think they know when they're being productive, but they're often wrong. So true. http://www.geekherocomic.com/2009/01/19/efficiency-and-compromises/ http://www.geekherocomic.com/2009/01/19/efficiency-and-compr... > That's not to say that programmers have no clue, just that our internal radar isn't exactly infallible. People tend to feel "productive" when they feel like they're "getting a lot done," but real productivity depends on whether you're doing the right things and whether you're doing them well. So, is it safe to say that if you 'feel productive', you're most likely not?
- jefffoster 18y agoProgrammers are often a very poor judge of productivity. I've seen many Java programmers say they've had a productive day, but then I find they've typed 1001 getters/setters and intricately JavaDoc'd them. This is productive typing practice, but little more. In a similar vein, it's easy to feel productive if you're doing refactoring all day, but what has this actually achieved? One aspect of TDD that isn't often quoted is that it helps get a concrete measure of productivity (and it's one of the themes of Beck's book). If you can see that today you've knocked out 100 tests, that's some measure of progress. It's a running theme through agile-processes. Small iterations / stories / code changes with measurable outcomes.
- Tichy 18y agoThen again writing tests can be just as unproductive as writing getters and setters. Maybe that is one reason that it has become so popular (makes you feel more productive)?
- baseonmars 18y agoI think the hope is you write one test then write the code to make it pass. In theory the code and tests grow at a similar rate. If one treats the two activities as separate then i think it would be very easy to get caught up in the productive feeling that writing tests gives without receiving a good portion of the benefits.
- weavejester 18y agoIt seems to me that people's measure of productivity is relative. For a Java programmer, typing in 1001 getters and setters might be quite productive, at least compared to their typical day. For more sophisticated programmers, sure, it sounds like a waste of time, but perhaps that's because they have a higher average productivity.
- kragen 18y agoMaybe writing the JavaDoc helped them think out some design issues? Some of my most productive programming time has been sitting in a park with paper and a pencil. (Not billable, though, sigh.)
- adamc 18y agoI agree that this is really what a lot of people are probably discussing -- how they feel, whether they are in the zone. The interesting question is whether it really corresponds to getting stuff done. Solving interesting problems in new ways often puts me in that zone, but I'm not clear that such solutions necessarily buys the organization more.
- BigZaphod 18y agoI usually feel like I've been productive if I spent most of the day in the zone - but the truth is, that doesn't always move things in the right direction. For instance, I might suddenly obsess over some little visual detail that I want to get just perfect and end up spending an entire day on it. At the time it feels right - but looking back later when the project is behind schedule and everyone's in crunch mode, I have to wonder if that was really a productive day or not...
- jon_dahl 18y agoDon't forget the Dunning-Kruger effect. Mediocre programmers may feel productive when they get some nominal feature working, while great programmers may feel unproductive even though they've accomplished a lot.