That's fine, but you still need a control group that is given no compensation at all as a baseline.
426 karma · joined February 3, 2009
That's fine, but you still need a control group that is given no compensation at all as a baseline.
The studies that are being referenced lead naturally to the hypothesis "what would happen if I didn't give my employees any kind of artificial incentive at all?" (let's assume that they are all knowledge-work employees, say programmers for example).
The studies referenced in the talk and in Alfie Kohn's books suggest that you would see an increase in productivity, since that pesky, harmful incentive has moved out of the way.
Common sense (and experience, should anyone be foolish enough to actually try it) suggests that your workers will simply walk.
So while I think there is a lot of valuable insights to be gained from these experiments (e.g. people work like hell when something has meaning for them - see the works of Viktor Frankl for more on this), I think there's too much of a tendency to oversimplify and say "incentives are bad, mmkay?"
Fair enough. A counterexample: "the paycheck." :)
Those being?
It's not "completely broken," but no hits for a query of "zag" in an email that contains "zagg" comes uncomfortably close to "doesn't work." (FWIW, I use gmail and haven't had any huge problems with search, although I have had to do way more work to find something than I would expect given that it's from Google).
Code Complete? really, just read Weinberg
'twas just a quick copy and paste from my fortune file. Although as far as I'm concerned there ain't nothing wrong with Code Complete.
"Gerald Weinberg tells the story of a programmer who was flown to Detroit to help debug a troubled program. The programmer worked with the team who had developed the program and concluded after several days that the situation was hopeless.
On the flight home, he mulled over the situation and realized what the problem was. By the end of the flight, he had an outline for the new code. He tested the code for several days and was about to return to Detroit when he got a telegram saying that the project was canceled because the program was impossible to write. He headed back to Detroit anyway and convinced the executives that the project could be completed.
Then he had to convince the project's original programmers. They listened to his presentation, and when he'd finished, the creator of the old system asked, "And how long does your program take?"
"That varies, but about ten seconds per input."
"Aha! But my program takes only one second per input." The veteran leaned back, satisfied that he'd stumped the upstart. The other programmers seemed to agree, but the new programmer wasn't intimidated."
"Yes, but your program doesn't work. If mine doesn't have to work, I can make it run instantly."
- _Code Complete_, pp.595-596
within epsilon of 100%. I love Joel, his articles, and the Stack Overflow podcast, but nobody would have heard of him (or FogBugz) if he weren't such a brilliant marketer. He established FogBugz and Joel Spolsky as pretty big brands in the programming community, and made a previously unknown software company into what is now seen as one of the elite places to work in the industry.
He's got the technical chops to back it up, but that doesn't matter - he is amazingly good at marketing, and he really gets the power of brands.
My mind has been blown.
Do we even need to officially call "bullshit" when Tim Ferriss posts something, or is it just assumed now?
If you read 10 pages of technical material per minute, you will not have anywhere near as good an understanding of it as someone who read it slowly and carefully. Reading dense technical material at this rate is almost completely worthless (perhaps even worse than worthless, because there is a non-zero probability of the reader fooling himself into thinking he actually does understand it)
I believe this was shown in a study where experimenters gave reading selections to self-proclaimed speed-readers without telling them that the text was actually two separate texts mixed together (i.e. so that line 1 was from book A, line 2 was from book B, line 3 from book A, and so on). The idea being, of course, to see if they could really comprehend what they were reading, since the fact that this was a jumbled mess would be apparent to any careful reader within seconds.
Of course, the punchline is that none of the speed-readers even noticed it, which should give some indication as to the level of comprehension that can be achieved via speed-reading.
This is true, but I think in the original poster's case it could be much more easily and reliably be accomplished by continually giving him problems that are within (or more ideally, just outside) his circle of competence, rather than a problem like "predict stock prices" which isn't in any human being's circle of competence. Moreover, with the latter problem, he'll get virtually no feedback as to whether his answer was correct, because a correct answer for "use statistics to predict stock prices" doesn't exist. Odds are that if he follows that path he'll quit before making any progress, or at the least he won't be able to close the feedback loop that is so vital to gaining expertise.
I think that if he's starting from ground zero and wanting to learn statistics, he'd be much better served by sitting down with The Cartoon Guide to Statistics and a deck of cards and set of dice first. He can work his way up to conquering the stock market :)
Don't tell Google that it's slogan ("Organize the world's information") is biting off more than it could chew.
I think that's apples and oranges - he's trying to learn statistics, not trying to convince potential clients or investors that he's already an expert. I don't think it would be harmful at all for him to have a lofty, far-out goal like "predict stock prices" to aim toward, but I do think that if he starts out trying to learn statistics by typing "statistical stock prediction methods" into Google, he will burn out rather quickly. Pagefaulting in knowledge when you need it is probably optimal for something where you just want to make sure your knowledge is passable, but if he wants to truly know his domain, he's gotta get out the marbles and urns. :)
If you want to learn statistics, it's probably better to start at the beginning (_Cartoon Guide to Statistics_, O'Reilly's new _Head First Statistics_, or Huff's _How to Lie With Statistics_) than to leap headlong into a huge, mostly intractable problem and pagefault in knowledge at each point you come across something you don't know how to do.
I'm still waiting for M-x kill-it-with-fire.
I'm pretty sure programmers don't want to hear "you need to be writing functional specs" [http://joelonsoftware.com/articles/fog0000000036.html], "you don't know enough about Unicode" [http://joelonsoftware.com/articles/Unicode.html], "if you don't 'get' pointers and recursion, you just ain't cut out to be a programmer" [http://joelonsoftware.com/articles/ThePerilsofJavaSchools.ht...], or "you should never scrap a working codebase and start all over" [http://joelonsoftware.com/articles/fog0000000069.html]
http://www.fourmilab.ch/hackdiet/online/hdo.html
It will calculate everything for you and even provide the pretty little weighted graphs just like in the book.
and b) the idea may not be silly but the name sure is. By this nomenclature, all current economists should more properly be called "Econostatisticians" or "Econopsychologists" (to quote Charlie Munger speaking about the silliness of the term "Behavioral Economics": "If economics isn't behavioral, then what the hell is it?!?")
No offense meant, of course. I just think it's a bit humorous. He's an economist who uses methods from physics, that's all - no need to make up a new name for it (let alone a name that sounds even dopier than the previous name).
Does he study the supply and demand for pendula and inclined planes?