Of course I'm not trying to provide the ultimate recipe to big IR problems on HN in 10 lines of text written on my phone :) Just wanted to say that communicati

Of course I'm not trying to provide the ultimate recipe to big IR problems on HN in 10 lines of text written on my phone :) Just wanted to say that communication patterns and specifically communication overhead can and should be reflected in modularization of software. If two people can talk to each other very easily (because they're sitting near each other) then maybe (!) separating their code through e.g. APIs doesn't need to be that strict compared to teams who never talk to each other in person. These are not hard rules, but good guidelines. (Modularization isn't for free, so there's always a balance.)