Code works when it's written according to rules. Does that mean it's correct?
A lot of people don't understand programming. They think there's a right and wrong way to do it. ( there are degrees of correctness based on accepted patterns )
Smart, scrappy developers go into projects with a large amount of naiveté and enthusiasm. It can be quite productive.
If you start a project knowing all the things that could go wrong -- you'll pre-optimize your code and end up going so slow you don't finish. Unless, you're willing to move quickly and re-visit your work as necessary.
We've all seen @baz changing things on 200 words a day. He didn't have the perfect vision / plan before he went in. He creates features that break on occasion. That's all part of the process: Make a thing that works. Release it. Fix the edge cases as they come along.
This allows you to move quickly.
Writing is like that.
Words work when people understand them; when they elicit emotion or stimulate thinking. Words, however, can get wordy. You can use long, winding phrases, which commas can exacerbate, that lead your reader into thoughts of their own and run-on sentences that cause you to forget what you were even trying to say.
So, how do we get words out rightly? ( 2.5 writing tips ahead )
1. Write short sentences at first to clarify your points.
2. Edit your words - combine short sentences if you can increase flow without losing clarity.
2.5 The thing you are trying to say often ends up at the end. Could you put the important piece up front instead?