Thursday, 10 November 2011

Write it, then fix it.

I'm on a Java Programming course all this week, and although it's given me some extra time to edit my MS, due to the additional journey time, it's meant that any idea I get for a blog post has evaporated by the time I get a chance to write it.  Hence the lack of posts this week.
One of the comments the tutor made today hit a chord with me.  He said that when writing code, you should just write it, and then fix it after.  My immediate thought was it's just like writing. 
But, you guys know this already!


  1. I think that's a good reminder. I sometimes get caught up trying to write it perfectly the first time. I spend hours on one paragraph.

  2. I've been trying to do this and it has been making a huge difference. I just want to get the story out and then I will go back and make it better. Good reminder. :)

  3. Erin - Thanks. You sound like you start from the opposite end to me. I think after a 100 edits, i'll still be light years away from it being close to passable.

    Abby - I'm the same. If I don't get the story out onto the pc, then it tends to leak out of my ears instead.

  4. Oo, great point, Iain! Isn't it funny how we can relate most things to writing, once we've seen them in the right light? :)

  5. Yes Carrie. I seem to do that a lot :o)