1,015 karma · joined October 18, 2013
I found this story [1] fascinating, and really enjoyed this interview [2] where he talks about working with Joe Walsh, a fellow amateur radio operator, and many others. He had a very midwestern modesty.
[0] https://news.ycombinator.com/item?id=39573756
[1] https://web.archive.org/web/20111005221916/http://www.perfor...
my_plot_script.R --plot_col=g_max --output_type=pub_quality data_file1 data_file2 data_file3
It's possible to use optparse/OptionParser() to get that information (but you have an option for every argument, no --param1 X --param2 Y file1 file2 file3) but it is much more difficult to fit those arguments into the RStudio environment. I want an RStudio to be able emulate reading command line arguments (since they do not exist in RStudio). Right now, I have to check to see if there are commandArgs(), and, if not, do something else to get the information to the RStudio script.
(2) There needs to be an option that says STOP if something doesn't make sense. I have dozens of beautiful data plots that look great, but in fact do not in fact plot what I think they do, because factors have not been properly assigned to colors, shapes, or linetypes. (And it can be really hard to recognize that the data has not been plotted properly.) Give me an option that says, if I did not explicitly declare a column a factor, and I did not specifically associate colors/shapes/lines with factors, then the data will not be plotted.
If the growth over the next 2 years is 10% of current total, having it mostly be renewable is nice, but not very meaningful. It is reassuring that coal growth is negative, but what is the total? Negative 2% is very different from negative 20%.
There are, of course, administrators among the administrative faculty, but far fewer than it appears.
Let’s imagine (unrealistically) that through some technical breakthrough, patients knew the cost before making their purchasing decision. They still do not know what it is worth, because they have no idea what the risks of not being treated are. There is a problem that your doctor also probably does not know the cost, but they are the only person in the decision making process with the information necessary to make a rational recommendation. (And, unfortunately, they usually have a conflict of interest.)
Healthcare is different from buying cars or groceries - even if you know the relative costs, you are unlikely to know the relative benefits.
Read from a certain perspective, TAOCP is less a book about how to do things better (the focus of many CS courses), and more about "wow, who would have imagined ...". I think CS students might find their curricula more engaging if, rather than having a set of concepts to master, there were actually interesting puzzles to solve. Thus, I suggest reading TAOCP not as a text book, but more as a novel. Take a look at the parts that interest you (how many ways of sorting 10 numbers can you think of just using paper and pencil?). CS is a lot easier to learn as a process of surprising discovery, than as a set of barriers that must be overcome.
I suspect that people who have decided to pay extra for the Pro model may actually have some idea how much RAM they need.