Mateusz Nowak's wroclove.rb 2025 single-speaker talk. Frames DDD as 'might' (patterns/heuristics learned from books and talks) plus 'magic' (experience and intuition gained by practicing every day — even by modeling apps you use like Uber, and speculating about new features). Demonstrates a full application-design process on a Heroes of Might and Magic III creature-recruitment scenario: start with EventStorming (Alberto Brandolini) to harvest events with domain experts (available-creatures-changed, creature-recruited, creature-added-to-army, creatures-surrendered, combat-finished, etc.); identify business processes; then switch to Event Modeling (coined by Adam Dymitruk in 2018, originally 'single flow event storming') to draw processes like movie frames using commands (blue), events (orange), views (green), and properties — avoiding technical jargon like policies/aggregates. Uses the 'what happened before/after an event?' heuristic to find autonomous module boundaries (recruited creatures also join army, but surrendered creatures and battle outcomes also affect army — so those belong to separate modules joined only by an Automation). Explains slices: write slice (command→event), read slice (event→view), and automation slice (event→command), which enables parallel task-splitting for a team. Maps the model to code with three pure functions — decide (command + state → events), evolve (events → state), and react (event → command) — in a decider-style, persistence-agnostic Ruby sample that can be plugged into either event sourcing (events→evolve→state→decide→events) or snapshot storage (state→decide→events→evolve→state). Advocates translating given/when/then model specifications into tests, delegating the boilerplate to LLMs like ChatGPT. Ends by replacing code review with architecture review/execution during planning, citing modularity as a business capability (Heroes 5 duel mode shipped as a paid extension because the game was modular enough), and quoting 'it is not the expert's knowledge that is translated into code but the developer's understanding'. Closes with LinkedIn article series, QR code, and feedback survey.