notes · thoughts ·
Stronger tools, more judgment about what to add
Making code and interfaces easier does not decide what deserves to stay. I want to judge additions by whether they make the experience easier to understand.
The question after making becomes easier
AI tools make it easier to add features, screens and explanations. Less effort to produce them does not necessarily mean less effort to use or understand them. A feature brings another choice for a user to learn, and code remains something to read and maintain.
Before adding something, I want to explain how it improves the experience. Does it reduce a frequent task, clarify a confusing state or make needed information easier to reach? If the benefit is unclear, I can leave it out for now.
Removing things needs context too
Simplicity cannot justify every removal. In this catalogue, emphasizing selected work and making the other records inaccessible were different decisions. I can choose what readers see first while preserving a path to the full list.
Before removing an element, I need to examine who uses it, when they use it and which decisions become harder without it. Treating a smaller quantity as the goal can also remove useful context. Simplicity is closer to understanding what to do next than to counting what remains on screen.
Keep responsibility for judgment
Skills and automated checks help with execution. A passing check or a quickly produced design does not establish the value of a choice. I should be able to explain why a meaningful addition is needed and understand why the existing system took its current form before changing it.
Stronger tools make more options available. Choosing what to build and what to retain remains a matter of judgment. When a small change solves the actual difficulty, stopping there can be part of completing the work.