I have a growing preference for systems that stay close to the person maintaining them. Not because complexity is evil, and not because ambitious tooling is always wrong. Mostly because a lot of good ideas die under the weight of setups that made sense in theory and quietly became chores in practice.
Writing is a good example. It is easy to borrow someone else’s platform and call the problem solved. For a while, that is a perfectly reasonable move. But eventually the trade becomes obvious. You get distribution, but the home of the work lives somewhere else. The archive belongs to someone else’s interface. The design language is borrowed. The relationship to your own writing starts to feel secondhand.
Simple can still be deliberate
I do not want to confuse simplicity with laziness. A small system still deserves structure. It still needs clear organization, good defaults, and room to grow. The point is not to avoid thought. The point is to avoid building machinery that asks for more maintenance than the work itself.
That is why I keep coming back to setups that are boring in the best way. One source of truth. One archive. One place to update. Pages that live where they are supposed to live. A workflow simple enough that adding the next piece feels like writing, not like managing infrastructure.
The test I trust
The test I trust now is whether I can imagine still using the system when I am busy, tired, or short on patience. If the answer is no, it is not a system yet. It is a concept drawing. The strongest setups are the ones that remove excuses. They do not ask for a perfect mood. They just let the work get published and stay organized afterward.
So the rule I am trying to keep is simple: start small, stay close, and only add machinery when the work itself proves it needs it. That applies to product work. It applies to writing. It probably applies to more of life than I want to admit.