building
It leaves no sign of its past self behind
Anasazi dwellings
If you want to build an outrageous building
The grid and its difficulties
A timeless space
Quaker Square Inn
The Timeless Way of Building
A Book by Christopher Alexander- Mind of no mind
- The quality without a name
- An objective matter
- Bitterness
- The most precious thing we ever have
How Buildings Learn
A Book by Stewart BrandBuilder Brain
An Essay by Charlie WarzelThe Builder mindset often eschews policy completely and focuses on the macro issues, rather than the micro complexities. It is a mindset that seeks to find very elaborate, hypothetical-but-definitely-paradigm-shifting, futuristic technology to fix current problems, instead of focusing on a series of boring-sounding and modest reforms that might help people now.
…The worst version of Builder mentality is that their dreams become reality, but instead of maintaining their creations, they simply move onto the next Big Thing, leaving others to deal with the mess they’ve made.
A time to build and a time to repair
An Article by Elizabeth M. RenierisThere is a time to build and a time to repair. Repairing what is broken is difficult and important work that requires contextualizing technology and working within creative constraints…If we just keep building without repairing what exists or applying lessons learned along the way, we will continue to spin our wheels as the same problems accumulate and amplify. In this way, our technology may evolve, but our relationship to it (and to each other) can only degrade.
The joy of the humble brick
An Article by Tim HarfordThe brick is one of those old technologies, like the wheel or paper, that seem to be basically unimprovable. ‘The shapes and sizes of bricks do not differ greatly wherever they are made,’ writes Edward Dobson in the fourteenth edition of his Rudimentary Treatise on the Manufacture of Bricks and Tiles. There’s a simple reason for the size: it has to fit in a human hand. As for the shape, building is much more straightforward if the width is half the length.
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.
Are We Really Engineers?
An Essay by Hillel WayneFollies
A DefinitionFolly at Hagley Hall, Hereford and Worcester, built by Sanderson Miller, 1749–50
In architecture, a folly is a costly, generally nonfunctional building that was erected to enhance a natural landscape. Follies first gained popularity in England, and they were particularly in vogue during the 18th and early 19th centuries, when landscape design was dominated by the tenets of Romanticism. Thus, depending on the designer’s or owner’s tastes, a folly might be constructed to resemble a medieval tower, a ruined castle overgrown with vines, or a crumbling Classical temple complete with fallen, eroded columns.
On the "Building" of Software and Websites
An Essay by Dorian TaylorI’m beginning to suspect that software, and more conspicuously the Web, is fundamentally the wrong shape for the archetype of the construction project.
Deadlines are bullshit
In software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
External vs. internal deadlines
When are deadlines necessary?
- Contractual obligations
- Technical liabilities (e.g., dependency EOL)
- Compliance, government, investors, and other external stakeholders
What do all of these deadlines have in common? They are all important. They are all deadlines that cannot be missed. They are all external.
When are deadlines evil?
- Your manager says you have a deadline
- Your software development methodology says you have deadlines
What do all of these deadlines have in common? None of them are important. They are arbitrary. They are all internal. They are all bullshit.
Why are internal deadlines evil?
- Estimation: When estimating engineering work a substantial time investment is required by an engineer in order to get an accurate estimate.
- Misaligned Incentives: There is an incentive to lie and give estimates much longer than the feature is truly expected to take.
- Low Morale: Deadlines are likely to be missed often. Repeated failure has a cost to the morale of the team.
- Micromanagement: Deadlines are wielded by middle managers as a whip to harass and annoy engineers working on features.
- High Stress: When engineers feel the pressure of other stakeholders holding deadlines over their heads it creates an environment of high stress.
- High Turnover: On teams with high turnover rates the best engineers have an easy time finding new work and leave quickly, the worst engineers have a difficult time finding work and remain. This selects for a lower quality team over time.
Engineers who love their work
The resolution is simple. Never have internal deadlines. Operate on a prioritized and ordered list of features. Estimate only when necessary to prioritize and do so in a t-shirt sizing way. Trust your engineers and they will begin to love their work. Engineers who love their work are happy and productive.