stuff, mostly related to software and information technology

What happens is that I come up with a topic that I just have to write about, an opinion or something else that I find interesting. Then I start writing a post but after a while I go back and read what I just wrote and start analyzing it. Is it good? How will that be interpreted? Is it correct? And so on. In the end I end up(see two “ends”, that looks weird) with a text that is full of comments about the text itself and fragments of half finished sentences that I’m happy with scattered all over the place and doesn’t work as a whole. After a while I feel like it’s taken way too much valuable time and gives it a rest for later. I haven’t gone back to finish one such post.

I used to be a good story writer when I was a kid, good imagination and all that. I’m also able to keep a conversation going and I can code(not relevant but anyway). So what is the problem? Possibly it’s because I feel that I can’t release anything that is not good enough. But the only judge of that if I don’t publish is me, and since I’m not a good blogger how can that count for anything?

So, here I am writing about writing. Something I promised myself not to do because I think it’s lame to fill blogs with topics like “ah I don’t know what to write” and that becomes a post about that there’s nothing to write, if you know what I mean. What happened was that I was writing another post and ended up editing back and forth just like I described and just had to stop and think about it for a minute. While thinking about it I wrote this. The good thing is, I didn’t go back and edit this(ok a little). See this post as personal exercise(for me) and in no less than in two minutes after I put this dot here. <- yes that one! …this post will go live!

By Martin | in: Uncategorized
« Word Of The Day: Connectile Dysfunction DevCase, a silent website guaranteed! »

2 Comments »

  1. Translating your thoughts into code, this might be a solution:

    In the Transact-SQL Extended Syntax, there is a forward_only switch for cursors, which, as the name says “Specifies that the cursor can only be scrolled from the first to the last row”.

    Maybe that should be your new rule when writing, forward_only.

    Then later, you could perhaps change that into fast_forward, to get your speed up. However, fast_forward is basically a forward_only, read_only cursor and read_only is probably better for readers.

    Maybe that could be an idea for a WP plug-in? A plug-in that disables the backspace button when writing.

    ::m

    Comment by Mikael Östberg — February 7, 2008 @ 7:59 am

  2. It’s not a bad idea! Since I’m now manually not pressing backspace or delete ;-)

    Comment by Martin — February 19, 2008 @ 9:18 pm

RSS feed for comments on this post. TrackBack URL

Leave a comment