[fitchb]

Chris: I've been following your work since I backed LightTable on Kickstarter. I just want to say congratulations and keep on truckin'.

I've been programming professionally for about three years. When I got my first job, I spent days setting up ruby/rails/zsh/vim/git. I was seriously dumbfounded. I could not believe that programmers (in 2011) actually worked this way. And I was even more perplexed that the main tools for reasoning about my code were print statements, browser reloading, and unit tests (so, so many unit tests). This is "the pain we forgot", except it's recent enough that I've never forgotten it.

Thanks for your work. I'm looking forward to a better programming for my kids. And hope to support any way I can.

[jdewald]

I prefer not to think of unit tests as a write to reason about the code you're writing now, but to let the system confirm that your current reasoning doesn't contradict with your previous reasoning (about other parts of the code).

[MoOmer]

For ruby, there's Pry [0].

[0]: http://pryrepl.org/