Maintaining a good structure is a cost on its own. A good analogy is how most many engineers think "if I spend two days writing documentation then I'll save one hour figuring out things later, resulting in net gain of negative fifteen work hours, great job".
Software "Engineers" thinking about creating documentation and actually creating documentation? Where? Usually I find "engineers" trying to use new unrelated tech to create more work for themselves and the company. Like adding the AWS stack to an Azure firm. Or the overzelous "perfectionist" starting with way too much abstraction to solve a simple problem. Real engineers get certificates, but software "engineers" range from over-glorified PowerApps developers all the way to the people who program medical devices and other life/death-grade solutions. The former never thinks about documentation and the latter has most all documentation provided or automatically generated.
