4 ms·
I'm incredibly intrigued as to how they are sure they are not measuring the reverse direction. That is, developers in a poor process and badly managed product
by taeric 10y ago
I'm incredibly intrigued as to how they are sure they are not measuring the reverse direction. That is, developers in a poor process and badly managed product are likely to be unhappy. Not that unhappy developers are likely to poorly follow process and create poor software.
I'm not asking to throw out the results. I want help understanding how they are able to make this claim.
- PaulHoule 10y agoDoes it matter? Fix the broken process and you get happier developers and better productivity.
- foota 10y agoIt does matter. If unhappy developers cause bad software then the solution is to make the developer happy and the software will fix itself. If it's the other way then the process is the one that needs fixing.
- artifaxx 10y agoFor current issues yes, it doesn't matter you just fix it and get the results. If you want to prevent it in the future it helps to know which one causes the other. Then you can focus preventative efforts on the factor that causes the issue.
- jayajay 10y agoDevelopers can also become unhappy when they are working on products which they think either aren't important or aren't ethical.
- taeric 10y agoYes it matters. You have to know the direction of causality. Consider it in different words. "Tired people are bad for themselves, for process, and for projects." To many, this will read as "hire folks that aren't tired." Worse, it will be "your folks are tired, so they will make things bad for themselves, their processes, and their projects." At best, you will get people who will see it and victim blame in a way that won't help. "You are jeopardizing our ability to succeed with your tiredness. In addition to your current tasks, I'm assigning you the job of getting less tired." So... odds of increasing wakefulness, slim. Now, it could turn out that it is something you can fix in this way. I don't know and that is my point.
- artifaxx 10y agoUnfortunately without putting randomly assigned teams into controlled settings to test this, how else can we figure that out? I want to know too, but this seems expensive to test to any high level of certainty for the causation.
- taeric 10y agoReading what you are saying, I would say more that there is a link between unhappiness and these things. This title is borderline negligent.
- artifaxx 10y agoI agree, the title is certainly overconfident if not negligent. Preventing people from writing inaccurate communications would be the topic of many studies and papers by itself though!
- patmcguire 10y agoRandomly assigned teams sounds like any straight out of college hiring pipeline, although controlled settings is harder. Google has done research on this, although I don't think they've done much with it.
- artifaxx 10y agoGood point. I don't think Google did exactly that, but I did find this: https://hbr.org/2013/12/how-google-sold-its-engineers-on-management https://hbr.org/2013/12/how-google-sold-its-engineers-on-man... It still is Google specific data though, so sadly it won't generalize as more than a set of ideas to test.
- 131012 10y agoWelcome to the fuzzy world of social sciences my friend! More seriously, these guys need some help from other disciplines (psychology, sociology or business administration). There are so many ways this thing could go wrong... Reinventing the wheel can be a cool side project, but won't get you published anywhere.
- brandall10 10y agoI'm going to go out on a limb and say it's inversely proportional to skill. That is, skilled developers will want a better product/process and they will want to work with other skilled devs. Putting them in less-than-ideal situations causes frustration. OTOH, a poorly skilled dev will want to push the environment in the other direction, for no other reason than to obfuscate the lack of skill. Putting them in an ideal situation for the skilled dev causes fear. Their aim is job security.
- watwut 10y agoI do not think it is that simple. Skilled developer can still be pretty fine with bad process, as long as worst consequences of the process don't fall on him personally. So when juniors have more mistakes as a result of not knowing requirements or code changes (process does not help to broadcast information), the skilled developer is fine - he is doing most code reviews so he personally knows enough and has control. Skilled developer in that situation will resist changes, because he is fine - it is just that juniors are less capable which strokes his ego. Or when junior are increasingly demotivated due to excessive micromanagement (bad process), skilled developer is perfectly fine - he is the one doing micromanagement. The fact that juniors could learn faster and achieve more will escape such developer. Moreover, more skilled developers are oftentimes better able to offset the bad process. The less skilled developer pays more price for bad process - it turns him from able to do work into unable to perform the work. Technical skill and ability to organize or see through process are not the same thing. You wont be able to organize if you do not have enough of technical skill, but technical skill in itself wont make you able to create good process.
- brandall10 10y agoI mean much more than technical skill... communication, delegation, mentorship, humility, culpability, etc. The hallmarks of being a good teammate in addition to someone who can sling code. Character is important. If someone like this is in a situation where they need to micromanage or mitigate that is going to be a source of frustration. If someone has dysfunctional or antisocial tendencies and that's the reason why they're technically excellent, yes, they will gravitate toward chaos, just like they would probably gravitate toward a co-dependent relationship in their personal life. Also to be clear, when I say skilled I'm talking about relative to the expectation of the position. A skilled jr. dev will be one who possesses the potential for greatness and who does good work at that level. As a sr. dev may enjoy mentoring others, a good jr. dev will seek out mentorship. And an ideal environment will be conducive to and support these types of relationships.
- d4mi3n 10y agoIn my experience, a good process and environment will make people of _any_ skill or experience level shine. Nobody likes to stagnate. Give most people a safe place to learn as they work and you're likely to see them improve over time.
- codingmyway 10y agoThere are plenty of things that affect happiness and therefore productivity if you follow their assertion. The stress of trying to pay rent in tech cities being one I can think of. Would be interesting to see if developers in more easy going places are more or perhaps less productive.
- omouse 10y agoIt doesn't look like that's the point. It looks like the point is to have a good starting point for further studies that will use the same codification for surveys and questionnaires so that various studies can be compared.