@jamesthomson Editors have helped me, but sometimes I get a little worked up when it comes to a debate about content. Here's one about a short story set on the Florida NW coast: Did you put an Australian pine in this piece because you're submitted to an Australian journal? Me, containing my anger and the assumption that I am really that stupid and unprofessional: "No, these grow in Florida where the story is set." And, unable to help myself, I provide a link to substantiate my claim and choice.
@jamesthomson ask them about commas. Really make it clear they have authority over commas and nothing else. Argue against the Oxford comma for a week. Let them win in the end. Good luck, you’re fighting the good fight.
@chrisphin@jamesthomson I’m currently editing a Q&A a dev sent me. It’s really great. Full of personality. But also 2x the length my editor would accept. So as an in-between editor, I’m going full-on red pen and really not enjoying it. Bah.
@jamesthomson@chrisphin Better to have too much than too little at this end. But it’s always tough when as an editor you need to cut things back that were good in the first place. But that’s the nature of the job.
@jamesthomson Oh, I realise I was unclear. It’s when you’re an editor who HAS written, getting your work edited by another editor. Jumped-up little shit…
@jamesthomson@dmoren Right 🤭. Btw, I chose “Delphi” for the “So long” quote, because it’s close enough to “Dolphin” (or “Delfin” in Swedish). Thought it would be appropriate because of the Pascal association – and then in turn – classis Mac app dev.
@jamesthomson I noticed during the time I worked as a (sub-)editor – gradually winding down a few years ago – that people have got way more reluctant to be edited. They used to treat editing quite deferentially, now they are used to being able to publish directly to (insert long list of platforms) and often start to push back if you do anything more than fix typos.
Add comment