+1You should see my company's software manuals.... Manuals are surprisingly hard to make. When I did my obligatory engineering technical writing course at uni, it all looked so simple and straightforward, I was so wrong. FWIW, you need someone who is really good at it, and engineers who have 5-6 hours to spare to sit down with the Tech Writter...
Software manuals are nigh impossible to make. I freelanced to one telecom-software company for six months, endless aggravation of trying to herd cats. If you can get one techie to sit with you, there's five more that are revising the software code at their computers that makes null & void your present meeting with that one techie you miraculously cornered. Same thing happened when I was editing another telecom's proposal/tender to gov't for a new type of license...
I'd love to write a manual for an FX pedal, something that actually has a solid shipping date and a physicality that can't be revised between the morning's coffee break and lunch-time.
OT
Admittedly I'd mostly want to have good tracking, but I'd also love to stick the
