Most people treat documentation like a tax. Something you do after the real work, when you still have energy, which you rarely do. Then a problem repeats, a handover breaks, an automation attempt fails, or a new joiner gets stuck, and suddenly everyone wishes the work had been written down properly. This is the fundamental divide between reactive firefighting and proactive architecture...
