At a uniformly comfortable termperature In America our tendency has been to get away from thermal conditions as a determinant of behavior. Instead, we have used our technology to keep entire living and working complexes at a uniformly comfortable temperature. As a result, our spatial habits have become diffused, and activities that were once localized by thermal conditions have spread out over a whole house or building. We forget, unless a system breaks down, that such wide-ranging use of space is extremely dependent upon the available heating and cooling equipment. Lisa Heschong, Thermal Delight in Architecture Controlled environments spacebehavior
Everyone sees themselves as behaving normally To understand why people act the way they do, we must first realize that everyone sees themselves as behaving normally. Eliezer Yudkowsky, Rationality: From AI to Zombies behavior
Architectural sequences Noted designer and architectural theorist Bernard Tschumi would call the predictable repetition of events inside an architectural space a sequence: a linear series of actions and behaviors that are at least partially determined by the design of the space itself. Geoff Manaugh, A Burglar's Guide to the City Architectural screenplays architecturebehaviorux
Contrafreeloading A Definition en.wikipedia.org Contrafreeloading is an observed behavior in which an organism, when offered a choice between provided food or food that requires effort to obtain, prefers the food that requires effort. workbehavior
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