I had a feeling the author would be a Ruby programmer. It feels like the Ruby community exists in two wildly different camps: - One like that of the author, w

I had a feeling the author would be a Ruby programmer. It feels like the Ruby community exists in two wildly different camps: - One like that of the author, where there's an emphasis on programming as an artistic/creative endeavor (see also: why) - One that instead emphasizes seriousness and sternness, often coupling Ruby and Rails tightly at the hip In both of the cases where I worked for Ruby development shops (one consultancy and one SaaS vendor), the dominant culture was very much the latter, and yet I always gravitated toward the former. I recall mentioning reading stuff like why's Poignant Guide to Ruby early in my career and getting responses from coworkers along the lines of "ugh, really?", and I was always left baffled.