Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (79)

On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 The future is bright Mar 30, 2025 On luck and gumption Oct 8, 2023 Some thoughts on recent RTO announcements Jun 22, 2023 One size does not fit all: neither cloud nor on-prem Apr 10, 2023 Comparing AWS SQS, SNS, and Kinesis: A Technical Breakdown for Enterprise Developers Feb 11, 2023 Working from home works as well as any distributed team Nov 25, 2022 Things to be Thankful for Nov 24, 2022 Why you should question the “database per service” pattern Oct 5, 2022 Stop Shakespearizing Sep 16, 2022 Using GNU Make with JavaScript and Node.js to build AWS Lambda functions Sep 4, 2022 Why don’t they tell you that in the instructions? Aug 31, 2022 Monolithic repository vs a monolith Aug 23, 2022 Keep your caching simple and inexpensive Jun 12, 2022 Java is no longer relevant May 29, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Peloton could monetize these ideas if they only listen May 15, 2022 Best practices for building a microservice architecture Apr 25, 2022 True identity verification should require a human Mar 16, 2020 The passwords are no longer a necessity. Let’s find a good alternative. Mar 2, 2020 What programming language to use for a brand new project? Feb 18, 2020 TDWI 2019: Architecting Modern Big Data API Ecosystems May 30, 2019 Configuring Peloton Apple Health integration Feb 16, 2019 All emails are free -- except they are not Feb 9, 2019 Using Markov Chain Generator to create Donald Trump's state of union speech Jan 20, 2019 The religion of JavaScript Nov 26, 2018 Teleportation can corrupt your data Sep 29, 2018 Let’s talk cloud neutrality Sep 17, 2018 A conservative version of Facebook? Aug 30, 2018 On Facebook and Twitter censorship Aug 20, 2018 Facebook is the new Microsoft Apr 14, 2018 Node.js is a perfect enterprise application platform Jul 30, 2017 Design patterns in TypeScript: Factory Jul 30, 2017 Design patterns in TypeScript: Chain of Responsibility Jul 22, 2017 Singletons in TypeScript Jul 16, 2017 Architecting API ecosystems: my interview with Anthony Brovchenko of R. Culturi Jun 5, 2017 TDWI 2017, Chicago, IL: Architecting Modern Big Data API Ecosystems May 30, 2017 I tried an Apple Watch for two days and I hated it Mar 30, 2017 Emails, politics, and common sense Jan 14, 2017 Online grocers have an additional burden to be reliable Jan 5, 2017 Here is to a great 2017! Dec 26, 2016 Apple’s recent announcements have been underwhelming Oct 29, 2016 I am addicted to Medium, and I am tempted to move my entire blog to it Sep 9, 2016 What I learned from using Amazon Alexa for a month Sep 7, 2016 Praising Bank of America's automated phone-based customer service Aug 23, 2016 Amazon Alexa is eating the retailers alive Jun 22, 2016 In search for the mythical neutrality among top-tier public cloud providers Jun 18, 2016 In Support Of Gary Johnson Jun 13, 2016 Files and folders: apps vs documents May 26, 2016 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 JEE in the cloud era: building application servers Apr 22, 2016 Managed IT is not the future of the cloud Apr 9, 2016 LinkedIn needs a reset Feb 13, 2016 In memory of Ed Yourdon Jan 23, 2016 OAuth 2.0: the protocol at the center of the universe Jan 1, 2016 IT departments must transform in the face of the cloud revolution Nov 9, 2015 Banking Technology is in Dire Need of Standartization and Openness Sep 28, 2015 Top Ten Differences Between ActiveMQ and Amazon SQS Sep 5, 2015 We Live in a Mobile Device Notification Hell Aug 22, 2015 On Maintaining Personal Brand as a Software Engineer Aug 2, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 Attracting STEM Graduates to Traditional Enterprise IT Jul 4, 2015 The longer the chain of responsibility the less likely there is anyone in the hierarchy who can actually accept it Jun 7, 2015 Guaranteeing Delivery of Messages with AWS SQS May 9, 2015 The Clarkson School Class of 2015 Commencement speech May 5, 2015 Apple is (or was) the Biggest User of Apache Cassandra Apr 23, 2015 Ordered Sets and Logs in Cassandra vs SQL Apr 8, 2015 Exploration of the Software Engineering as a Profession Apr 8, 2015 What can Evernote Teach Us About Enterprise App Architecture Apr 2, 2015 Microsoft and Apple Have Everything to Lose if Chromebooks Succeed Mar 31, 2015 Where AWS Elastic BeanStalk Could be Better Mar 3, 2015 Configuring Master-Slave Replication With PostgreSQL Jan 31, 2015 Docker can fundamentally change how you think of server deployments Aug 26, 2014 Infrastructure in the cloud vs on-premise Aug 25, 2014 Things I wish Apache Cassandra was better at Feb 12, 2014 "Hello, World!" Using Apache Thrift Feb 24, 2013 Thoughts on Wall Street Technology Aug 11, 2012 Scripting News: After X years programming Jun 5, 2012 Java, Linux and UNIX: How much things have progressed Dec 7, 2010

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.