Everything that uses configuration files should report where they're located
In my day job I do a lot of troubleshooting. That&#x27;s most of my job... helping other IT folks figure out what the heck is happening with something.<p>I&#x27;d say that in 70% of things I work on, part of that time is figuring out what config files are used because the app&#x2F;service&#x2F;process&#x2F;whatever is doing something the owner&#x2F;tech&#x2F;whatever doesn&#x27;t expect, yet is rational, and they &quot;didn&#x27;t tell it to do that&quot;.<p>It&#x27;d be great if everything reported as the article mentions -- amazing, in fact -- but I feel like it&#x27;s a pie in the sky wish. Like asking that all programs always exit cleanly or something. I feel like there&#x27;ll always be inevitable edge cases -- libraries that themselves pick up config files or registry values or environment variables that aren&#x27;t expected, who knows -- that&#x27;ll need to be discovered. If things are already not going right with a program, I&#x27;m less likely to trust what it says it&#x27;s doing and more likely to just watch it and see what it&#x27;s actually reading and doing.