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 Right Tools for the Job
Tool-building is an essential but poorly incentivized component of academic geography and social science more broadly. To conduct better science, we need to
build better tools.
A representational tension
Do I need to know the precise polygonal geometries of Los Angeles and the University of Southern California to assert that the latter is within the former? No. My mind contains no such precise geometric model of points and lines, yet I know that USC is in Los Angeles. When humans reason with the real world, they focus on its objects, relations, and processes—rather than starting with geometry—because these are the keys to understanding and explaining the real world. Our GIS tools, however, usually do the opposite. Built from the geometry-up around the legacy logic of traditional cartography (geometries and layers), most GIS tools today are restricted by that legacy’s limited ability to model objects, relations, and processes. A representational tension thus exists in GIScience between being a geometric information science versus an ontological, relational, and processual information science.
The teleology of tool-building
The teleology of tool-building suggests that the real value lies in the end use of the tool, rather than in its origins
Urban form and grain
One square mile of different cities' street networks, held at the same scale to compare the urban form and grain.
Software often feels inevitable
Software often feels inevitable because its backstory is often invisible. We click a download link, run an installer, and suddenly have a new tool to use. Yet this conceals years of human decisions, experiences, and constraints shaping software outcomes that are in no way pre-destined.