Post History
Since writing my last question, I've been able to write a handful more items and have tried to nail down some more specific items I can ask about improving my writing. This issue became readily ap...
#3: Attribution notice added
Source: https://writers.stackexchange.com/q/6950 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
Since writing my last question, I've been able to write a handful more items and have tried to nail down some more specific items I can ask about improving my writing. This issue became readily apparent. In writing programming code, I've found that it can be really easy for things to just wash together so you can't see what is there. I've found many times that something I struggled with one day was easily solvable by going back the next day and looking simply because everything washed together and I didn't see something. I'm finding that in my writing, as well, especially if it has markup in it. I can write something and then put it away and come back about 2-4 weeks later and see stupid things like poor phrasing that renders the expressed idea into nonsense, grammar issues, and so on. Now obviously, I can't sit on everything I do that long without moving onto something else, but I find even that I don't see things in the next day or two because what I want to say is so ingrained in my mind that I substitute that for what is actually being said by the written word. So how do you get around the aspect of your writing being so fresh in your mind that you can't see what is actually being communicated by it?