miniblog.

Emacs tip of the day: http://t.co/dGscbchZVm

Compiling Clojure to shell: https://github.com/pallet/stevedore . Sounds slightly bonkers, but effective (especially wrt improving startup time).

I'm gradually getting into org-mode. It has yet to revolutionise my life, but it's handy for taking notes with inline code.

'63 packages marked for upgrade' I feel I need to upgrade and test one-by-one. This is why I'm excited by stable packages on @melpa_emacs.

With Office available on a wide range of platforms, why bother with Windows? Only a few obscure games is the only reason I can see.

Interesting HN comment contrasting TDD and unit tests: https://news.ycombinator.com/item?id=7467853

I've seen ^L used in elisp source to break up code into screenfuls, but today I saw something similar in Python:

"The biggest reason to use twine is that python setup.py upload uploads files over plaintext." Cripes, I did not know that. #python #psa

py.test has this curious feature 'xfail', that allows you to ensure a test execute, but expect it to fail. Not sure I've had a need for it.

Travis version matrices are great. A few lines in .travis.yml and suddenly I'm testing against a wide range of dependency versions

Debugging a git-svn issue by using `git svn clone` on a GitHub subversion URL. I've come full circle!

Discovered find-file-at-point at point today. I used to wish #emacs had this, and it already does!

It's remarkable how many software projects never reach 2.0. Reaching 1.0 is also getting rarer.

Turns out using Python 2.7 does not make you entirely immune to memory leaks: http://t.co/9vbgL2dDMJ (fixed in 2.7.4)

According to T&Cs our solicitors will keep electronic records for _15 years_! That'll require good backups and careful file format choices.