Josian Chevalier
@josianchevalier.bsky.social
Software Crafter @ Shodo.io, DDD practitioner
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".
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.
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.
Software development mostly falls into the "Complex" domain of the Cynefin:
- Software is built by socio-technical systems, which are inherently complex
- Organizations don't exist in isolation, so the software must adapt to global changes.
- Setbacks can arise at any point, from any tool.
- Software is built by socio-technical systems, which are inherently complex
- Organizations don't exist in isolation, so the software must adapt to global changes.
- Setbacks can arise at any point, from any tool.
November 23, 2024 at 1:30 PM
Software development mostly falls into the "Complex" domain of the Cynefin:
- Software is built by socio-technical systems, which are inherently complex
- Organizations don't exist in isolation, so the software must adapt to global changes.
- Setbacks can arise at any point, from any tool.
- Software is built by socio-technical systems, which are inherently complex
- Organizations don't exist in isolation, so the software must adapt to global changes.
- Setbacks can arise at any point, from any tool.
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.
Using hexagonal architecture, we can implement the persistence layer of this new domain to proxy calls to existing contexts, treating them as remote data stores. This ensures both the legacy system and the new context remain in sync.
November 16, 2024 at 8:54 PM
Using hexagonal architecture, we can implement the persistence layer of this new domain to proxy calls to existing contexts, treating them as remote data stores. This ensures both the legacy system and the new context remain in sync.
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.
“A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it.”
― Frank Herbert, Dune
(1/8)
― Frank Herbert, Dune
(1/8)
November 10, 2024 at 7:11 PM
“A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it.”
― Frank Herbert, Dune
(1/8)
― Frank Herbert, Dune
(1/8)
Most features I built in my career were nearly useless and brought no value to the final user. It takes time and maturity to understand that user stories and requirements are only a value hypothesis.
Only the feedback from production can confirm or contradict that hypothesis. (1/2)
Only the feedback from production can confirm or contradict that hypothesis. (1/2)
November 9, 2024 at 11:38 AM
Most features I built in my career were nearly useless and brought no value to the final user. It takes time and maturity to understand that user stories and requirements are only a value hypothesis.
Only the feedback from production can confirm or contradict that hypothesis. (1/2)
Only the feedback from production can confirm or contradict that hypothesis. (1/2)