There can be all different sorts of anecdotes, but the link was about a study with more than 100k doctors, which would be a stronger evidence that the probability of survival is better for patients with younger doctors.
353 karma · joined January 9, 2013
There can be all different sorts of anecdotes, but the link was about a study with more than 100k doctors, which would be a stronger evidence that the probability of survival is better for patients with younger doctors.
Also, there are many books that discuss software design. The one that helped me most was "Principles of Computer System Design". Not all the parts are great, but reading the first few chapters & recommended books changed my software writing.
At an earlier stage, building my own sizable project helped me the most. I still remember writing bunch of Java code in the middle of Iowa when I was an exchange student, which ended up helping a lot of my friends course registration in my university and got great feedback about the UI of the program. I learned a lot, especially about all the basic system building, and the best thing was that it gave me the confidence that I am capable of building something useful.
Since then, one of my weekend hobbies was doing some fun project that does not need a whole lot of effort -- like making a simple dashboard for the family in Ruby, building a home automation bot in Go, writing some my own investment tool in Python, etc.
It's just the same as picking up another language or any other skill: there is no one path people learn it. The way I learned English was mostly by reading many books, and many other people learn a second language mostly by watching TV shows or talking to people. There is no set path -- although there may be necessary things people would need to do regardless to achieve high-level of mastery, like talking and reading in a language -- but one thing necessary is an incentive, especially a positive one, and building confidence over time.
The glassblowers there seemed to think that the repair of broken glass equipments is potentially hazardous to the glassblower, and one of the founders who handled more repair requests had two cancer surgeries. It's only an anecdote, but it could be a reason why it is difficult to find a successor of this 71 year-old person.
[1] https://translate.google.com/translate?u=http%3A%2F%2Fwww.ha...
But who knows? There could have been a death that could have been prevented by turning off a fan, and nobody can verify its nonexistence. My attitude toward this is like my agnostic attitude toward God: I just can't know its existence or nonexistence. And I think what the people in the article are expressing can be understood in a similar line (though 100% is an overstatement.)
Still I sometimes argue with Koreans with relatively less background in scientific thinking about scientific things like if fan deaths are possible, or using metal spoons for yogurts kill more microbes than plastic spoons, etc, but many times, my conclusion is that I just can't have any conviction about either ways.
[1] GPUnet: Networking Abstractions for GPU Programs, OSDI 2014 https://sites.google.com/site/silbersteinmark/GPUnet
I would say I am not a finisher, but what I am trying to do is reducing these reasons: trying to understand/plan better to the deepest level, sleeping/eating well, getting more satisfaction from finishing things than starting one, and doing smaller things, selectively.
Also, mapreduce is not embarrassingly parallel. Out of mapreduce, map is the only embarrassingly parallel phase. It has input parsing, shuffle, reduction phases that are not embarrassingly parallel.
On consistency: I don't think UN, as a group of nations with conflicting goals, tries to behave in a consistent way, although people are free to blame it for its inconsistency.
B.R. Myer's talk explains the motive behind NK's nuclear program pretty well.
http://www.booktv.org/Watch/11315/The+Cleanest+Race+How+Nort...