Resonates. The concept is basically that written word may inspire or produce joy, but code is about producing results, so no results means no real value.<p>The part I like is bringing coding back to results.<p>But the comparison of "coding as results only" vs "writing as expression only" is a strawman.<p>Professional Writers write to earn a living, persuade, inform or entertain, probably choosing two or three of those as much as possible. If you don't have readers and you don't entertain persuade or make a living, your writing has failed by the same metric your Professional Coder's code has if it failed to solve the problem.<p>But in the personal / semi professional worked, writing for its own sake is called practice, as is coding for its own sake. Neither of those have intrinsic value, beyond learning, and if something good results, then sharing.