R
Richard Twitchard
twitchard.github.io · Personal blog · on HN since 2019
Richard Twitchard writes essays on software development, process, and system dynamics, questioning data-driven approaches in favor of good arguments.
What HN saysHN links it in discussions of explanation and evidence in software, where commenters push back on how data relates to good theories.
16HN people shared it
2linked it in comments
28stories submitted
707story points
5 months agolast shared
2019people per year2026
Most-shared posts
- 1Be good-argument-driven, not data-driven3 people · 477 points · first shared 2022 · 161 comments on HN
- 2Software Development and the False Promise of Science3 people · 4 points · first shared 2019 · discussion on HN
- 3Not Mysticizing System Dynamics2 people · 127 points · first shared 2022 · 74 comments on HN
- 4Glamorize Your Problem Domain2 people · 7 points · first shared 2022 · discussion on HN
- 5Against Process2 people · 6 points · first shared 2020 · discussion on HN
- 6If Software Teams Were Proof Engines2 people · 5 points · first shared 2020 · discussion on HN
- 7Pushing the Boundaries of Streamlit2 people · 3 points · first shared 2024 · discussion on HN
- 8Not a real engineer (2019)1 people · 42 points · first shared 2023 · 2 comments on HN
- 9Breaking Changes: A Tooling Problem1 people · 13 points · first shared 2024 · discussion on HN
- 10P(user-hostile trash heap)1 people · 4 points · first shared 2025 · discussion on HN
- 11Beware Middleware1 people · 3 points · first shared 2019 · discussion on HN
- 12The worst thing about Jenkins is that it works1 people · 3 points · first shared 2023 · 2 comments on HN
- 13Please, Systematically Enforce Your Constraints1 people · 2 points · first shared 2021 · discussion on HN
- 14MCP: REST Reborn?1 people · 2 points · first shared 2025 · discussion on HN
- 15The Catholic Church vs. the Turing Test1 people · 2 points · first shared 2025 · 6 comments on HN
What HN people wrote when they linked it
jasode · 2022-09-01
>A simple answer to this is that good explanations are hard to vary.
But the "hard to vary" explanations were built up from observing data of smashing particles. E.g. from your link:
- Frank Wilczek describes hard-to-vary-ness as follows "A theory begins to be perfect if any change makes it worse." He explains further using the Standard Model as an example of a hard-to-vary explanation: Too many gluons! But each of the eight colour gluons is there for a purpose. Together, they fulfil complete symmetry among the color charges. [...] No fudge factors or tweaks are available.
This author's blog post about "data" also links to his previous post[1] about "science" leading one astray from "good arguments" is the opposite of "hard to vary" explanations.
Here's the reason for the disconnect: The author is using the adjective "good" in his idiosyncratic way to describe the type of arguments that depend more on "storytelling" and "intrinsic motivation" -- rather than empirical science/data. Excerpt:
- >And here is a secret: in the natural sciences themselves, storytelling and bare conjecture are far more important modes of persuasion than data-based empirical argument, anyway. [...]
- >A good example of the sort of argument I think is helpful is A Philosophy of Software Design. Ousterhout defines his terms clearly, accompanies his definitions and claims with illustrative examples, and tells an occasional story. You, the reader, are free to evaluate each claim based on…
twitchard · 2026-05-27
Fwiw the teaching of the church is that (today's) AI isn't at a human level because human intelligence is something that we experience whereas artificial intelligence seems to be merely a sophistication in performing tasks.
This week's encyclical didn't go into this. Last year's "Doctrinal Note" (less authoritative) did though: https://www.vatican.va/roman_curia/congregations/cfaith/documents/rc_d…
and I did a write-up on it here: https://twitchard.github.io/posts/2025-06-28-the-catholic-church-vs-th…