korrents
Phil Hagelberg

What Phil Hagelberg thinks about design

@phil-hagelberg · 16 positions · On ppll ↗

Programmer known online as technomancy; author of Leiningen, the Clojure build tool, and a maintainer of the Fennel programming language.

Phil Hagelberg did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

Filter design · Newest first
Topic
All 16design 3developer tools 3JavaScript 2open source 2privacy 2software quality 2America 1behavioural science 1capitalism 1
6 more topics
compilers 1cybersecurity 1government 1Linux 1SaaS 1social media 1
Sort
NewestOldest

Only Phil Hagelberg on design. See everyone on design

3 dated positions, 2022, in their own words. Our reading of what Phil Hagelberg has said — not written or endorsed by them.

3 positions so far — this page is not yet offered to search engines.

  1. Our readingSoftware design that assumes text behaves predictably like English reflects the cultural bias of its typically white American developers.

    America

    Their wordsIn my opinion the root cause of this bug is that when a white american developer sees a terminal they immediately interpret it as this idealized cartesian plane where they can lay out any writing they want in neatly-spaced characters that behave in "predictable" ways (in other words, behave exactly like English).

    ↗in which the word column has several meanings, none of them architecturaltechnomancy.us 1st of 2 in this piece

  3. Our readingBecause programming requires forgetting, developers should weigh the costs of their abstractions and who those abstractions leave out.

    Their wordsProgramming, of course, is forgetting, but we need to at least try to be aware of the costs of the abstractions we choose and consider who it is that ends up being forgotten.

    ↗in which the word column has several meanings, none of them architecturaltechnomancy.us 2nd of 2 in this piece

  4. 5 months earlier

  5. Our readingNo single way of modeling data and methods in code is universally correct; every approach is just a set of trade-offs.

    Their wordsBut I do want to stress that each of these five approaches are all just trade-offs, and none of them are universally wrong.

    ↗in which five different paths lead to methodstechnomancy.us 2nd of 2 in this piece