Skip to main content

Basic Blogger

Reading the article by Nick Holmes in Legal Information Management about law blogs, made me think about just how little I really know about certain technical stuff.I’ve been blogging personally since March 2006, so I can post, I can hyperlink, I can insert pictures, yet I still don’t know how to make a banner. HTML is a mystery to me (new look Blogger = so nice!!), I can’t trackback visitors (to either blog), and I failed when trying to put a statcounter in the code of this one.

I’m a techie failure.

But, I ask myself, do I NEED to know all these things? A banner makes things look prettier, and I may not be able to do it myself, but I know people that I could ask to do it for me. I can live without prettyness, and save favours for essential times. Do I really need to be able to rummage in HTML? Why would I need to track back visitors, other than for my own personal interest? Do I have the time to learn how to do any of these things anyway, and if I do, would I be able to spend enough time on them to make me actually good at them?

I’ve come to the conclusion that I should be happy about the fact that I’m able to do a lot, and accept that I don’t have to be able to do everything.

I think that works for life / work too.

Comments

James Mullan said…
I read the article as well and thought it was very good. I have to agree in that you really don't need to be that technical to create blogs and feeds.

That is the power of Web 2.0 that it gives web users the chance to create content without having in-depth knowledge of HTML or XHTML because either the code exists already and you can just add it or it's likely that someone will write it soon and it will be freely available.

Popular posts from this blog

Relaunching a library service

What do you do when you decide to do what is verging on library-based insanity, and basically scrap your current library service, and relaunch everything - physical layout, LMS, and classification system? In my case, spend a year, planning, developing, preparing….and then a frantic few weeks hauling stock!
The background to this apparent madness is this: when I took on this role I inherited a library using a layout that didn’t seem to make sense, a classification system I wasn’t familiar with, and an LMS that had been in place for 20 years but didn’t seem suited to our needs. As I was new to the library, a major part of the time I had available while settling in during my initial few months was dedicated to exploring how well these things were working, both for users, and library staff. I had the benefit of my colleague also being new to the library, only a few months after me, so together we looked at these issues with fresh eyes.We came to the following conclusions: The physical layou…

Impressive shelving technique

I have a new role model: the shelving technique demonstrated between 12 and 18 seconds by the librarian in this Lucozade video is something to aspire to! :D


Too close to the problem to see the achievements

Sometimes, you have so much to do, that you can't see what you've actually done. I'm feeling very much that way at the moment, so I thought I'd make a public list for myself of all the work and professional things I've done since taking up my role in mid January. Then maybe I'll feel less like I'm just not very good at anything. It's worth a try. Although for obvious reasons, I can't publicly say much about the baddest/hardest stuff, but...it's in there. Maybe it's not explicit about how hard it's been, but it's there.

So: what have I done?


Service management and development

Replaced someone who ran the library for 21 years, who retired 3 months before I started, and gave me no handover information.Got 6 weeks of company/training on the library from an assistant, who then retired, leaving me as the only person in the organisation who knew anything about how the library actually worked.Done the assistant librarian and librarian job simu…