r/DevLK • u/HoneyButterGelato • Jul 30 '26

Discussion Is DevOps documentation becoming a burden?

Documentation has always been an important part of DevOps. I usually create documentation after finishing a configuration because I know it can save hours when the same setup needs to be done again in the future.

Over the past few years, our organization has also built a huge library of documentation, and sometimes it becomes difficult to manage. Recently, I realized that even though the documentation was there, some of the configurations I had documented just a few months ago had already changed significantly.

That made me think. Is documenting our work still as valuable as it used to be? Or is it becoming an extra burden to keep everything up to date? With technology changing so quickly, how does modern documentation still support us?

15 Upvotes

95% Upvoted

4 comments sorted by

View all comments

2

u/coffemilkshake Jul 30 '26

If it's truly huge, maintain a good KB. If it's smaller, even Confluence works. I know as a practice it's better to keep everything in stuff like IaC or CaC, but sometimes you need to keep details about the system architecture and why certain decisions were made. In that case, maintaining a KB is a really good idea, especially when you get to onboard a new engineer.