1. 13
  1. 5

    My advice—just do it!

    I started blogging in [[http://boston.conman.org/archive/][1999]], and back then, there wasn’t much in the way of blogging software. At first, it was just a series of hand written HTML files as I started on the software [1]. As time went on, I imported the entries I had into the blogging engine I wrote and continued on [2].

    The original idea for my blog was to keep friends up to date while I was away in Boston for a short contracting job (I never did get that job) but over the years, it’s more for me than for other people, but if others read it, that’s fine. Because of that, there’s no single subject my blog is about—it’s more of an online journal (which was popular in the mid-to-late 90s), but for me, that’s okay.

    So, just do it already!

    [1] Which I still use, by the way. https://github.com/spc476/mod_blog

    [2] It took me nearly two years writing the software before I said “Enough! This won’t ever be perfect” and released it. There were features I was stressing over that in the long term, turned out not to matter at all.

    1. 1

      I think it is wonderful that you have all your old post still published and available. I’ve lost anything I had before 2008, but I’ve made a point to keep everything available that I can.

    2. 4

      I partially disagree with the “quantity over quality” advice regarding topics one is passionate about. There’s so much content now that posting often hardly helps one stay visible. Deep topics do require deep posts, and for practicing writing it may be better to take small topics that wouldn’t make big posts anyway.

      There’s an inherent problem with the blogging paradigm, that posts are complete and if you have something new to say, you write another one. It’s easy to see where it’s coming from: there are no protocols whatsoever for announcing content updates, and everything from RSS/Atom to ActivityPub is focused on notifying people about new content only.

      But perhaps there should be. Or we should be ok with making write-ups on topics we are passionate about living, updatable pages rather than fire-and-forget blog posts, and be ok with having to promote them outside of the blogging paradigm.

      1. 3

        I thought about this as well recently and think it might be feasible to try and generate some sort of diff of an article and use that as another feed element. This could then link to a chapter of an already existing blog Post which has been added. I’m not yet sure where the issue will be yet as I haven’t tried implementing it yet, but it definitely makes the feed generation a lot harder than it currently is.

      2. 2

        This actually gave me the little shove needed to go and write (and publish!) the blog post idea which has been knocking around in my head for the last few days!

        1. 2

          One more thing: work out a publishing method that is as close to effortless as you can make it, and stop dinking around with different blog engines. OK, that’s two more things.

          My publishing method with pelican is two commands. The first is make newpost NAME="name of the post" which summons my editor with a skeleton already in place, and then make rsync which invokes pelican and if successful fires it off to the publishing location.

          1. 3

            I set things up so I can email entries to my blog. Makes it quite painless to write.