miniblog.

Brilliant CSS minifier: http://t.co/P2ug0OT7KL -- very cool.

Need to submit a BREW request to a RFC2324 device over Hyper Text Coffee Pot Control Protocol? Emacs has you covered: http://t.co/qFxG9pjW4E

I continue to be impressed with @digitalocean . Slick and works really well.

Most tourism webcam sites are disappointing. Huge scope for disruption.

@duolingo should there be a translation visible on a sentence's discussion? Found whilst doing http://t.co/cFmBVS2RaA http://t.co/QcoGZxyVSQ

@docker Typo on http://t.co/2fLgdBPUWd "Your almost there" on the JS quiz. Which repo should I send a PR for?

Ruby's 'more than one way to do it' still seems foreign to me. Comparing Chef script practices:

Had to install a Fortran compiler today. Yikes! Haven't needed to setup Emacs for it yet, fortunately.

Image recognition with nltk and some basic image processing still feels pretty magical.

I've noticed that the ease-of-use of an API is inversely proportional to the number of docs tabs I end up opening.

I've actually used metaclasses today! Ensuring a #Python class is never instantiated twice with the same arguments:

Surprised to discover that 'foo " bar' and 'foo \" bar" are the same in Python. Not what I was expecting.

If you use #python and #emacs with MELPA, you can now install the emacs package python-info to view the Python docs as an info manual!

I'm finally beginning to wrap my head around python packaging. The current convoluted state of affairs summed up: http://t.co/eWZkjjz2QK

Hmm, what's the correct Stack Overflow etiquette when you get two excellent answers?