21–30 of 44 posts
I'm curious: what is your way of flagging typos or bad grammar to colleagues? I often just do it without much fluff around it, but sometimes some people think that's harsh or nitpicky, but I really don't think anything bad about them while doing so. Any advice? BTW I'm talking about documents/tickets, not in chats or internal mails or something
It's nice and makes it their decision.
Which is why reading text backwards can help to find typos, or so I've heard. (Typos tend to jump out at me, even in my own writing.)
Because the solution is hidden behind "subscribe to wired to keep reading"! I find reading the text back in a different font often helps, particularly switching from mono-spaced to variable or vice-versa, though I'm not sure why. Perhaps I remember the shape of the words as correct because that is what I just typed, and when all the words have a different shape I'm forced to think about it differently. It is why I of…
> I find reading the text back in a different font often helps, particularly switching from mono-spaced to variable or vice-versa, though I'm not sure why. A related technique I use with LaTeX documents is to proofread the output PDF. Of course, that only works if you use LaTeX or similar.
I'm curious: what is your way of flagging typos or bad grammar to colleagues? I often just do it without much fluff around it, but sometimes some people think that's harsh or nitpicky, but I really don't think anything bad about them while doing so. Any advice? BTW I'm talking about documents/tickets, not in chats or internal mails or something
I'm less worried about tickets; they're read much less often, and need to be quickly written without lots of thought.
I'm curious: what is your way of flagging typos or bad grammar to colleagues? I often just do it without much fluff around it, but sometimes some people think that's harsh or nitpicky, but I really don't think anything bad about them while doing so. Any advice? BTW I'm talking about documents/tickets, not in chats or internal mails or something
If you make detailed comments the whole way through, you run the risk of encouraging the writer to submit sloppy first drafts. Unless it's your job to be the writer's servant, think carefully before taking on that role.
I'm curious: what is your way of flagging typos or bad grammar to colleagues? I often just do it without much fluff around it, but sometimes some people think that's harsh or nitpicky, but I really don't think anything bad about them while doing so. Any advice? BTW I'm talking about documents/tickets, not in chats or internal mails or something
My personal policy is not to do it unless someone asks for it. I think it’s an ok way to go about things most of the time. If I have ”skin in the game” with that text and it’s important, I try to nicely ask for a permission to edit things. In my experience nothing pisses any person, including myself more than when someone starts editing my stuff and possibly even changes the meaning of things as they go. Way in the p…
I do a lot of proof reading for my own and other people's papers and decks. When I started out I found I was incredibly hit and miss at spotting issues. I now have a few rules that help me catch (most of the) issues: Start by finding somewhere quiet and reading the document out loud yourself, you will catch so many issues this way (though you still risk your mind filling in blanks or missing your common errors). Idea…
I'd hope it at least reached two or three :thinking:
I do a lot of proof reading for my own and other people's papers and decks. When I started out I found I was incredibly hit and miss at spotting issues. I now have a few rules that help me catch (most of the) issues: Start by finding somewhere quiet and reading the document out loud yourself, you will catch so many issues this way (though you still risk your mind filling in blanks or missing your common errors). Idea…
> The list could go one, I'd hope it at least reached two or three :thinking: