miniblog.

I've set up coveralls.io for Trifle lisp. 94% test coverage of .py files! The experience was nicely straightforward.

@CoverallsApp I'm getting a 'down for maintenance' on https://coveralls.io/sponsors#ourSponsors (after ~9 secs), is this expected. Is the service up?

http://t.co/h7elhFU0jD is excellent, and I'm struck by how many entries are just using contextual data.

Question of the day: How would you write an app if you wanted it work ten years from now? What tools or platforms would you use?

Not enough docs show examples. Trifle lisp tries to have an example for every function (just like the excellent http://t.co/E8vFyTrbez).

PEP 462 is an interesting insight into the challenges with Python core development. We're spoilt with GitHub, Travis and pull requests.

Implemented eval in Trifle lisp. It was actually easier than I expected.

Python: "\q" == "\\q" Ruby: "\q" == "q". C is as Ruby, but with a warning. In trifle lisp we will throw an error instead for clarity.

"Happily, the Tab-letariat can agree with the Space-eoisie that a separation of the whitespace classes is necessary and good."

Argh. I can't assume 'python2' is available on all Linux distros, but some distros now use 'python' for the Python 3 executable.

Just discovered ace-jump-line-mode, which lets you jump to an arbitrary line on screen. Wish I had known about it earlier. #emacs

CSS nirvana: changing styling whilst only looking at one page, and styling on other pages updates, but looks correct.

https://www.runscope.com/ looks like an excellent way of monitoring APIs in production. I'm looking for an excuse to try it.

Elisp surprise of the day: (setq 0x123 42) is legal. #emacs

"'Legacy code' often differs from its suggested alternative by actually working and scaling." --Bjarne Stroustrup