What is tool minimalism fewer tools more productive?

Tool minimalism fewer tools more productive is a concept in personal epistemology: Fewer well-chosen tools outperform a large collection of poorly integrated ones.

Example: A senior developer uses exactly five tools for her entire knowledge workflow: a plain text editor, a terminal, a browser, a notebook, and a version control system. A junior colleague uses twenty-three tools — separate apps for notes, tasks, bookmarks, read-later, highlights, calendars, project management, mind mapping, habit tracking, and more. When a new project arrives, the senior developer is writing code within ten minutes. The junior developer spends forty-five minutes deciding which tools to use, setting up integrations, and configuring dashboards. Over the course of a year, the senior developer ships three major projects. The junior developer ships one — and has a beautifully curated productivity stack to show for the difference. The senior developer is not more talented. She is more focused, because her tools do not compete for her attention. Her stack is small enough that every tool is deeply learned, fully integrated, and invisible during actual work. The junior developer is not lazy. He is fragmented, because his tools demand constant maintenance, context switching, and decision-making about which tool to use for which task. Fewer tools, deeply mastered, outperform a sprawling collection every time.

This concept is part of Phase 46 (Tool Mastery) in the How to Think curriculum, which builds the epistemic infrastructure for tool mastery.