use case driven
banner
tpierrain.bsky.social
use case driven
@tpierrain.bsky.social
Change Agent (powered by software) now living in Lyon(France). Symmathecist & VP of Engineering in a booming scale-up (Agicap).Organizer of #DDDFR #AntiColonialist

https://medium.com/@tpierrain
+100 talks: https://github.com/tpierrain/me-myself-and-i
Nietzsche’s version of nihilism by @malk-zameth.bsky.social at #newcrafts
November 7, 2025 at 10:34 AM
Thanks for the tip @ldoguin.name 🙏
November 6, 2025 at 10:59 PM
We missed you, but it was nice (and we made some new acquaintances). Plus, we tried another excellent Turkish restaurant.
November 6, 2025 at 5:43 PM
Just arriving at home. Almost 11h30 from Berlin to Lyon this time 😄🤦‍♂️
October 24, 2025 at 12:06 AM
Reposted by use case driven
« When it’s complicated with the business, developers tend to focus on the technical part of the job instead of the business problem »
This is so on point!
October 23, 2025 at 12:48 PM
I would say go for #theHive pattern, it would help you to iterate at a cheaper cost while allowing you to go for a microservices version at any time if needed.

Here the rationale @julientopcu.com and I have made:
youtu.be/JZBsy6PsCRY?...
And here the live-coding version: youtu.be/VKcRNtj0tzc?...
The Hive: a scaling and supple architecture style - Julien Topçu & Thomas Pierrain
YouTube video by KanDDDinsky
youtu.be
October 22, 2025 at 4:39 PM
Take away from Sara which is comparing 3 ways of dealing with data consistency at #KanDDDinsky
October 22, 2025 at 1:29 PM
Explicit vs Implicit coupling.

We need to be aware when we introduce a new coupling between 2 overlapping decision models (in DCB).

#KanDDDinsky
October 22, 2025 at 1:25 PM
And tools/event stores are now supporting DCB
October 22, 2025 at 1:22 PM
Now Sara is warning us about some misunderstanding related to DCB, comparing static boundaries and dynamic boundaries.

#KanDDDinsky
October 22, 2025 at 1:21 PM
DCB is not an architectural style but rather a technique.
#KanDDDinsky
October 22, 2025 at 1:19 PM