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
Einmal Ist Keinmal
Jacked in
In digital design, products and services are frequently imagined and implemented placelessly: as if the consumer were jacked into The Matrix, and considering this product or that product from among an infinite set of choices at an infinitely-provisioned mercantile. The things we make are good, by this way of reasoning, if they fit the market’s demand.
Immer wieder
My attitude toward Alexander’s teachings prior to experiencing the places and spaces realized in his practice was akin to what Alan Watts said about certain teachings in The Bible:
Sometimes, as St. Paul pointed out, commandments are not given in the expectation that they will be obeyed, but in the expectation that they will reveal something to those who hear them.
Today, my answer is unequivocal. My interpretive lens: literal. Time and again, across cultures and continents and islands and oceans, in five different places now I’ve examined the evidence, and am persuaded.
Nicht nur einmal: immer wieder.
But what if it is?
Occasionally, one or two students out of sixty would take this task [of timeless thinking] up with some seriousness, and before too long would visit me in office hours to see if I could relieve them of their distress. They needed me to assure them that what Alexander says in his books isn’t…you know…real. For a number of reasons, not the least of which being the seeming incompatibility between how they’d been taught to think about design and what these teachings insist one must do in order to be, as they might say, “doing it right.”
And having never been to any of Alexander’s buildings, I’d simply turn the question around and ask “but what if it is real?”