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
Sermon for WIAD Bristol 2021
The language itself has been weaponized
It’s quite difficult, to fight back against the seeming wisdom of axiomatic “truths,” when the language itself has been weaponized through the power of pattern. Through rhythm, rhyme, alliteration, and consonance.
The last time I was in England was at the invitation of Nomensa, to give a talk at a conference wherein I encouraged the audience to discard an axiom that I feel has done users of the English language more harm than good through endless and glib repetitions.
Like “Curiosity Killed The Cat,” “You Are Not Your User” sounds so good that we keep on saying it, without appreciating what we’re reifying through repetition. The pleasure of repetition, the pleasure of pattern matching, the pleasingness of Kuh Kuh Kuh consonants on the one hand, and of the round vowelly Yuh Yuh Yuh on the other make these things we say seem true because they sound and feel so good to say.
One Of Us
That’s the primary difference between an axiom like “Curiosity Killed The Cat” and an axiom like “You Are Not Your User. ” The former rings true in common experience. It’s test-able, like striking a tuning fork or dangling a bit of yarn in front of a kitten. The latter is just some stuff that somebody said.
Sometimes, axiomatic sayings like “You Are Not Your User” no longer have a who that’s saying them. They cease being an actual instruction, and instead serve as a kind of identity, to identify the person who’s repeating the axiom as One Of Us.
The technical term for when an axiom devolves into an ID card is shibboleth: a custom, principle, or belief distinguishing a particular class or group of people, especially a long-standing one regarded as outmoded or no longer important.
You and your user are one
In the case of the seeming egalitarianism and beneficence of the voice from the cloud that says “You Are Not Your User,” what I hear in that voice is the ringing of a cash register, and the creaking of the crank on the side of a box that software development efforts disappear into, and that money comes out of.
A mechanism that would seize up instantly if some still small voice were to propose the opposite of what the thunder says: that you and your user are one.