What is Macker good for?
Macker is a nice sanity check to keep your code matching all those boxes and arrows on the whiteboard, and prevent the architectural theory from unraveling in practice. It gives developers immediate feedback when they break conventions, and drives little mistakes and big architectural issues out into the open. When architectural rules don’t work, the problem prompts a group discussion instead of an obscure hack. If you’re designing for a project with a large number of developers, Macker is a great way to keep architectural principles from being diluted after release in the wild. All those people who weren’t in on that discussion at the whiteboard, and thus don’t necessarily have the whole picture in their head, will get a helpful nudge in the right direction when they go astray.
