The drift The Situationists were also practitioners of a special urban-analytic walking style, the dérive—the “drift”—which Debord described as “a technique of transient passage through varied ambiences. The dérive entails playful-constructive behavior and awareness of psychogeographical effects; which completely distinguishes it from the classical notions of the journey and the stroll.” “In a dérive,” Debord deadpans, “one or more persons during a certain period drop their usual motives for movement and action, their relations, their work and leisure activities, and let themselves be drawn by the attractions of the terrain and the encounters they find there." The dérive joins the free association of surrealism, the LSD of hippiedom, and cinematic montage as tactics for overcoming the fixity of received ideas of order and logic. By putting progress through the city into a state of constant indeterminacy, it represents a schooled “style” of being lost. Michael Sorkin, 20 Minutes in Manhattan PsychogeographyRaindrops leaving an erratic trail psychologymovement
The axis of movement Moving in the city means constantly changing the axis of movement. In general, lateral movement is confined to a single plane, what’s called grade, the ground level. Because circulation in multistory buildings is fundamentally one way—which is to say from the bottom up—the condition at the top is invariably different from that at the bottom. Rooftop circulation is the domain of Fantômas, of cat burglars and fleeing criminals, of lovers, and of those acrobatic enough to negotiate the gaps between buildings. Michael Sorkin, 20 Minutes in Manhattan A Burglar's Guide to the City movement
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