Archive

The Dulin Report

Browsable archive from the WordPress export.

2022

In most cases, there is no need for NoSQL Apr 18, 2022 TypeScript is a productivity problem in and of itself Apr 20, 2022 Best practices for building a microservice architecture Apr 25, 2022 Good idea fairy strikes when you least expect it May 2, 2022 If you haven’t done it already, get yourself a Raspberry Pi and install Linux on it May 9, 2022 Most terrifying professional artifact May 14, 2022 Peloton could monetize these ideas if they only listen May 15, 2022 Am I getting old or is it really ok now to trash your employer on social media? May 25, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Automation and coding tools for pet projects on the Apple hardware May 28, 2022 Java is no longer relevant May 29, 2022 Good developers can pick up new programming languages Jun 3, 2022 Scripting languages are tools for tying APIs together, not building complex systems Jun 8, 2022 Keep your caching simple and inexpensive Jun 12, 2022 All developers should know UNIX Jun 30, 2022 Monolithic repository vs a monolith Aug 23, 2022 Why don’t they tell you that in the instructions? Aug 31, 2022 Using GNU Make with JavaScript and Node.js to build AWS Lambda functions Sep 4, 2022 Stop Shakespearizing Sep 16, 2022 The Toxic Clique Sep 28, 2022 Book review: Clojure for the Brave and True Oct 2, 2022 Why you should question the “database per service” pattern Oct 5, 2022 Why I am a poll worker since 2020 Nov 11, 2022 If we stop feeding the monster, the monster will die Nov 20, 2022 Things to be Thankful for Nov 24, 2022 Working from home works as well as any distributed team Nov 25, 2022 Should today’s developers worry about AI code generators taking their jobs? Dec 11, 2022

Why don’t they tell you that in the instructions?

August 31, 2022

“Zen and the Art of Motorcycle Maintenance” by Robert Pirsig is one of those books that you either get or you don’t. It’s one of those works with a loyal following, and most people don’t get it.



I like to think that I get it.



I first read it back in 2000 while bicycling alone from Clarkson University to New York City on a soul-searching trip. One of my professors gave me a copy as a graduation gift. Since then, I must have re-read it in some shape or form at least a dozen times.



A recent conversation with colleagues reminded me of a scene in the book where the protagonist and his friend John park their motorcycles by a diner and go inside for lunch. When they come out, the sun is up, and the day is hotter. John follows the instructions booklet for his BMW motorcycle to the letter and struggles to start it:




I’m started and ready to go and there’s John pumping away on the kick starter. I smell gas like we’re next to a refinery and tell him so, thinking this is enough to let him know his engine’s flooded. 



“Yeah, I smell it too,” he says and keeps on pumping. And he pumps and pumps and jumps and pumps and I don’t know what more to say. Finally, he’s really winded and sweat’s running down all over his face and he can’t pump anymore, and so I suggest taking out the plugs to dry them off and air out the cylinders while we go back for another beer. 



Oh my God no! He doesn’t want to get into all that stuff.



“All what stuff?” 



“Oh, getting out the tools and all that stuff. There’s no reason why it shouldn’t start. It’s a brand-new machine and I’m following the instructions perfectly. See, it’s right on full choke like they say.” 



“Full choke!” 



“That’s what the instructions say.” 



“That’s for when it’s cold!” 



“Well, we’ve been in there for a half an hour at least,” he says. 



It kind of shakes me up. “This is a hot day, John,” I say. “And they take longer than that to cool off even on a freezing day.” 



He scratches his head. “Well, why don’t they tell you that in the instructions?” He opens the choke and on the second kick it starts. “I guess that was it,” he says cheerfully.



— Zen and the Art of Motorcycle Maintenance: An Inquiry Into Values by Robert M. Pirsighttps://a.co/9FWD5cc




Here is the thing. Software Engineering is a stochastic art. Programming is deterministic, but engineering is not. You may very well write your program to the exact specs, but you don’t know the conditions the code will run in. You may follow instructions to the letter, but if you encounter an edge case, will you know what to do?



The motorcycle manual can only account for so many things, and it cannot describe all possible permutations of riding styles, outdoor temperature, humidity, atmospheric pressure, rider’s weight, etc. The manual is only a starting point, but if you own a motorcycle, you need to know how the machine works to grok it.



The nature of our jobs as software engineers is such that we must deal with externalities. Hardware will crash. Services will auto-scale up and down. Garbage collection will occur. Humans will make mistakes and use our software in ways we did not anticipate. Someone will write configuration instructions for you on how to setup your dev environment, and they might not apply perfectly to your setup.



Grok your tools and your craft.