How we do, what we do
Sign up to get posts via email,
or grab the RSS feed.
Since we published why we’re leaving the cloud, we’ve received a lot of questions about our actual spending. We’re happy to share, both where we currently are and where we’re going.
Active Record restates the traditional question of how to separate persistence from domain logic: what if you don’t have to?
When discussing software design techniques, actual code should be a mandatory ingredient.
Some of the best releases are ones that people never notice at all.
My hunch is that if anything can make you 10 times more productive, it’s the environment not the programmer.
An inside look at the work we do (during cooldown).
Long-running jobs can create maintenance and support nightmares as they run up against resource and time constraints. What if we could break them up—automatically—into smaller chunks of work?
A common critique of Rails is that it encourages a poor separation of concerns. That when things get serious, you need an alternative that brings the missing pieces. We disagree.