Sorry, i don't want to injure any of the technical writers. They are the only guys keeping big projects from informational collapse. Moreover, they are some kind of project detectives, collecting clues about how this pile of * actually works.
But if you are making something, you have to make some pieces of human-readable information about it and the poor quality is significantly better that no internal documentation at all. That the way developer or manager can help real technical writer.
Also you can express your thoughts in short notes, schema drafts, checklists, documenting your mindflow. It's very usable and nearly impossible to delegate. You can steer at the lines and rectangles or lists, looking for missing points or removing redundant. Not hackworking, just harmonizing the details because it's odd to have time to polish shoes and no time to polish work.
But if you are making something, you have to make some pieces of human-readable information about it and the poor quality is significantly better that no internal documentation at all. That the way developer or manager can help real technical writer.
Also you can express your thoughts in short notes, schema drafts, checklists, documenting your mindflow. It's very usable and nearly impossible to delegate. You can steer at the lines and rectangles or lists, looking for missing points or removing redundant. Not hackworking, just harmonizing the details because it's odd to have time to polish shoes and no time to polish work.