The majority of companies I’ve worked at have used Confluence. And the one thing you can be sure of is that any documentation you have written there will be hopelessly out of date.
I’ve been doing a lot of research on the cost of bad software documentation, and came across this paper by C. J. Satish and M. Anand. It’s a survey of various published works to indentify recurring pain points caused by bad documentation. One highlight: what happens when a developer leaves?
This is a post I wrote for the official Terrestrial.io blog a few weeks back. I’m posting it here too since I personally found the whole topic interesting and useful.
I'm Nik. I'm a software engineer with interests ranging from documentation, databases, distributed systems, web development, Rust, Elixir, Ruby.