Also available here
My regular readers are aware of some of my issues with my PI's time management skills. One particular issue is how long it takes him to give feedback on data and manuscripts. His approach is to immediately starting editing sentence by sentence, refining every detail, without reading through the overall paper.
Because he's a) busy and b) been busy so long he's got a backlog, this can mean that even if he's actually working on the paper (which is a whole separate can of worms), it can still be two months before you recieve *any* kind of feedback except by accident. Accidental feedback is things like while jetlagged, he mentioned that he was working on my paper, but the flow was rough. When I went and re-read it, my paragraphs were jumping all over the place like bunnies on speed, which is just how my brain seems to work. So I calmed the bunnies down, reorganized some thing and sent it back the next day. This apparently surprised him. I just thought it was the point of feedback...
This is also a problem because it means that he doesn't look at the data or conclusions until he's had the paper for quite awhile, and that's the feedback most of the students in my group are looking for. Does the model seem reasonable? Do the conclusions make sense? Are there more experiments/simulations I should be running?
When I'm editing for others, I usually try to read through once to get a feel for the overall flow, and then go back and start fixing the little things. I read absurdly quickly, so I find this technique rather helpful. It also gives me a chance to spot any big problems more quickly.
Editing my own stuff, I do it the other way around (since I already know where I'm trying to go). I have to take time away from the document before I can edit for flow, because otherwise my train of thought just follows the same tracks.
What's your editing strategy?