813 karma · joined July 23, 2010
As far as it goes, it is a useless statement anyway. The point of calories in/calories out rhetoric is not about the physics; it's about how animals regulate their weight. You could make the same case that body temperature is about heat in/heat out but that would be missing the point of how humans regulate body temperature. The criticism of calories in/calories out is in this vein. Do you think you control your body temperature by consciously monitoring heat transfer? Then what makes you thinks complex animals control their body weight and composition by consciously controlling their calorie usage and intake?
At the end of the day, Taubes might be wrong about some or all of what he thinks. But the reason why he is generally well liked on HN, a community of very smart, very analytical people, is because Taubes is highly analytical and highly rigorous in his approach. This isn't some woo-woo magic stuff. I've never met a more methodically and rigorously researched book than GCBC. I can't review every study he cites because that would take 5 years at least.
Directories scanned: %g
Files found: %g, Directories with files: %g
1) don't critisize, create instead 2) Criticism is good, even if is kind of mean.
But I think this a false dichotomy. Words and tone do matter. If you put the object of your criticism in a defensive position, you are unlikely to effect any change at all. This is not some new insight; it's been well understood at the very least since Dale Carnegie. You might acheive the goal of making yourself feel good, but then that certainly isn't worthy of any external respect.
What's the difference between: 1) You app is ugly and it fucking sucks. If you used abc to do xyz, at least I wouldn't be vomitting.
and
2)Nice effort on your app. You might consider using abc to do xyz. It might improve the aesthetics and usability some.
Some might say it says effectively the same thing, but the there is a world of difference in the way the reader reacts to those statements.
I find this is a good mix of not too trivial but not overwhelming, I don't expect people to come up with the fastest possible algorithm on the spot. If they code the naive solution, that's OK if it makes sense and they can describe the performance characteristics. Then we'll talk over the algorithm and I lead them to something better and see how the conversation develops.