🏞 The structure of JUnit

{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....

May 12, 2015 · 1 min · 94 words

📜 for each desired change, make the change easy (warning: this may be

for each desired change, make the change easy (warning: this may be hard), then make the easy change. Kent Beck

July 3, 2014 · 1 min · 20 words

📜 How many bugs and wasted CPU cycles and instances of human frustration

How many bugs and wasted CPU cycles and instances of human frustration (not to mention bad design) have resulted from that one small shortcut about 40 years ago? Keep that in mind next time you want to cut a corner in your code. Rob Pike (via A lesson in shortcuts. Long ago, as the design of the Unix… )

December 11, 2013 · 1 min · 59 words