If there's anything I've learned in a career of cleaning up other people's apparent development messes, it's that making assumptions about a codebase without having seen it is one of the big mistakes a developer can make. You (nor I, nor anyone but the owners) have no idea what sort of problems their codebase is designed to surmount, what kind of hardware they have to make do with, or the codebase's evolutionary history, or really anything about their back-end. Making those kinds of assumptions shows a sort of narrow "I know what I'm talking about enough to assume" mindset that makes me, a person unfamiliar with Tumblr, wary of the article as a whole.