A new article, this one about the application of Clausewitz's concept of friction to Software Engineering:

https://deadsimpletech.com/blog/friction_software_engineering

Understanding friction in software engineering | deadSimpleTech

That, in short, is how friction works in war: things start out organised, prepared and informed. Then the bullets start flying, and little by little, things go wrong and start to break apart. Co-ordination breaks down, people get tired and demoralised, and eventually what started out as a well-oiled, effective machine that was more than capable of achieving objectives ends up as a tired, worn-out blob that cannot fight any more or go any further. This seems simple, but as Clausewitz has it, "in war, everything is very simple, but the simplest thing is hard".

deadSimpleTech

@iris_meredith interesting how this article uses "tendency of unexpected things to start happening" as a holistic view on technical debt, brittle deployments, morale, death marches, engineering leadership, ...

And argues that not having awareness of that higher order concept prevents solving that higher order problem. Starting with naming it.

@iris_meredith Personally, I don't like using the word 'friction' for this concept. Because it already has a meaning that is different.

Which shows even in this article under 'friction as an ally'.
Eg. "adding Kubernetes to your stack should be a high-friction process"
The definition for friction in this sentence is back to the universal definition (~involuntary-slowdown-resistance) rather than Clausewitz's definition (tendency of unexpected things to start happening)

@iris_meredith for reference: 'friction as an ally'
The war defense stuff does not mix definitions. But the parts where describing applications to tech seems to describe positives of friction-slowdown-resistance rather than Clausewitz-friction-chaos.
- new feature requests
- introduction of new technologies
- adding Kubernetes
- hiring engineers

As I understand from the article, Clausewitz-friction-chaos (tendency of unexpected things to start happening) does not have upsides in a tech project.