Some pretty good advice overall, but it's more important to understand why these rules are important and why it's valuable to follow them (and why it might be w

Some pretty good advice overall, but it's more important to understand why these rules are important and why it's valuable to follow them (and why it might be worthwhile to break them). Also note that there are exceptions to every rule, but you are probably not the exception. Most importantly, writing (like coding) is not a process of scrubbing through a checklist of rules and making sure you follow each one. Build your toolkit through practice, refine it by editing yourself with a critical eye (using lists of advice if you like), learn to improve what comes out the first time in the future, and get closer and closer to a natural cycle of being able to reliably produce good writing without herculean effort. It's the same as in coding. You need to learn the lessons to know what patterns of code are useful, what code smells are worth putting in the effort to fix, how to effectively refactor code and go from one design to another without dropping the ball or hitting a wall along the way. It'll never stop being work, but you can get good enough so it will feel natural and you'll be able to produce stuff that you can feel proud of (even when you look at it years later).