Jon Black

I've started added some doxygen style comments already. But you're right, that should be done here as well.

@kbknapp I like the proposed layout for the book and would love to help out. A lot of what's being proposed I suspect will end up in the first section...

I found the following quotes about the UNIX philosophy which I think outline our cause, too: > **Many UNIX programs do quite trivial things in isolation, but, combined with other...

I copied the following items from the here: https://www.slideshare.net/bigfishdesign/well-behaved-unix: * Correctly handle signals (SIGHUP, SIGINT, SIGCHLD) * Respect hard/soft resource limits (e.g. max open files)

I'm not sure where I copied the code from, but I had the following line which was also printing the cypher queries. Not strictly related to logging, but a headache...

I'm not using rails. My issue was the subscription to query and printing which I copied from somewhere without knowing it.

What's misleading (particularly for beginners) is the following line: >Ember will look for an error template **or route** in the following order I've always considered a route to be something...

That makes sense. In that case, I would expect some kind of error response because it's guaranteed never to work but fails quite silently. Perhaps the Spec resource shouldn't be...