"The greatest performance improvement of all is when a system goes from not-working to working" from [1]

"That which is not tied on will be lost" from [2]

"It should travel with all the things that it needs" from [3]

File:Wirfs-Brock and Wilkerson - 1988 - An Overview of Modular Smalltalk.pdf

They might never tell you it's broken

Code that doesn't rot

Drafts

Opinion

Tight coupling over fragile links is one of the industry's biggest problems right now. Tight coupling and fragile links are enemies.

WIP (or Works Not Started), in first person:

  • The case for the triple script module system
  • The case for accepting the W3C–WHATWG hypertext system as the universal medium, aka "Browsers, builds, and burdens"; basic thrust "The WWW is an acceptable NLS"
  • The case for object-functional programming

Notes

(NB: There's a reason why these pages are called "Notes" and live in my personal namespace. You are not expected to be impressed by or receptive to anything here. In fact, best not to even look at these. There's a whole wiki to peruse and interesting papers linked above, instead.)