Gien

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

Listen to “Communication patterns for engineers” on our @aardling@m.aardling.social YouTube Channel: https://youtu.be/oKdbQfqDolU (Also available on Spotify and Apple Podcasts.)

Only 20 days left until @newcrafts@mastodon.social. I will be talking about all things decision during the conference. I am very excited about this, a full 45min on decisions :-D At the end of my talk you will understand a decision a bit better, have some extra vocabulary to have discussions on how to make decisions in your company and you know how I applied decision-making theory to software design. I hope to see you there! https://ncrafts.io/

We often mock architects being in an ivory tower, making all the decisions, not listening to the software 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, one that fit the agile mindset software teams adapted to a long time ago. [1/2]

I am giving a talk and doing a workshop at #gsas25 (https://gsas.io) It is not too late to get your ticket! 13-15 October 2025 in Barcelona. Come find me :)

The way we think and the way we design our software systems is not aligned. In order to make that alignment better, we need to understand ourselves, our thinking, and the system we are currently in.
In this episode of Satisfying Software, I spoke with @diana@hachyderm.io on decisions, belief systems versus truth, and non-linear thinking.

Listen to “System Thinking” on our @aardling@m.aardling.social YouTube Channel: https://youtu.be/PQ7alnbdUp4 (Also available on Spotify and Apple Podcasts.)

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? Why is it worth designing an Event-Driven system? These are a few of the questions I discussed with @noctovis@hachyderm.io in our latest episode of Satisfying Software!

Listen to “Designing Event-Driven Systems” on our @aardling@m.aardling.social YouTube Channel: https://youtu.be/Ez1tZntKrJs (Also available on Spotify and Apple Podcasts.)

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@mas.to on the Tactical Patterns of Domain-Driven Design.
Listen to the episode via our @aardling@m.aardling.social YouTube Channel: https://youtu.be/kIsd9EUg5UI
Also available on Spotify and Apple Podcasts

This year is the 10th edition of @dddeu@m.aardling.social, and I wanted to share my personal journey during the next couple of weeks of this wonderful conference. This conference and the people organising it (spoiler alert, my colleagues) have been an important in my professional career for the past 10 years. So 10 seems like the right number to take a trip down memory lane. [1/3]

“How do we design our software system so that our teams can be autonomous?” is a very common question I receive during training or consulting. In this episode of Satisfying Software, I dig a bit deeper into team organization with @joaorosa@mastodon.social. He shares his ideas and opinions on questions like “what does it mean for teams to deliver value?”, and “what are some of the common mistakes made when organizing teams?”.