The way we think and the way we design our software systems isn't aligned. In order to make that alignment better, we need to understand our thinking, and the system we are in. In this episode, I spoke with @mentrix.bsky.social on decisions, belief systems versus truth, and non-linear thinking.

We often mock architects being in an ivory tower, making all the decisions, not listening to the developers, and not caring if they made the right architectural choices. What most of us failed to notice was that nobody was offering them a different process to make architectural decisions. [1/3]

What does it mean to be good at communicating? I have tried (and failed) to improve my communication in general because being to communicate your solutions is as important as the solutions. In this episode of Satisfying Software, I spoke with @tekiegirl.bsky.social on the communicating architecture.

Event-Driven systems come with challenges: How do we version our events? Can we only publish events in an Event-Driven Architecture? How do we test all of this? These are a few of the questions I discussed with @noctovis.bsky.social in our latest episode of Satisfying Software!

Which programming language works really well with Tactical Patterns? When should be involve our software developers? How to deal with something that is over or under modeled? In our second episode of Satisfying Software, I spoke with @tcoopman.bsky.social on the Tactical Patterns of DDD.

Software design is a discipline of uncertainty. We took principles and tools from disciplines of certainty into a discipline of uncertainty and we are surprised when hell breaks lose. On our 1ep of Satisfying Software, I spoke to Barry O’Reilly on finding a better way to architect software system.