Winter Rant<p><strong>The Weekly: No Vibes in Manuals and Testing</strong></p><p><em>… also in this issue: <a href="https://rant.vpalepu.com/2025/04/28/the-weekly-no-vibes-in-manuals-and-testing#life-is-for-living" rel="nofollow noopener noreferrer" target="_blank">Sauce, SloMo</a> and some <a href="https://rant.vpalepu.com/2025/04/28/the-weekly-no-vibes-in-manuals-and-testing/#on-my-mind" rel="nofollow noopener noreferrer" target="_blank">stuff brewing in my mind</a>.</em></p><p>There is a scene in Die Another Day, where Q hands Bond a thick instruction manual for his new Aston Martin that comes with all kinds of guns and gadgets, and says, <em>“You should be able to shoot through that in a couple of hours.”</em> </p><p>Bond takes the manual tosses it in the air and the car’s motion-detecting machine guns fire the manual to bits. Bond then remarks, <em>“Just took a few seconds, Q!”</em></p><a href="https://youtu.be/ICmuFRBvPmk?si=Kg8ONqtdubMBlgul&t=85" rel="nofollow noopener noreferrer" target="_blank"></a><p>It’s a telling scene that betrayed a broader cultural attitude towards instruction manuals: no one likes instruction manuals. I grew up in a generation that tossed aside instruction manuals and instead just drove the machine, be it a car or a software application.</p><p>Manuals and handbooks were commonplace in the case of software for the longest time. But at some point people just stopped reading them. <em>Learn by doing</em> became the mantra around software. Running the program or software application first, to learn what it could (or could not) do, was the way to go. We all wanted to discover the application’s features ourselves without having to read through reams of text. Playing (or tinkering) with the app, especially for newly released software, came with a sense instant gratification.</p><p>Not sure when it happened but, slowly but surely the vibes around software manuals just vanished. Even if they came with the boxed software, or CD-ROM, people would typically just toss them aside. Of course, some folks would read them I suppose. IT Admins who manage enterprise software come to mind… as cohort of people reading these things; but that was because they were paid to do so. If you did not think that there was a need or requirement to read manuals, you skipped it.</p><p>It’s not like people got better at discovering features in software applications. On the contrary, I think tossing away the software manual created a new problem for software developers: feature discovery.</p><p>It is common to hear a software application’s end-users complain about missing features, while not realizing that the feature is already available and simply requires turning on a setting or configuration. Not discovering such settings in complex software applications became a direct consequence of software manuals falling out of fashion1. Collectively, humanity set aside a useful artifact for only one tiny benefit — we did not have to spend time reading. The practice of not reading manuals was a net loss. </p><p>Software Writer was a whole job category that just went out of fashion with those manuals. You see, writing anything, even software manuals, needs expertise and skill. But when you stop shipping those manuals, you do not need folks who possess such skills.</p><p>In fact, it gave rise to a subtler, invisible problem: software developers stopped documenting their code. If your users are not interested in manuals for the app’s features, then what’s the point in writing down notes about how the app works? Over time this became an anti-pattern that developer community recognized, and course corrected on. As an industry, I would argue that we have slowly come to recognize the value of maintaining documentation for software projects, esp. as wikis and open source software gained momentum. But still … do not expect anything but dirty looks when you ask a programmer to document their code. Writing is sadly not a dominant part of software culture at this point.</p><p><strong>I worry about another artifact losing its vibes much in the same way that manuals did: software tests.</strong></p><p>Software tests suffer from the same disdain that software manuals and documents do. You do not ship software tests to the end-user, so why bother writing and maintaining them? It’s not like we have figured out a better way to enforce software quality. Programmers are still shipping software with bugs. But just as with software manuals, we do not have good substitutes for software tests — we just rather not write them. And just like with job roles like Software Writer, roles around software testing is a dying job category. Startups and larger enterprises alike, question the value of a software tester.</p><p>Like with Software Writer, turns out that being a Software Tester requires skill and expertise. Writing test code is a fundamentally different skill than writing application code. I have seen some skilled programmers who are just plain <s>bad</s> <s>terrible</s> atrocious at writing software tests. They have the capability to stink up a whole room with their software tests2.</p><p>And like all things, AI is pouring gasoline on these problems. It’s a problem that predates AI, so I do not place primary blame on AI. That said, developers of all stripes are ready to generate documentation and tests without really caring if any of it is correct. We are setting fire to real value when it comes to software manuals and tests. I wish we could ship those artifacts to end users in a way that genuinely engages software users. It is a real problem.</p> <p><strong>Life is for Living: SloMo and Sauce</strong></p><p><em>Instead of rushing through life, I find myself standing still more than I used to. It has allowed me to notice life around me. And when not intensely private, I capture it with my camera.</em></p><p><strong>Pasta Sauce</strong></p><p>This weekend, I spent some time cooking. One thing I ended up making was a pasta sauce with tomatoes, garlic, basil, rosemary and thyme, lots of black pepper and salt. The wife loved it, thank goodness! Here is a snapshot of the ingredients just out of the oven, baked … right before I blended them.</p><p></p><p><strong>Water Dropping in SloMo</strong></p><p>I walk past this fountain ⛲️ almost every day. I like sitting next to it every so often. Recently I captured the water droplets in slow motion. The result turned out to be a satisfying ASMR video. <a href="https://vimeo.com/1079636451" rel="nofollow noopener noreferrer" target="_blank">Check it out…</a></p><p><a href="https://vimeo.com/1079636451" rel="nofollow noopener noreferrer" target="_blank">https://vimeo.com/1079636451</a></p><p></p> <p><strong>On my mind: anything but AI</strong></p><p>I realized that anything I think about lately is tainted by AI. Anything I want to write about has a profound AI-angle to it. I get that AI is everywhere. But not everything needs to be about AI. AI this, AI that. It started to become nauseating. I also found it to be intellectually lazy.</p><p>So, I took a break from writing and blogging last week and started thinking hard about things that are not principally about artificial intelligence. In fact, I am obsessed — both at work and in personal life — on how to best approach an issue without AI in the mix.</p><p>Don’t get me wrong: I think there are really cool applications of AI that I use everyday. But the best way to discover those cool applications of AI is to think hard about how to first approach something without AI. And I suspect that it is also a great way to<strong> keep the human in the loop at all times. </strong></p><p>It is a healthy exercise for me, mentally and intellectually. You will see me write more about things where AI is not the main character. I will still have my AI-rants and takes. But they will start featuring less over time.</p> <p><strong>footnotes</strong></p><ol><li>I have no data to back this of course. That is why this remains a blog called “Winter Rant” and not an academic publication 😁 ↩︎</li><li>I could write dissertations on this subject. ↩︎</li></ol><p><a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/cooking/" target="_blank">#Cooking</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/documentation/" target="_blank">#Documentation</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/james-bond/" target="_blank">#JamesBond</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/manuals/" target="_blank">#Manuals</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/slomo/" target="_blank">#SloMo</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/software-manuals/" target="_blank">#SoftwareManuals</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/software-tester/" target="_blank">#SoftwareTester</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/software-testing/" target="_blank">#SoftwareTesting</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/software-writer/" target="_blank">#SoftwareWriter</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://rant.vpalepu.com/tag/testing/" target="_blank">#Testing</a></p>