miniblog.

Literate programming with continuous testing: http://t.co/jgVWLzj4e3 Feels rather reminiscent of Bret Victor's work.

Sometimes the increased computerisation of the world bothers me. The idea of rebooting a watch or toaster is no longer inconceivable.

I'm happy to announce v0.5 of Trifle lisp! You can now actually do things with strings! (They're just sequences now)

Docs or it didn't happen.

Classic #Emacs tip: if you use query-replace 'foo' with 'bar', Emacs will replace 'Foo' with 'Bar' and 'FOO' with 'BAR'. Ingenious.

Etsy actually regularly run ClamAV on their source code! http://t.co/pzZmFCMwjE

It's wiser to have a simple backup with an awkward restore process than the opposite. Simple backup schemes get run.

Type-checking is just one static verification tool. Arity, numeric overflow, array bounds and null errors can also be verified statically.

The difference between a functional experience and a compelling experience is usually huge.

Migrating servers is often more hassle than anticipated.

IPython also allows you to paste in '>>> foo()' and it treats it as 'foo()'. Really smart, and not an obvious thing to implement.

IPython includes a 'who' command, which shows variables that have been defined during your interactive session (not imported). Handy.

Having code style guidelines is a good thing, but after getting to know a team it's usually possible to work out who wrote what.

It's remarkable how many successful languages don't provide namespaces.

Downloading software securely is nearly impossible: http://t.co/8bgFvzLU3u App stores and Linux package managers do a somewhat better job.