Rails

I came to Rails in 2008 because I wanted a bare-bones web application framework that would allow me to 1) separate each layer of the development stack (HTML, CSS, JavaScript, the back-end) in development; and 2) combine these layers in a single app as I needed to.

Rails became my entry into the Ruby world. At first, it was both very satisfying and rather frustrating. Satisfying due to the good defaults, the DRY principle, emphasis on testing, and a large degree of developer freedom. (Not to mention an incredible developer community).

Frustrating because I'd rather know how things work than rely on "magic". But that is a whole other conversation - namely, Ruby...

In this category

  1. Are you process-oriented or product-oriented?