|
|
|
|
|
|
by halhen
4828 days ago
|
|
|
LaTeX and git. Granted, we're a small company with five people in the tech department, all working the terminal most of the time, so we can choose pretty freely. We're a B2B company. Having solid, continuously improved, and useful documentation to put on the table at the first meeting is a huge win in trust and efficiency. In my experience, the critical success factor is having someone in the team that truly cares about it. In our case, we had a guy whose peace of mind depended on having everything in order, including well-structured, complete, and correct documentation. He left us a couple of months ago, and already the documentation is starting to deteriorate. |
|
|
Entirely true. In my last job, I was that person. In my current job, I care about it, but in a sort of different manner. My personal documentation is great (or so I'd like to think), but I don't push for other people to post their documentation unless it's something they're trying to ask me to do by following the documentation.
As a result, documentation is sparse, even though they lament the lack of documentation for services.
You need someone who takes ownership for documentation. Whether it's a self-appointed task or a dedicated employee, if you're missing that you'll be missing documentation.