chrishenn

This looks really excellent, I'm excited to try it out.

Good ol' Socrates :)

This resonates with me very strongly. But it seems all too easy to extend this sentiment towards others and remind them that they don't know what they're doing, which creates a pretty toxic environment.

The violin plots are cool and look like a great alternative to box plots, I had not seen those before. Sweet!

I've been working with Ember over the past few months and am still impressed with how simple and productive it makes every day tasks. Basic CRUD stuff, especially render code, is a lot less drudge work. I'm even more excited for where the community is leading the framework, through projects like ember-cli and htmlbars.

Ember is conceptually pretty massive though. A tutorial like Michael Hartl's Rails tutorial would be a huge benefit, it looks like that's what this is aiming for. Thanks!

I will soon, thanks!

One pain point I've really felt recently with Python is in the deploy step. pip installing dependencies with a requirements.txt file seems to be the recommended way, but it's far from easy. Many dependencies (such as PyTables) don't install their own dependencies automatically, so you are left with a fragile one-by-one process for getting library code in place.

It was all fine once I got it worked out but it would so much nicer to provide a requirements.txt file and have pip figure out the ordering and dependency stuff. That and being able to install binary packages in a simple way from pip would make me much happier with python (no more waiting 10 minutes for numpy or whatever to compile).

As far as actual language features go however, I still find python a joy to work in.

I've always wondered what coding is like for those who don't speak english, or only speak a little. I imagine it's something like working with code beatified by this tool.

Almost every codebase is filled with english verbs and nouns. They are one of the primary tools for making source code readable by humans, not just machines.

Very cool tool.

How do provisioning systems compare to Docker? Right now I have a development environment that consists of salt stack provisioning Vagrant. Spinning up a production server just means running salt on the host (Rackspace, DO, whatever.)

Is there any use for Docker in this case?

Hey krrishd, I also offer my help. It will be the most useful for front-end web design, or maybe some minor backend things.