Interesting. The same is mostly true of programming -- indeed, I've gradually learned that the most common and worst mistake you can make in programming is over-thinking things. The best code usually arises from getting a rough idea of what you're doing, slamming out the code, and then "refactoring" (revising) it afterwards.
In programming, we've gradually developed something of a discipline around refactoring: an ever-growing list of specific problems to look out for (usually called "bad smells"), and common options for how to improve them. Does anything of the sort exist in writing, or does everyone just wing it?
There may be no cognate discipline -- it may not even be a sensible question in writing -- but I'm struck by how your writing process resembles my programming one...
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
zaluzianskya and ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
skylark_photos
no subject
Date: 2014-07-16 05:58 pm (UTC)In programming, we've gradually developed something of a discipline around refactoring: an ever-growing list of specific problems to look out for (usually called "bad smells"), and common options for how to improve them. Does anything of the sort exist in writing, or does everyone just wing it?
There may be no cognate discipline -- it may not even be a sensible question in writing -- but I'm struck by how your writing process resembles my programming one...