Restoration, Renewal, Recovery
Ending is better than mending
Kanawa-tsugi
When our tools are broken, we feel broken
I could do better than that
No ordinary objects
Responsibility for the sidewalk
I'm sorry, I love engineers
Repair
Little by little
Crafting repair
Hyperart: Thomasson
Snipping the dead blooms
Builder Brain
Rethinking Repair
Maintenance and Care
A time to build and a time to repair
Can maintenance save civilisation?
Makers and Making
Chesterton’s Fence
The McDonald’s Theory of Creativity
Imperfectly locked doors quietly waiting
Feature parity
The way we usually do infrastructure
Broken world thinking
Semi-detached houses, 2019
How the light gets in
A Quote by Leonard CohenThere is a crack in everything.
That's how the light gets in.The Maintainers
A WebsiteThe Maintainers, a global research network interested in the concepts of maintenance, infrastructure, repair, and the myriad forms of labor and expertise that sustain our human-built world. Our members come from a variety of backgrounds, including engineers and business leaders, academic historians and social scientists, government and non-profit agencies, artists, activists, coders, and more.
Software that nobody wants
Finding 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 'date scrum' anti-pattern
Date Scrum is an R&D pattern where developers are asked to estimate software project requirements upfront for the entirety of the project. After the project is green lighted and the budget is set based on the final estimates, the team then holds daily scrums to status and manage risk as they “iterate” the solution toward the release date. To some, this approach is described as doing Waterfall in sprints.
The fundamental problem with Date Scrum is that the team is de-focused from discovering the best solution. Instead they are heavily focused on delivering Something™ by the Date™. Engineers are problem solvers, and if the primary problem becomes delivering Something™ that will pass QA by the Date™, they will, with enough pressure, solve that exact problem.