unknown

A personal journey from basic programming to advanced architectural patterns. The author describes discovering Domain-Driven Design, learning to distinguish between entities, value objects, and services, then progressing to CQRS for separating read and write operations. The breakthrough came with Event Sourcing, which stores the complete history of events rather than just current state. Event Storming methodology bridges the gap between business and development by collaboratively modeling domains using events, transforming software development from isolated coding to shared understanding.

How my understanding of software changed

Welcome to PHP Dev, a dedicated space for sharing knowledge about PHP and its ecosystem (only PHP directly related).
Help us find good articles and blogposts and provide links. Upvote or downvote, after reading, it's essential

PHP Dev

Here is a reflection on how years of building and testing software have reshaped the way I think about code, quality, and what “good software” really means. If you have ever looked back at your own evolution as a developer, this one might resonate.

Here is a reflection on how years of building and testing software have reshaped the way I think about code, quality, and what “good software” really means. If you have ever looked back at your own evolution as a developer, this one might resonate.

I agree wholeheartedly with your article, Sebastian.
DDD really shines because it puts the domain front and center. This is the only thing that matters to non-developers, but developers tend to focus on the mechanics.
Ubiquitous language, event sourcing, bounded contexts, yada yada, is awesome and helps, but will only get you so far.
Event storming really makes it click with non-developers, provided the stakeholders and the culture surrounding the domain is ready for it.