miniblog.

Using Travis CI with Jekyll is a fantastic way to find build errors. Otherwise it's easy to use a different Ruby version that doesn't error.

Blogged: Lisp Is Just Syntax: http://t.co/Q39SBSxYTX (#lisp, #python and a ridiculous transpiler!)

The perils of accepting freedom-denying software (pun!):

The biggest problem in modern cryptography is usability and uptake.

"Regardless of the value of the DEBUG setting in your configuration file, all Django tests run with DEBUG=False." Wise, but surprising.

It's a _major_ undertaking to build a modern web browser. At this point, it seems unlikely that we will have new proprietary engine. Good?

I don't understand long legal disclaimers at the end of emails. If they're of legal worth, why d[o|id]n't they occur on letters?

If you're using Django with nose, `python manage.py test -v 3 --collect-only` is great for seeing where nose looks for tests.

"Unknown error, please try again". Argh, the perennial problem of black box cloud services.

A fun part of writing a lisp is snaffling great ideas from other dialects. http://t.co/cFBaa7vLke

Woah, new Twitter web UI. Most of the time I end up using third party clients though.

I suppose it was inevitable, but I'm still taken aback to learn about password cracking as a service: https://www.cloudcracker.com/

@melpa_emacs happy to report that MELPA is on http://t.co/b4PoC3L1P8 :)

TinEye lets you find other versions of the same image. How long before someone builds a facial recognition search engine?

No software is ever finished, though some reaches maturity.