Josian Chevalier
@josianchevalier.bsky.social
Software Crafter @ Shodo.io, DDD practitioner
Reposted by Josian Chevalier
My first @newcrafts.bsky.social was an absolute thrill!
Packed with enlightening sessions and vibrant discussions, what an experience!
Our talk on Model Tension Heuristics, co-presented with @josianchevalier.bsky.social drew fantastic feedback. Huge thanks for the support! 🤩
Packed with enlightening sessions and vibrant discussions, what an experience!
Our talk on Model Tension Heuristics, co-presented with @josianchevalier.bsky.social drew fantastic feedback. Huge thanks for the support! 🤩
November 7, 2025 at 7:04 PM
My first @newcrafts.bsky.social was an absolute thrill!
Packed with enlightening sessions and vibrant discussions, what an experience!
Our talk on Model Tension Heuristics, co-presented with @josianchevalier.bsky.social drew fantastic feedback. Huge thanks for the support! 🤩
Packed with enlightening sessions and vibrant discussions, what an experience!
Our talk on Model Tension Heuristics, co-presented with @josianchevalier.bsky.social drew fantastic feedback. Huge thanks for the support! 🤩
Reposted by Josian Chevalier
C'était un immense plaisir de jouer cette 20ème représentation de notre conférence sur Model Mitosis devant une salle comble lors de l'Agile Tour Bordeaux 2025 avec mon compère @josianchevalier.bsky.social !
Merci @racheldubois.bsky.social pour tes retours ainsi que la photo :)
Merci @racheldubois.bsky.social pour tes retours ainsi que la photo :)
October 31, 2025 at 12:36 PM
C'était un immense plaisir de jouer cette 20ème représentation de notre conférence sur Model Mitosis devant une salle comble lors de l'Agile Tour Bordeaux 2025 avec mon compère @josianchevalier.bsky.social !
Merci @racheldubois.bsky.social pour tes retours ainsi que la photo :)
Merci @racheldubois.bsky.social pour tes retours ainsi que la photo :)
Reposted by Josian Chevalier
All models are wrong, but some are useful. This insight from George Box has become a cornerstone of software modeling.
While exploration and experimentation are essential for shaping models, it is challenging to know when a model is wrong or when it has become obsolete. 1/5
youtu.be/EZTl9FH5AFQ...
While exploration and experimentation are essential for shaping models, it is challenging to know when a model is wrong or when it has become obsolete. 1/5
youtu.be/EZTl9FH5AFQ...
Model Tension Heuristics - Julien Topçu & Josian Chevalier - DDD Europe 2025
Domain-Driven Design Europe 2025 - Organised by Aardling (https://aardling.eu/)https://dddeurope.comhttps://newsletter.dddeurope.com/ https://be.linkedin.com...
www.youtube.com
October 13, 2025 at 6:52 AM
All models are wrong, but some are useful. This insight from George Box has become a cornerstone of software modeling.
While exploration and experimentation are essential for shaping models, it is challenging to know when a model is wrong or when it has become obsolete. 1/5
youtu.be/EZTl9FH5AFQ...
While exploration and experimentation are essential for shaping models, it is challenging to know when a model is wrong or when it has become obsolete. 1/5
youtu.be/EZTl9FH5AFQ...
Reading posts on linked in makes me realize that many people (specifically agile coaches) don't understand what we mean by "team autonomy".
May 27, 2025 at 1:51 PM
Reading posts on linked in makes me realize that many people (specifically agile coaches) don't understand what we mean by "team autonomy".
When I first heard of Cynefin and Wardley Maps, I felt like it was stating the obvious.
Some domains are less predictable than others, some technologies are less mature, and this should affect our decision process, not exactly groundbreaking.
Some domains are less predictable than others, some technologies are less mature, and this should affect our decision process, not exactly groundbreaking.
May 10, 2025 at 9:12 PM
When I first heard of Cynefin and Wardley Maps, I felt like it was stating the obvious.
Some domains are less predictable than others, some technologies are less mature, and this should affect our decision process, not exactly groundbreaking.
Some domains are less predictable than others, some technologies are less mature, and this should affect our decision process, not exactly groundbreaking.
Reposted by Josian Chevalier
🌟 Big news! 🌟
I'm thrilled to announce that @josianchevalier.bsky.social and I will present our talk on Model Mitosis for the very first time in the US at Explore DDD Conference in Denver (April 14-17)! 🇺🇸
I'm thrilled to announce that @josianchevalier.bsky.social and I will present our talk on Model Mitosis for the very first time in the US at Explore DDD Conference in Denver (April 14-17)! 🇺🇸
March 31, 2025 at 6:00 AM
🌟 Big news! 🌟
I'm thrilled to announce that @josianchevalier.bsky.social and I will present our talk on Model Mitosis for the very first time in the US at Explore DDD Conference in Denver (April 14-17)! 🇺🇸
I'm thrilled to announce that @josianchevalier.bsky.social and I will present our talk on Model Mitosis for the very first time in the US at Explore DDD Conference in Denver (April 14-17)! 🇺🇸
Reposted by Josian Chevalier
A massive thank you for all your incredible feedbacks on our talk, Model Mitosis: Stop making the wrong choice between microservices and monolith at @voxxedzurich.bsky.social with @josianchevalier.bsky.social
Check out our slides
slides.com/julientopcu/...
And our repo
gitlab.com/beyondxscrat...
Check out our slides
slides.com/julientopcu/...
And our repo
gitlab.com/beyondxscrat...
March 25, 2025 at 2:47 PM
A massive thank you for all your incredible feedbacks on our talk, Model Mitosis: Stop making the wrong choice between microservices and monolith at @voxxedzurich.bsky.social with @josianchevalier.bsky.social
Check out our slides
slides.com/julientopcu/...
And our repo
gitlab.com/beyondxscrat...
Check out our slides
slides.com/julientopcu/...
And our repo
gitlab.com/beyondxscrat...
Organizations are scared of change because they are scared of failure. Not all failure is catastrophic, safe-to-fail experiments are the best way to learn.
March 25, 2025 at 6:54 PM
Organizations are scared of change because they are scared of failure. Not all failure is catastrophic, safe-to-fail experiments are the best way to learn.
Reposted by Josian Chevalier
This year's VoxxedDays were really insightful ✨
If I could recommend one talk to watch on YouTube, it’d be «Model Mitosis» by @julientopcu.com & @josianchevalier.bsky.social. While it didn’t offer new insights (for me), it’s a great summary of the monolith vs. microservices approach 👏
#VDZ25
If I could recommend one talk to watch on YouTube, it’d be «Model Mitosis» by @julientopcu.com & @josianchevalier.bsky.social. While it didn’t offer new insights (for me), it’s a great summary of the monolith vs. microservices approach 👏
#VDZ25
March 25, 2025 at 5:04 PM
This year's VoxxedDays were really insightful ✨
If I could recommend one talk to watch on YouTube, it’d be «Model Mitosis» by @julientopcu.com & @josianchevalier.bsky.social. While it didn’t offer new insights (for me), it’s a great summary of the monolith vs. microservices approach 👏
#VDZ25
If I could recommend one talk to watch on YouTube, it’d be «Model Mitosis» by @julientopcu.com & @josianchevalier.bsky.social. While it didn’t offer new insights (for me), it’s a great summary of the monolith vs. microservices approach 👏
#VDZ25
Reposted by Josian Chevalier
Join @josianchevalier.bsky.social and I on Tuesday at 11:05 AM in Room 4 @voxxedzurich.bsky.social to explore a dynamic approach for iteratively splitting your business model, without getting tangled in spaghetti code or creating a dreaded “distributed monolith.”
March 24, 2025 at 7:00 AM
Join @josianchevalier.bsky.social and I on Tuesday at 11:05 AM in Room 4 @voxxedzurich.bsky.social to explore a dynamic approach for iteratively splitting your business model, without getting tangled in spaghetti code or creating a dreaded “distributed monolith.”
We commonly use the building construction metaphor to illustrate software development. But a software isn't a building, it's a garden.
December 26, 2024 at 9:40 AM
We commonly use the building construction metaphor to illustrate software development. But a software isn't a building, it's a garden.
Models are tools designed to solve specific categories of problems. Just as you can't replace a toolbox with a Swiss Army knife, you can't build effective software around a single model.
November 27, 2024 at 2:47 PM
Models are tools designed to solve specific categories of problems. Just as you can't replace a toolbox with a Swiss Army knife, you can't build effective software around a single model.
We don't work to get the best outcomes for our products. We work to stay busy. Sometimes, the best thing you can do is... nothing.
November 25, 2024 at 1:30 PM
We don't work to get the best outcomes for our products. We work to stay busy. Sometimes, the best thing you can do is... nothing.
The push to define processes in most companies stems from fear and the need for a false sense of control.
November 23, 2024 at 1:30 PM
The push to define processes in most companies stems from fear and the need for a false sense of control.
"Startups need to write code quick and dirty to find their market fit. Take on technical debt, and worry about paying it later. Software craftsmanship will come when the finances are stable."
November 22, 2024 at 3:35 PM
"Startups need to write code quick and dirty to find their market fit. Take on technical debt, and worry about paying it later. Software craftsmanship will come when the finances are stable."
The most valuable lesson I learned from working with @julientopcu.com is the difference between a model and its expression.
November 21, 2024 at 11:42 PM
The most valuable lesson I learned from working with @julientopcu.com is the difference between a model and its expression.
A good (socio-)technical architecture isn't one that anticipates every future evolution you can imagine.
November 19, 2024 at 1:30 PM
A good (socio-)technical architecture isn't one that anticipates every future evolution you can imagine.
In tech, we tend to reduce continuous self-improvement to technical watch.
November 18, 2024 at 1:30 PM
In tech, we tend to reduce continuous self-improvement to technical watch.
Socio-technical systems naturally evolve toward their most stable state.
This state is shaped by forces at play on this system. There are many types of such forces, including Conway's law, company culture, developer culture, automation, impedance mismatch between domain and tools.
This state is shaped by forces at play on this system. There are many types of such forces, including Conway's law, company culture, developer culture, automation, impedance mismatch between domain and tools.
November 17, 2024 at 1:30 PM
Socio-technical systems naturally evolve toward their most stable state.
This state is shaped by forces at play on this system. There are many types of such forces, including Conway's law, company culture, developer culture, automation, impedance mismatch between domain and tools.
This state is shaped by forces at play on this system. There are many types of such forces, including Conway's law, company culture, developer culture, automation, impedance mismatch between domain and tools.
Where did we go wrong with microservices?
Quite a few companies have gone bankrupt from the microservice hell, and countless developers are still drowning in it.
Quite a few companies have gone bankrupt from the microservice hell, and countless developers are still drowning in it.
November 13, 2024 at 11:22 PM
Where did we go wrong with microservices?
Quite a few companies have gone bankrupt from the microservice hell, and countless developers are still drowning in it.
Quite a few companies have gone bankrupt from the microservice hell, and countless developers are still drowning in it.
One crucial property to consider when designing a system is isolating parts that need to change frequently from those that have high change inertia.
By change inertia, I mean the effort required to make changes in a system.
#DDDesign
By change inertia, I mean the effort required to make changes in a system.
#DDDesign
November 12, 2024 at 11:54 PM
One crucial property to consider when designing a system is isolating parts that need to change frequently from those that have high change inertia.
By change inertia, I mean the effort required to make changes in a system.
#DDDesign
By change inertia, I mean the effort required to make changes in a system.
#DDDesign
"𝘞𝘪𝘵𝘩 𝘩𝘦𝘹𝘢𝘨𝘰𝘯𝘢𝘭 𝘢𝘳𝘤𝘩𝘪𝘵𝘦𝘤𝘵𝘶𝘳𝘦, 𝘸𝘦'𝘭𝘭 𝘣𝘦 𝘢𝘣𝘭𝘦 𝘵𝘰 𝘤𝘩𝘢𝘯𝘨𝘦 𝘰𝘶𝘳 𝘗𝘰𝘴𝘵𝘨𝘳𝘦𝘴 𝘵𝘰 𝘢 𝘔𝘰𝘯𝘨𝘰!" No one does that. Not one person ever. Okay, maybe a few. But honestly, what's the probability? Is it worth the efforts and overhead?
November 12, 2024 at 9:21 AM
"𝘞𝘪𝘵𝘩 𝘩𝘦𝘹𝘢𝘨𝘰𝘯𝘢𝘭 𝘢𝘳𝘤𝘩𝘪𝘵𝘦𝘤𝘵𝘶𝘳𝘦, 𝘸𝘦'𝘭𝘭 𝘣𝘦 𝘢𝘣𝘭𝘦 𝘵𝘰 𝘤𝘩𝘢𝘯𝘨𝘦 𝘰𝘶𝘳 𝘗𝘰𝘴𝘵𝘨𝘳𝘦𝘴 𝘵𝘰 𝘢 𝘔𝘰𝘯𝘨𝘰!" No one does that. Not one person ever. Okay, maybe a few. But honestly, what's the probability? Is it worth the efforts and overhead?
We use events in Event Storming for the same reason we use them in Event Sourcing. And the reason is not that it’s in the name.
Events are symptoms of unfolding processes. Processes are hard to capture directly, but events give us glimpses into them.
Events are symptoms of unfolding processes. Processes are hard to capture directly, but events give us glimpses into them.
November 11, 2024 at 8:58 PM
We use events in Event Storming for the same reason we use them in Event Sourcing. And the reason is not that it’s in the name.
Events are symptoms of unfolding processes. Processes are hard to capture directly, but events give us glimpses into them.
Events are symptoms of unfolding processes. Processes are hard to capture directly, but events give us glimpses into them.