
On modularization
Assumed Audience Anyone who sorts their work into boxes, which is most people with a job. The second half gets into repositories and services, so it speaks most to engineers, architects, and whoever signs off on their diagrams. A recurring part of my work is (trying) to talk people out of splitting something up; a second repository, a separate service, sometimes even a whole separate team. The gist is always that the parts get presented/wishful-thinked as separate, yet in reality they’re still coupled, but now there’s a border, with all the overhead that requires. It happens so often that I wanted to do some research to figure out why. Why do humans split things? And why do they split more than is useful for the job at hand? ...