> he already added unforeseen couplings that could get out of hands if it was a big codebase And one should be able to fix things that get out of hand when the

> he already added unforeseen couplings that could get out of hands if it was a big codebase And one should be able to fix things that get out of hand when they start getting out of hand. Architecture should be based on current facts, not on our fantasies about the future. For some reason we're always making this weird assumption that future engineers working on a problem are going to be less capable than us. So we decouple things in advance for them. Those future idiots won't know how to architect for scale, but we, today, with our limited domain expertise, know better. The reality is that in most cases we are those future engineers. And, unsurprisingly, "future we" tend to know more, not less.