miniblog

After implementing COND in my partial evaluator, I've concluded that IF is a better special form. COND simply has too many ways to use it.

Travis is introducing Build Stages, supporting workflows like 'run all this in parallel but only proceed if green' https://blog.travis-ci.com/2017-05-11-introducing-build-stages

Language Server Protocol using Clangd https://eclipse.org/community/eclipse_newsletter/2017/april/article5.php C++ is a textbook example of a community benefiting from a shared OS parser!

'Fishing' for p<0.05 is an unfortunate term:it implies ill-intent rather than inadvertently finding spurious results https://www.stat.columbia.edu/~gelman/research/unpublished/p_hacking.pdf

I've not found anything that scales to lengthy text as well as book/ebook. Long webpages are too easy to accidentally scroll.

The Smalltalk Blue Book https://stephane.ducasse.free.fr/FreeBooks/BlueBook/Bluebook.pdf is great (introduces the language, explains usage) but also has this cute mouse explanation!

Ensure you have enough data to run any subset of the code!

It's always seemed odd to me that Lisp is mentioned with functional programming. Perhaps FP colloquially means 'effective but uncommon'?

'yarn create foo' automatically installs create-foo, so users don't need globally install the correct tools: https://yarnpkg.com/blog/2017/05/12/introducing-yarn/ (neat!)

Really interesting filesystem, which even uses machine learning to predict access patterns to help caching! https://twitter.com/changelog/status/866680805887807488

GitHub integration in Atom: https://blog.atom.io/2017/05/16/git-and-github-integration-comes-to-atom.html (I'm excited to see how this develops, it's GitHub's central feature set)