Reading Coraline’s post on a year at Github inspires a lot of feelings: feelings on behalf of a friend; feelings about culture; feelings about how organization structure always wins out over intent. But it also brings up some much more personal feelings.
On probably half a dozen different occasions some aspiring entrepreneur has asked me: Would you be interested in a hosted solution for selling screencasts? In most cases, the promised solution never goes beyond talk. In a few cases I’ve been sent invitations to beta test. In all cases, a successful business has failed to materialize, […]
Someone drew my attention a “leaving Ruby for Haskell” rant from a few years ago. I thought I’d reprint my reply here.
From time to time I have advocated for design approaches which value consistency and ease of change over raw operations per second. I realize that this strategy makes some programmers uncomfortable. So I thought I’d document some guidelines for optimizing your code.
A young developer newly embedded in the enthusiast programmer community could be forgiven for believing certain truths to be self-evident: that most people use Apple computers. That most websites are written in Ruby, NodeJS or Java. That most tech jobs are at Internet app startups. The truth is little different:
A developer notebook on applying classic Object-Oriented principles to Ruby on Rails projects.
