Jobs (2)

Quite a surreal experience today. Pretty much since I lived in this village, I worked up in London. There was always quite a clear demarcation between home and work.

But today I interviewed with a couple of guys who work for one of the few businesses in the village. It’d be strange to work for them – working within walking distance of home, first time ever.

Realistically, I’m trying to get back into the industry after five years away, so wouldn’t really rate my chances – I’m not sure if it is something I’d want to be doing either. But equally, they’re a charity based in our tiny village, so they probably won’t attract many candidates. I wouldn’t mind betting that every candidate they do attract will have a back-story similar to  mine.

Realistically, every interview is practise for the next interview. This one didn’t go at all badly, considering the time I’d been away, how much water has passed under the bridge. But then again, I have spent months boning up technically, so really, that shouldn’t come as any surprise. I got a little tripped of on some of the most recent language concepts, but that’s not really a problem because I have already read up on the question I was asked, and I can easily read up on general updates to the language in the next few days. The only day that I am busy this week is tomorrow. Next time around, I’ll be convincing.

One interesting thing: I’ve never been a fan of “blagging” – pretending I know more about something than I actually do, instead I’ve always been very “matter of fact”, and have generally floated to the top in every environment that I worked in because I have always been stronger than most people, technically. If fact it would surprise you how often I’ve worked with poor technologists in supposedly prestige environments. Anyway, yesterday I had already come clean about my lack of up-to-date knowledge, so I asked these guys some questions about a few aspects. They didn’t use those aspects either! Just goes to show, you have to look past the blurb.And I still maintain that a lot of the languege’s innovations, while labour-saving for developers, are not necessarily intuitive for reviewers.

Pharmacy Blunders

The first thing I do each morning is to fire up the computer and see anything that happened overnight, either on social media or by email.

This morning, a friend of mine had posted a story he’d picked up from the BBC. Some pharmacy (in the UK) had issued a chap with the wrong meds, the chap subsequently died. The same thing once happened to me, except I check all my meds, so noticed the mistake before I’d even opened the box.

The error was with my local pharmacy. Somebody had picked the wrong drugs. Somebody else had then checked those wrong drugs, and signed them off anyway. Having designed many banking systems, I am very familiar with four-eyed processes.

When I spoke to the pharmacy, their excuse was that they were very sorry, but the staff were soooo hard-worked and always in a hurry.

To compound matters, I complained to the NHS, lest the same thing happen to somebody else. The result was that despite the mistake, the pharmacy’s working practises were sound so therefore no action would be taken.

I mean, I never complained to try and make any financial gain from the situation, but maybe I should have? I have a feeling that the NHS just cover up for each other, whereas a court might have taken this more seriously. Certainly, at the end of this process, there was a definite note-to-self: next time, call a lawyer. It can’t have been far from their minds either, one of the first things the pharmacy asked was whether I could return the evidence, errrr, the meds back to them.