Damian Płaza

@raimeyuu.bsky.social

Problem Solver/Solution Problemer. Engineer, baptized in control engineering. Passionate about people, software design, and modeling. Functional-first thinker.

Event Sourcing tests double as documentation. Given: [OrderPlaced, ItemAdded] When: RemoveItem Then: [ItemRemoved] This reads like a spec. It IS a spec. Your tests become the living documentation of your business rules.

The pendulum swung back! Now, the "modular monolith first" is the best advice. But is it? It sounds great in theory but can fall short in practice. In practice, too often: module boundaries erode, resource isolation is absent, and that promised "easy split" rarely happens. 1/