getriver

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.

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"

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

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.

Thanks Techbrunch. I replied back as well.

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

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.

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

* 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.

It usually goes:

* Write a todo. Ex: Log errors from Fb. * Ask a question if I'm stuck. Ex: Will Log4R block the reactor? * Play with various approaches. Ex: Write in thread, plug into Goliath's logger. * Note any bugs. Ex: Logger blah blah * Rinse and repeat.

I know its a silly example, but you get the idea. Hope that helps.

Its a trial and error process. Write down as much you can without slowing down too much and then try to read back in couple weeks and see if it makes sense. The longer the gap in betweenm the better since your memory disintegrates and you're left with just the information on the paper.

Sadly I've never run into a notebook with pre-numbered pages. I did buy the Think/Create/Record for less than 4 bucks. Numbering them isn't as time consuming as you'd think them to be. Someone mentioned composition books, they're leatherless and inexpensive.

OP here. This is a pleasant surprise, I woke up this morning and saw the title and for a split second thought someone wrote the exact same post as me!

Reading the comments on here and reddit, it seems to me there are two different motivations: getting thoughts on paper vs. having a trail for future reference. Pen and paper is great for the former, which is my primary motivation.

I highly recommend you try the paper approach at least for a week to see if it helps you. Its is a hassle switching gears from keyboard to pencil, but it helps a lot. I did try various programs, but it never felt personal enough for me. Maybe its just me.

Wow, pry and its plugins universe gets better each day.

If you're new to pry I recommend you check pry-remote & pry-debugger.