This is the 1,000th post to "Through the Interface" – a milestone I mentioned was coming up a few weeks ago. Which means I'm hitting about 142 posts per year, which is pretty much on target (I aim for 3 posts a week, so that's about right).

Something that occurred to me, over the weekend, is that it's often not very easy to discover content contained in the blog: there's search (which usually seems to work well, but even I have trouble finding posts I'm sure I've written, from time to time) and the post indices ("Post Index" and "Reverse Index" in the left-sash, as well as category- and month-based indices in the right-sash), but I thought it was time to try something different.

How randomI've therefore added the "10 Random Posts" section in the right-sash, which picks out and displays a set of random posts from the blog's content archive every time a page is loaded. This was surprisingly tricky to implement using TypePad: I had to jump through some hoops to generate the information I needed for the various posts and ended up storing hard-coded information on the first 999 posts in the sash itself (anything from 1000 onwards gets added to this list dynamically, so future posts will also be included).

This hopefully won't impact the blog's load times too badly: right now it's an extra 140K of data that needs to be loaded – which doesn't seem as though it would cause a problem, particularly – but I'm certainly open to switching it off, in case people start to complain (legitimately :-).

Give it a try and let me know if you find it helpful: the tooltip for each link contains the date the post was published, to help you decide whether it's worth clicking on, or not.

11 responses to “1K”

  1. Congratz...Kean!

  2. 1000 posts and I've only scratch the surface of your amazingly insightful blog. Looking forward to the next 1000.... No pressure 😉

  3. Well done Kean !!

    ... and the random posts will be great for rainy Saturday afternoons 🙂

    Stay well.

    ps: if you're looking for topics .. a series on unit testing with AutoCad and .NET would be a treat.

  4. Kean Walmsley Avatar

    Thanks, Kerry. 🙂

    Interestingly (although perhaps it's not a coincidence - perhaps the question was also asked elsewhere) you're not the first person to ask me in the last week for a series on unit testing with AutoCAD & .NET.

    I pointed that person to Scott McFarlane's highly rated AU 2012 class, as a starting point. Perhaps Scott might be able to contribute a guest post or three to cover the details... I'll reach out to him to see.

    I'd also like to learn more about this area, so one way or another I'll find a way to get this topic covered here.

    Best,

    Kean

  5. Thanks Kean. I know a few people who would appreciate a bit more than just a basic paragraph or two.
    It wouldn't be an easy topic to cover. Tell Scott I've been known to exchange Jelly Beans and Vegemite for favours.

    Regards,

  6. Thanks Kean. I know a few people who would appreciate a bit more than just a basic paragraph or two.
    It wouldn't be an easy topic to cover. Tell Scott I've been known to exchange Jelly Beans and Vegemite for favours.

    Regards,

  7. Alexander Rivilis Avatar
    Alexander Rivilis

    Congratulations! Great job, Kean! Keep on!

  8. Congratulations Kean on reaching such a great milestone! Many a seemingly unsolvable problem has been solved right here.

    Cheers
    Martin.

  9. Stephen Preston Avatar
    Stephen Preston

    Woot!

    How many words is that. 🙂

  10. Kean Walmsley Avatar

    I have wondered about that. I haven't counted (obviously :-), but suppose I could use the TypePad API to find out. One for a rainy day.

    Kean

  11. Hi Kerry,

    TypePad thought this comment was spam - probably because of the product references - and I only just realised. Sorry about that.

    Yes, Scott is the right person to tackle this tricky topic, and he tells me he's getting to the end of Part 1 of 3. Should be a great series!

    Cheers,

    Kean

Leave a Reply to Kerry Brown Cancel reply

Your email address will not be published. Required fields are marked *