planning
The Thing-deadline calculus
The best-laid plans
But bulldozers move mountains
Good design is redesign
Obsessed with absolute numbers
A warning against the limitations of my own prescriptions
The plan must anticipate all that is needed
Many a corner office
Individuals matter
Driving engineers to an arbitrary date is a value destroying mistake
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™.
Hofstadter's Law
An Idea by Douglas HofstadterIt always takes longer than you expect, even when you take into account Hofstadter's Law.
Planning doesn't make for better software
A Fragment by Robin RendleMy own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it.
Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me.
After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64.
Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way.
Yagni
A Definition by Martin FowlerYagni originally is an acronym that stands for "You Aren't Gonna Need It". It is a mantra from Extreme Programming that's often used generally in agile software teams. It's a statement that some capability we presume our software needs in the future should not be built now because "you aren't gonna need it".
Four principles
The essential purpose of Direct Management, as we understand the term, is to create buildings which are whole. This means that each part of the building is right in relation to the other parts, and to the part of the land that makes the buildings and the land more beautiful.
I will try to summarize the real meaning of Direct Management.
- The design evolves during construction. This means that the form of control over designs does not stop when drawings are finished, but goes on, continuously, before, during, and after construction. This cannot be done if architect and contractor are separate, or consider their jobs separately. It will only happen if the person who controls the design at the beginning actually controls the construction, too.
- Flexible cost control. Cost control requires continuous changing of ideas about what is built, in relation to money that is available, and in relation to what has been done already.
- Experience with one's hands. It is also impossible for an architect to have enough knowledge to control the process successfully, unless they have experienced almost every phase of construction with their own hands.
- Love of craft and the joy in the physical process of making. In the old days, making a building was clearly understood as a work of making. In this word, designing and physically building are inseparable. However, in the modern world, design has become separated from construction. Architects think of their work as designing, on paper, with the idea that the building process is a separate process. This is not what I call making at all. A good building can only be created, when it is deeply understood as something which is made, by a direct connection of the act of making, and the act of feeling, with your hands.