kong looks pretty cool!

any plans to add pluggable backend ie not use cassandra? i've no experience managing cassandra and would rather not worry about it.

Yes, Kong plans to add support for PostgreSQL (https://github.com/Mashape/kong/issues/331). In the meanwhile you can outsource Cassandra to cloud providers like https://www.instaclustr.com

For testing check out http://kongdb.org/, but don't use it in production.

A better error message would be helpful. For example I tried to do: https://falkor-api.herokuapp.com/api/query?url=https://kodin..., all I got was "Request failed"

That's a good point. I pretty much wrote this in an evening or two so haven't had time to refine it much. But yeah error messages will definitely be improved. It's because of the way URLs are handled in the underlying web app. Will be an easy fix.

I read through couple chapters and enjoyed it. Does anyone have suggestions on other books dealing with this level of complexity?

I haven't read any of the chapters of this, so my comparison may be a bit off, but you might check out The Elements Of Computing Systems[1]. It goes from logic gates to compilers.

http://www.nand2tetris.org/book.php

I thoroughly enjoyed this book but it doesn't go into near as much detail as I would like- it gives a vague, general concept of how things work and some pointers on how to implement them, but doesn't really go into real systems, often relegating major features to "optimizations", etc.

If you're looking for a really great book on basics of systems with particular focus on Unix/Linux and C (like what this tutorial seems to be... rather than all computer science), I don't think you could do better than "Computer Systems, A Programmer's perspective" by Bryant and O'Hallaron.

Modern Operating Systems by Tanenbaum, perhaps?

Here is the table of contents: http://www.amazon.com/review/R3K8J39AMWS64U/ref=cm_cr_dp_tit...

For something covering the "lower half" of this material, I highly recommend Patterson and Hennessy's "Computer Organization and Design". I'm currently reading the 5th edition, and have gotten to the last chapter, which is on parallel processors.

I should mention that print copies of the book are pretty expensive, but you can easily Google for .epub or .pdf downloads/torrents.

Hey hoverbear, sorry for the long wait time.

We're in public beta now and anyone can sign up: https://koding.com

P.S. I work for Koding.

Hey hobs, it's possible some chrome plugin is interfering with Github authentication though. If you can provide a little more info, I can debug it for you.

P.S. I work for Koding.

No worries, I got registered via chrome and now the github login works in firefox as well. Thanks!

We provide root access to our vms, which is why we require all users to provide a password. But once you signup with github, you can then login with either Github or email/password.

senthil@koding.com

mail sent.

Thanks Techbrunch. I replied back as well.

This is awesome! Only minor suggestion is to improve readability a little more. Font is way too small with too little space in between each entry.

Also, I got this error: http://cl.ly/image/2D2S1E020e0W. I think I clicked on Stanley Kubrick and then came back to the home page.

Thanks for the suggestions and for the bug report.

The only numbered notebooks I've seen are daily planners. Moleskines are leather, though not sure about the quality.

Edit: Saw these in comments: http://www.leuchtturm1917.com/de/content/startseite

Those fit with exactly what I was looking for, thanks!

* Write date in journal first thing in the morning when you wake up and keep the journal open next to you while working. This reduces the friction of starting.

* Look back at it at the end of the day and see what you've done that day. This is your reward for using it. Alternatively you could have your own reward.

* If you forget to do it today, restart tomorrow without any fuss. Don't worry too much about the lost day, like I used to.

In the beginning I was pretty excited about it and it was real easy, but after couple months it got a little old. Eventually I got around to the point where if I don't write in the journal while working I feel uneasy.