File system equivalent of commenting code
Last week I came across what I have decided is the file system equivalent of commenting out code - not deleting directories when we are no longer using them.
The specific situation we ran into was while trying to make some Tomcat configuration changes but everything we changed was having no effect on what we were seeing on the web site.
Eventually we realised that we were actually changing the configuration in the wrong place - we actually had two Tomcat folder lying around. One for Tomcat 6 and one for Tomcat 5.5. We are running the former but were changing the configuration for the latter by mistake!
Of course the underlying problem was that we weren’t paying enough attention to what we were changing, but if there had been only one possible place to make changes then we wouldn’t have had a problem.
Lesson Learned: Treat the file system like the code - if something is not needed delete it straight away. It can always be retrieved from source control in the future if it’s actually needed.
About the author
I'm currently working on short form content at ClickHouse. I publish short 5 minute videos showing how to solve data problems on YouTube @LearnDataWithMark. I previously worked on graph analytics at Neo4j, where I also co-authored the O'Reilly Graph Algorithms Book with Amy Hodler.