> Build your monolith with clean hard edges between modules and functions so that it will be easier later, This is unfortunately very easy to override. Oh the

> Build your monolith with clean hard edges between modules and functions so that it will be easier later, This is unfortunately very easy to override. Oh the rants I could write. If I could go back in time we would've put in a ton of extra linting steps to prevent people casually turning private things public* and tying dependencies across the stack. The worst is when someone lets loose a junior dev who finds a bunch of similar looking code in unrelated modules and decides it needs to be DRY. And of course nobody will say no because it contradicts dogma. Oh and the shit that ended up in the cookies... still suffering it a decade later. *This is a lot better with [micro]services but now the code cowboys talk you into letting them connect directly to your DB.