It's funny how things change. Smart ideas end up ruining everything. Quick hacks end up becoming established practice. How we've written Ruby has changed over the last fifteen years. We have this vague notion of "code quality", but what does that actually *mean*? Let's grab a whole bunch of Ruby projects, pick them all apart, and see what they say about making successful, lasting projects.
Sign in to add slides, notes or videos to this session