Architecture

You know what architecture really is? It’s the art of drawing lines. With the interesting rule that once you have drawn the lines, all the dependencies that cross that line go in the same direction. A good architecture allows major decisions to be deferred … A good architecture maximizes the number of decisions not made. That rot will slow you down. It will slow the whole team down. [Read More]
rb 

Love your package manager

Notwithstanding that it’s wrong, as far as debian rubies go: Because going back to non-packaged non-vetted flavor-of-the-month code is a retrograde step back to 1993. You lose consistency, you lose the ability to reliably recreate a same environment, you lose tested and low-friction security updates, you lose dependency management, you lose the security of a crypto web-of-trust, and you lose the google-fu of being on the exact same versions of software as thousands of other people. [Read More]
deb  rb 

"Features are too big to fail"

[W]hen solving larger issues we have a higher tolerance for technical debt… That said, we probably shouldn’t throw caution to the wind and take on unlimited debt because we’re still paying back our last emergency loan. I know Aaron [Patterson] said that features are too big to fail. There’s nobody actually going to bail us out, though. Later: Your tolerance for debt is “features now + features later” over “cost now + maintenance. [Read More]
rb