programming

A great many wars have been fought over the religion of quality code. For who has not had a peer slain by the zealots of TDD? What programmer among ye has not spent longer than their heart desired on a pull request to DRY their code further? Who has not seen a code base lain asunder by the conquest of OOP?

Jack of all trades master of none.

Jack of all trades master of one?

Jack of all trades master of none... but often better than a master of one?

What the heck was the original quote, and why would learning more programming languages be helpful?

There is frequent discourse on how to make code more maintainable. I for one think more discussion is needed on making code deprecateable. It may be nice to envision that a beautifully designed code base will last forever, but there are two things certain for code; becoming legacy, getting deprecated, and off by one errors.

What does a spiritual practice, the hair maintenance of a Himalayan bovine and reviewing text editor config files have in common? Having long since solved my core productivity problems, what motivates me to continue to poke and prod my config file? It's not about optimization anymore.

Welcome brave reader. It's dangerous to go along without context. Take this pointer to the source of truth on GitHub.