“Software design is an exercice of human relationship” (here between sponsors and geeks-changers). @KentBeck at #newcrafts
Saying “we will now work on the Structure during 6 months and adding no new features in the mean time” is not helping the human relationship between the geeks and the sponsors. 😀
We need to maintain the relationship.
Programmers very often don’t have respect in their own work. A kind of ritual scaring (should be painful) 🤦♂️@KentBeck#newcrafts
Be careful: Moving the structure (refactoring) may be very addictive and seductive, but need diminution return.
(It’s comfortable cuz we don’t even have negative feedback from users like when we deliver a change of behavior). @KentBeck#newcrafts
The cost of Software is equivalent to the cost of change which is equivalent to… the cost of coupling.
- Lack of patience
- Seeking perfection (can be demotivating)
- Guilt-shame-despair
- I don’t know (we don’t trust our own ability-opinion
- No spears, no spikes
- No compassion
#CQRS is not a general purpose style of architecture.
A thread ⬇️
The first time I built a CQRS system… it was in 2006. The term hadn’t be coined yet by Greg (that happened in 2010), but the practice was ubiquitous in finance with tons of high throughput platforms to build or to maintain.
Actually, the first time I’ve used this architecture style was not due to my young skills of tech architect, but rather on a technical constraint.
M: Despite what people here are saying, they are very often long-lived. They last more than a day, more than a couple of days. Sometimes a week… When no merge conflict is detected at the end it’s ok.
Bad things happen when there is a merge conflict at the end of the day.
H: Yes, but is it that much painful? Aren’t branches our bread n butter?