Look who’s back

Looks like Jevon is back among the bloggers again. Nice to see him back! He’s got a post about Real-time blogging and outlining that’s interesting. (permalinks, Jevon? I couldn’t find one) In a nutshell, he wants to use an outliner on his blog because that’s how he tackles technical learning, by writing out an idea, researching it, expounding on it, rewriting it, etc. He thinks he would make a better “real-time” blogger than a “journal” blogger. He might be right in that, but I can tell you he is right about one thing, outlining is not for everyone. There are a number of reasons that I wouldn’t do it. First, I would have a hard time being productive and writing while I work on something. I’m a trial and error person when it comes to tech, I’ll try something, not like it, switch it back, try something else, etc. Stopping to document what I was doing would kill my flow. I have a hard time even talking to someone when I’m messing with something, let alone trying to explain what I’m doing as I go along. No, I need to focus on writing when it’s time to write, and working when it’s time to work.

Secondly, I hate outlines. I have always hated outlines. In school, when you had to do outlines as part of your research papers, I would always write the paper first, then draw up an outline based on the paper. I write by flow, meaning I start writing and my thoughts take me along the path until the paper is finished. I was always a much better creative writer than I was at writing research and technical papers. That’s why doing something as simple as a “readme.txt” for that project I’ve been working on for Geek has taken me forever. It’s a simple text file, yet it takes me weeks to get it right, because I don’t work well trying to document something,. It took me 4 hours to create the thing, 3 weeks to document what it is!

Lastly, I need to think about what I blog because, in this state of writing by “flow” I can, and sometimes do, write things that I shouldn’t write. If I’m outlining, and writing as I go without paying complete attention to what I write, there’s a good possibility I’m going to write something that offends the hell out of someone. I’m an opinionated person, I’m old enough and have seen enough BS in my life to be able to call it that, but I won’t most of the time in as public a forum as this. Too many flames. When I write now, I decide whether or not to take on a particular subject, and how I’m going to take it on before I start writing, and that guides my writing. It keeps this blog from being a center of controversy instead of the sharing of knowledge and ideas I want it to be.

Those would be some of the same reasons I don’t plan to blog events live as they happen. I need to edit myself. *L*

Similar Posts

  • Week in review

    It’s been a crazy week, as you all have read. Made none any less crazy by the fact that our Annual Meeting is coming up next week, which brings about it’s own flurry of activity that I haven’t even talked about on here. What do I take away from this week? The whole battle between…

  • |

    Personal Tech update

    Just an update on some things I’ve been doing. Angela already wrote about the Roomba, so I’ll leave that alone, other than to say, as a gadget type of guy, I’m fascinated by watching it work. (Of course, the whole point is that it works while you’re doing something else, so I need to break…

  • Installing

    OK, I’ve got the MS Office beta, OneNote beta, InfoPath beta and Publisher beta installed. It wasn’t overly difficult and ran into only one small problem. Outlook on first start needed me to reinsert the Office CD in order to create the first “welcome message”. It was ok 1 minute later. Activation took about a…

  • My contribution to the RSS bandwidth question

    As discussed in the comments, using Bloglines might be considered a better way to limit the bandwidth I use in checking on feeds, since it checks once an hour and shares the feed with all of the subscribers to that feed. So I decided to give it a try. It’s better than I thought it…

  • On the other hand..

    Turns out the network cable wasn’t unplugged, but somehow, someway the data-port just went dead on us. Has this ever happened to you? I’m thinking some sort of electrical short or something from the desk hitting it, but that seems somewhat far-fetched. Especially considering the telephone jack still works fine! I’m not an electrician, so…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)