Gandalf Hudlow
The value-destroying effect of arbitrary date pressure on code
An Article by Gandalf HudlowThe mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™!
What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™.
Software that nobody wants
An Article by Gandalf HudlowFinding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
The Evolution and Fate of Botanical Field Books
To serve as a reminder
Looking back at my notebooks now, the information seems fairly sketchy, often abbreviated, and fairly uninformative. The purpose was merely to serve as a reminder for when, that evening, I would write up my notes in a proper field book.
Sterile creatures
Now that we are in the era of personal computers, traditional field books are being replaced by computer files. By default such “field books” are sterile creatures—all the words are spelled properly, the location data are exact to a matter of a few feet, and everything is properly formatted. In the spring of 1998, I penciled my last entry into my signature field book with the bright orange cover. Thereafter I have maintained a computer-based field book.
Oh, all the right stuff is there, clear, crisp and, well, dull… I tend to be overly particular about it—the format has to be right, everything properly spelled, the descriptive sequence in the proper order, and even the observations drafted with the final publication in mind (rather than what I happen to see at the moment). The emotions of finding something new, once mentioned in my handwritten field books, are now missing, as if my mental editor says “no, that is not proper for a scientific journal.”
Further and further away
In looking over my own forty-five years of keeping a record of plant specimens, I find that I am personally moving further and further away from the words I generate, becoming more aloof and separate from the experience of the actual event of collecting, concentrating instead on the precision of where and when. It is merely record keeping for the sole purpose of giving the facts.
With the decline of letter writing and the sterilization of field books, what we are losing is the individual. Field books are like letters that are replaced by often ephemeral emails. I fear that as we move further into the computer age we will similarly lose the detailed historical record that field books once provided. Sadly, the personalities of botanists will also be lost, for such musings as might be found in a field book are often telling to those wishing to know more of the past.