Owning the product: lessons from operating what you build
Why support, observability and small improvements compound into a better product than a long feature list.
Operation changes the design
Building a feature answers whether it can work. Operating it answers whether it is understandable, recoverable and worth keeping.
The best feedback is often operational: which step people repeat, which state needs explanation and which failure creates hesitation.
Keep the ownership visible
Every persistent file, scheduled task and external dependency should have a clear home. Ambiguous ownership is where small personal systems become expensive.
A concise runbook and a health check are product features when the same person builds, uses and supports the service.