If we don't, your comment doesn't help, and therefore is nothing more than boasting about how you "get it".
So what is it about? Static typing? Acceptance of change in all things? Acceptance that code will always have flaws? Aging? Lisp code-is-data advocacy? How the difference between beginners and experienced people is as much slogging through grunt work as it is skill? How pragmatism wins over either strongly-for or strongly-against approaches?
A reference to Joyce, as younger Steve Yegge "begins to question and rebel against the Java and Ruby conventions with which he has been raised."? What?
The article is about being a pragmatic programmer. Know when to stop modeling, stop writing endless abstractions, and start writing code that does something. Don't model for the sake of modeling.
