I do them carefully, labouriously, and with trepidation, and feel drained and tense after succeeding or failing at them, not to mention nervous while waiting to see how my efforts will be judged.
I feel that way about formal software testing. ("Formal" being the kind where you set up test situations and run situations looking for specific results, as opposed to the more informal "whack on it and see what breaks," at which I excell...) I haven't been doing it long enough to really feel confident about it, and there are a lot of things going on under the hood in the software I'm testing that I just don't understand, which makes things a bit difficult. I suspect the code itself is probably the least difficult part of it, believe it or not.
You are a very good writer, and probably a more-than-competent technical writer, whether you think so or not. I'd be happy to have you working as my "junior" on my current project, if that isn't too insulting. :)
(no subject)
I feel that way about formal software testing. ("Formal" being the kind where you set up test situations and run situations looking for specific results, as opposed to the more informal "whack on it and see what breaks," at which I excell...) I haven't been doing it long enough to really feel confident about it, and there are a lot of things going on under the hood in the software I'm testing that I just don't understand, which makes things a bit difficult. I suspect the code itself is probably the least difficult part of it, believe it or not.
You are a very good writer, and probably a more-than-competent technical writer, whether you think so or not. I'd be happy to have you working as my "junior" on my current project, if that isn't too insulting. :)