I thought quite a bit about this extension of Conway's Law, which is taking the flexibility of the system under change into account. Here are some unsorted and maybe random thoughts from my experience of doing an inverse Conway maneuver on a larger scale at Flix. #SoftwareDesign

https://twitter.com/mathiasverraes/status/1528756273012957184

Some context: in 2018 we were taking extreme measures to get a grip on our monolithic software system that had been growing dramatically over 6 years, going from 8 to ~170 devs and multiple million LOC. And yes, an inverse Conway maneuver (ICM) is an extreme social intervention.

There are so many different opinions about cost estimations in software, and many of these are rooted in estimates being used as measurements, targets or commitments. I want to clear up some misconceptions regarding estimations.

A thread 🧵1/n

#NoEstimates #ProEstimates The first thing we need are some definitions. One major driver of confusion are the various interpretations of the words "estimate" and "estimation".

An estimate is "an approximate calculation or judgement of the value, number, quantity, or extent of something". 2/n

I am more and more hooked on the idea of using message-driven finite-state-transducers as a mathematical model to describe #DDDesign Aggregates. This would enable automated determinism proofs, unions, concatenation, projections, and any other operation that is available for FSMs. A transducer is defined as a sextuple: (finite input alphabet / commands, finite output alphabet / events, initial state, finite set of states, state transition function (state, command) -> state / behaviours, output function (state, command) -> event). #DDDesign