217 karma · joined June 4, 2008
The other case, which is what I thought the article was about, is more of an "opportunity" type of luck. For example, if you happened to find a £10 note while walking home. That would be called "lucky" but it is not simply the result of chance: it is the result of you being more observant than everyone who didn't notice the money before you. And in that sense, people can easily be "luckier" than others, as the article describes.
I think this is an important point, which is freqently forgotten. So many apps that would be useful in a foreign country are useless because they require internet access. When I went to Bulgaria last year I would have loved to have a translator app for my iphone, but every single one available required internet access, which there's no way I'm paying for at £3/MB!
Both require knowledge of drag (and preferably a vacuum chamber) to perform correctly. Without that understanding, experimental results would probably have "proven" the rational model.
Does anyone know when air resitance/drag were discovered? A quick google indicated some time in the 1600s
* Went from being able to work on a computer unbearably 35 hours a week to 70+ virtually pain free (when I worked for a YC startup)
That's definitely encouraging. At the moment I can manage about 40 hours a week. Any more than that (like I'm doing at the moment) and the pain comes back :(
I thought this was an interesting remark, particularly as it would 'only' put him in the "lesser rich" band defined at the end of the article. It makes me wonder why he picked that particular amount, whether it marks a decent balance between effort and reward, or just a decent income off the interest for savings.
That doesn't necessarily make it a good thing though... At least with facebook or a phone you get to choose some of the data that is held on you.
(And believe me, if they would let me use something other than IE6, I would.)
I try to take into account how accurate my estimates will be: if a sub-task is something I've done alot, I stick with my estimate; if it's something where I think there's a risk of it going wrong I add more time (keeping a note of the estimate and the risk time separately - it makes project managers think you know what you're doing!). I then add them all up, divide by 0.7 (roughly how efficiently I convert booked hours into directly worked hours - the rest is email and meetings etc.). Also, any task where you have to write code that works with someone else's code, I double the estimate.