So tech-writers spend a long time worrying all about unimportant things. And they bother programmers and managers with pointless things. But they're necessary things. Otherwise why would you be employed. Perhaps the absence of simple reasoning short circuits their brains. Who understands?What we are able to get free from this is that there is a sensation that tech-writers spend time, and consequently, they're more or less at the bottom of the heap in the software world. I think a good example is just how some wealthy see the poor. Dirty little creatures... if only we could do without them...
But there's an up-side. I don't want you https://digitogy.eu/de/ it's all bad.Being at the bottom of the heap has its advantages. You are able to move undetected for decades in the event that you want. If you have not observed the movie, Company Room, you must hire it. There exists a small ferrety bloke in that who had been "release" years ago. Problem is, no-one ever told him, and due to a glitch in payroll he still got paid. No-one actually noticed.Being a tech-writer's a bit like that.
When I was handling doco clubs, my favourite expressing was "All we have to do is manage their expectations and our commitments ".Since programmers and managers decide themselves to the fact that they don't really know what's going on in the doco team, there's often a temptation to slacken off. Do not surrender to the temptation!!! In the event that you actually get found, carrying it out, it'll end up like the child who cried wolf - they'll never believe your estimates again!Another risk is that you'll eliminate your feeling of urgency. And that's a big section of why is a good worker. You should be really strict about controlling your commitments. This involves discipline, since occasionally it appears you are the only one that cares, however, you have to do it.
Something you ought to be alert to nevertheless, is your normal tech-writer in pc software uses no more than 50% of their time writing. The rest of your own time is used preparing, problem solving, solving your computer, exploring, interviewing the programmers, writing work pracs...I always discovered it was a good balance, though.It was when I began controlling teams that the underside really dropped out. Then the percentage dropped to about 10-20%. There have been occasions when I'd move months without writing any help at all. That can be very frustrating, particularly if you don't especially like managing.
Now handling tech-writers in software is an interesting thing. As with most technology management roles, you kinda belong to it, since you're the most senior/experienced person in the company. Regrettably, that doesn't qualify you to be always a manager. Computer software companies are famous for dumping people into management tasks without the actual training or support.I don't obviously have any guidance for you here. If it's gonna happen, it will happen. Only be familiar with it, and know that if you belong to a management position, it's gonna be difficult. (That's not to imply so it can't be rewarding though...)
