20 Minutes in Manhattan A Book by Michael Sorkin www.goodreads.com It begins with a trip down the stairsThoughts on stairsThey are something that has been buried(an architectural stem cell that might transform itself into any organ for living)The grid and its difficulties+41 More The MezzaninePsychogeographyTilted Arc architectureurbanismcitieshomewalking
Two Hundred Fifty Things an Architect Should Know An Essay by Michael Sorkin www.readingdesign.org The distance of a whisper.CornersWant, need, affordWhat the brick really wants.Borders+3 More 136 things every web developer should know before they burn out and turn to landscape painting or nude modelling architecturedesigncollections
Local Code: The Constitution of a City at 42º N Latitude A Book by Michael Sorkin www.goodreads.com The source code for SimCityLocal Code: 3,659 Proposals About Data, Design & The Nature of Cities regulationslawcities
Deadlines are bullshit An Article contrariantruth.substack.com 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 deadlinesWhy are internal deadlines evil?Engineers who love their work Hofstadter's LawThe Thing-deadline calculusNever enough timeDriving engineers to an arbitrary date is a value destroying mistake bureaucracysoftwareprocesswork
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. Building is never a straight line