change
What others want them to be
The subtlest slightest kinds of differences
Focus on the rate of change
When we hit our lowest point
Interlocking
Scales of change
A directional quality
A gradual refinement
All things change
The authors of this prognostication evidently assumed that the introduction of the sewing machine would result in more sewing – and easier sewing – by those who had always sewn. They would do the work they had always done in an unchanged setting. Reality turned out to be quite different.
It should be evident by now that there is no such thing as "just introducing" a new gadget to do one particular task. It is foolish to assume that everything else in such a situation will remain the same; all things change when one thing changes.
Ever, Never
EVER PRESENT, NEVER TWICE THE SAME EVER CHANGING, NEVER LESS THAN WHOLE
We change them and are changed
"We fill pre-existing forms and when we fill them we change them and are changed."
— Frank Bidart, Borges and I
How Buildings Learn
A Book by Stewart BrandBe A (Re)Visitor
An Article by Rob WalkerI was thinking about this not long ago while reading in Petapixel an essay by a photographer named Scott Reither, “Long Form Study: Why Photographers Should Repeatedly Revisit A Scene.” In it, he described photographing one particular stretch of beach, over and over, throughout his career.
Of course that landscape has changed over time, and of course he’s had moments when he felt he’d captured the same territory so many times there was nothing left to see.
But there was always something more to see — maybe because of a change in Reither’s life, rather than in the physical environment.
The Sheaves
A Poem by Edwin Arlington RobinsonWhere long the shadows of the wind had rolled,
Green wheat was yielding to the change assigned;
And as by some vast magic undivined
The world was turning slowly into gold.
Like nothing that was ever bought or sold
It waited there, the body and the mind;
And with a mighty meaning of a kind
That tells the more the more it is not told.So in a land where all days are not fair,
Fair days went on till on another day
A thousand golden sheaves were lying there,
Shining and still, but not for long to stay—
As if a thousand girls with golden hair
Might rise from where they slept and go away.Theory of Change
An Essay by Aaron SwartzA theory of change is the opposite of a theory of action — it works backwards from the goal, in concrete steps, to figure out what you can do to achieve it. To develop a theory of change, you need to start at the end and repeatedly ask yourself, “Concretely, how does one achieve that?”
When decades happen
A Quote by Vladmir LeninThere are decades when nothing happens, and then there are weeks when decades happen.
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.