In Defense of Browsing An Essay by Leanne Shapton www.curbed.com The feeling of fortuitous gratitude at coming across unexpected information is something most of us who’ve done any research, have experienced — that kismet of finding the perfect book, one spine away from the one that was sought. In the field of art and image research, this sparking of transmission, of sequence and connection, happens on a subconscious level. …Why is the vernacular image still being dismissed as ephemera? Why is its study not being prioritized? All languages are alive, but visual language is galactic. Keywords are not eyeballs, and creating rutted pathways to follow is the antithesis of study. A century of visual language, knowledge, and connectivity is marching toward a narrow, parsimonious basement of nomenclature. The NYPL takes a step backward if it models its shelves and research on a search engine. Spontaneity is learning. Browsing is research. The art of finding what you didn’t know you were looking forMarginalia Search connectionresearchlanguageserendipitychance
Marginalia Search A Website search.marginalia.nu I want to show you that that Internet you used to go exploring is still very much there. There are still tons of small personal websites, and a wealth of long form text from both the past and the present. So it's a search engine. It's perhaps not the greatest at finding what you already knew was there, instead it is designed to help you find some things you didn't even know you were looking for. The art of finding what you didn’t know you were looking forIn Defense of BrowsingMillion Short micrositessearchdiscoveryserendipity
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