25,360 karma · joined December 4, 2014
http://austinhenley.com
The C++ template answers are particularly scary...
PDF of the book: http://jeffe.cs.illinois.edu/teaching/algorithms/book/Algori...
I don't think that is weird at all. After the lead student on a project leaves, the faculty, especially non-technical or not so organized ones, may not even know how to access the data anymore. Who knows what arcane scripts or processes are needed to get it in a shareable form.
There can also be hoops with the IRB to jump through and a lot of effort in general to give someone access to data. I had an IRB insist that all raw data be deleted after 2 years of collection anyway, so by the time the paper got published the raw data had to be deleted forever.
I wish it were easier to release data and replication kits, but sadly the incentives aren't there.
void XorSwap(int *x, int *y) {
if (x != y) {
*x ^= *y;
*y ^= *x;
*x ^= *y;
}
}
[1] https://en.wikipedia.org/wiki/XOR_swap_algorithmOn another note, why does everything have to be exciting? Small incremental improvements over the years is what I aim for.
const char* myString = "Blah";
(var my-string (* (const char)) "Blah")In fact, this summer I wrote a 3-part tutorial series on implementing a BASIC compiler: Let's make a Teeny Tiny compiler (https://web.eecs.utk.edu/~azh/blog/teenytinycompiler1.html)
Not reproducible is different than no one attempting to reproduce it.
In the spring I’ll be teaching a graduate-level university course on how the Python compiler and tooling works, so I’ll be showing them your articles.
To summarize, a lot of effort during code reviews is spent on superficial details while missing high-level design discussions and bugs. Anything that can get rid of those superficial problems (i.e., linters and program analyzers) is helpful, but we found that it was even better to optionally show the analyzer's warnings to the entire team , not just an individual prior to the code review. Showing the warnings to the entire team let them discuss them (and they often did) and decide as a group what should be done.
Findings from our project: https://web.eecs.utk.edu/~azh/pubs/Henley2018CHI_CFar.pdf