miniblog.

← Back to all posts
Apr 8, 2017 at 00:04
Thinking the unthinkable What we cannot think in programming https://tomasp.net/blog/2016/thinking-unthinkable/ (which questions we ask matters)
Thinking the unthinkable: What we cannot think in programming
Thinking the unthinkable: What we cannot think in programming
Our thinking is shaped by basic assumptions that we rarely question. As described by philosophers of science, research paradigms determine how scientists approach problems and what questions are accepted as valid scientific theories. In this article, I try to discover some of the hidden assumptions in the area of programming research. What are assumptions that we never question and what might the world look like if we based our design method on different basic principles?

Related Posts

Jun 2, 2025 at 22:31
12
There are docs resources like https://diataxis.fr/ that categorise documents based on format and intended audience. They don't say where you should start, or what order you should write docs. I'm currently thinking README > reference > tutorial > how-tos. Agree/disagree?
Diátaxis
Dec 22, 2024 at 22:34
On thinking of books like software, treating them as evolving artifacts, and URLs versus paper book publishers:
Shriram Krishnamurthi: Books as Softare
Mar 18, 2024 at 15:22
Thinking more about the "auto eval definitions" approach, I think it breaks down when debugging. If I want to step through the existing definition, it'd be really awkward to re-evaluate the definition at my cursor.