@DanielMezick @RonJeffries @beniamin80 @Huperniketes @KarimHarbott @rogersaner @tobiasmayer @arifbobat @mikeonitstuff @jemdjelal @martinfowler It's not binary. As @snowded said, imposition is the right thing to do in a few really rare cases (at an educated guess, Chaotic, or highly Disordered in favour of the predictable and about to become Chaotic if they don't stop). And some things *do* require governing constraints.
@DanielMezick @RonJeffries @beniamin80 @Huperniketes @KarimHarbott @rogersaner @tobiasmayer @arifbobat @mikeonitstuff @jemdjelal @martinfowler @snowded Someone once asked me for instance how I would use probes when decomissioning power plants. I told him I had no idea; if I have a nuclear explosion in the code base I just roll back. SW is inherently safe-to-fail; some industries might need different governance to others.
@DanielMezick @RonJeffries @beniamin80 @Huperniketes @KarimHarbott @rogersaner @tobiasmayer @arifbobat @mikeonitstuff @jemdjelal @martinfowler @snowded So I don't want to go down the "Imposition is always bad" route. I suspect there are better routes, like, "Transparency is usually good" and "Visualize stuff" and "Clarify your intent" and "Make fast feedback loops". Which are different, though aligned, to the Agile principles.
