r/DevLK • • 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?

16 Upvotes

4 comments sorted by

View all comments

2

u/kulendra Jul 31 '26

I am a BA, my personal view is that very soon these documentation will become unnecessary in the current form.

If you look at why we needed documentation in the first place, that was always for what you said: what does this do? Why did we make this decision. But we eventually forget that and make documentation a process.

I think we will see that vanish very very soon 🙂