What is the thread?

It is the throughline of any blog post, essay, or book chapter.

1. The point
2. Setup
3. Reasoning
4. Exploration
5. The point

Start with the end in mind. What is the point? Write the title and the lede based on that.

Then, the setup. What is the problem? What is have I noticed?

Then, reasoning. Examples. Stories. Structures and frameworks. Subsidiary points.

Then some additional richness. How can you take the idea further? What are the unsuspected consequences?

And finally, the point again — but now with more knowledge and perspective, stated in a way that makes it stick.

{width=“562” height=“388”}

By version 4.11, transitive dependencies have proliferated seemingly unchecked. We are far from the short dependency-chains and few cyclic-dependencies of good structure.

A better way…

There are many ways to do this, but one way is to practice radial encapsulation . (…) shows the evolution of a radially-encapsulated program that is bigger than JUnit yet has throughout its history retained a structural clarity that JUnit seems to have abandoned.

{width=“562” height=“367”}

Programmers should be forced to wear their systems' package-structures on their tee-shirts.

(via The structure of JUnit – EdmundKirwan.com )

[technical