I’ll admit, I’m not a barista. Needless to say working in IT and coming from Australia I have a healthy respect for Good Coffee, and it occurred to me the other day there’s 3 simple rules to follow in order to have good, proper coffee:

  1. Does not have sugar in it.
  2. Is not measured by the gallon.
  3. Comes fresh from the bean.

The first rule is probably the most important – if you need to add sugar to the coffee (e.g., because it tastes bitter), then you’ve got bad coffee, or at least substandard coffee. The flavour of coffee should stand on its own, without any need for sugar based products. If you have to add some syrup or sugar to it, then you should look elsewhere for better tasting coffee.

The next rule is something inherently understood by anyone who has had the pleasure of either a macchiato or a ristretto. Usually whenever I’ve had a “big” coffee – e.g., anything bigger than a long-black in size, it’s typically diluted with either a lot of hot water or a lot of hot milk – and then usually with a whole lot of sugar as well. Good coffee is not about whether you get a big volume of liquid for the money you pay, but whether you get a good quality of liquid for the money you pay. To paraphrase Bill Bryson – I’d rather pay $8 AU for a good espresso than $2 AU for a half-litre monstrosity that tastes about as strong and solid as mop-water.

The final rule is about freshness. Don’t get me started on instant coffee, though I’ll at least grant that it’s portable, and thus fulfills some use in extreme circumstances. Otherwise though, this rule means: don’t buy pre-ground, and only grind when you’re about to use.

A final rule that should be obvious in what I’ve stated above – drip filter does not constitute coffee. If it doesn’t come out of a real honest to goodness espresso machine, it’s broken before it even hits the cup.

Does all this make me a coffee snob? Probably yes, but for good reasons.

 

(Or, information is like water – you can drink from it, you can swim in it, or you can drown in it. What do you want to do?)

IT people work in what I’d refer to as information rich domains. That is, there’s a huge amount of information out there that can be of use, and so the struggle is not necessarily a lack of information, but a challenge in finding the information you want.

(This, for what it’s worth, is why I think that certification exams as a whole are at best poorly representative of skills. Certifications for the most part seem to be about rote recall, which doesn’t reflect real life situations. That is, in real life when faced with a challenging technical problem, I don’t think many people lock themselves in a room devoid of any contact with anyone or anything else and attempts to solve the problem based on memory.)

Real life problem resolution is about not only having access to a plethora of information, but also being able to find the key bits of information. Yes, you need a certain base amount of knowledge in the area to get started, but after that the solution will come from your overall ability to problem solve, and your skill or capability to retrieve the right information.

There’s a few things I do that I think helps me to access information I need quickly. I’m not saying this suits everyone, but it works for me, so people of a similar ilk may find it useful.

First, when it comes to file storage, I’m incredibly anal retentive. (That means for instance, that it literally gives me the shudders if I look at someone’s desktop (Windows, Linux or Mac) and it’s full of files. To me that’s just like having a desk covered in papers and files 3 inches deep on every surface*.)

So I have lots of folders – lots, and lots, and lots of folders, nested, structured named in such a way that I can quickly access stored data. Yes, it may take a few clicks to navigate through folders, but I found this easier to do than searching through a few folders with hundreds or even thousands of files.

Being on a Mac, I make heavy use of Spotlight, the integrated search tool. To be quite frank, in Mac OS X 10.4 this feature sucked, performance-wise, and I regretted every time I tried to use it. In 10.5/Leopard however, it screams, and is fast enough that I even use it as an application launcher when I’m in a hurry.

Next, and what has helped me most in the last two years is a product called Yojimbo, from Bare Bones Software. This makes use of the SQLite component of Mac OS X to do information storage with full text search. I simply drop PDFs, text files, web locations, HTML pages, etc., into Yojimbo, (and also when I have the time add a few tags for additional identification).

The beauty of Yojimbo is that I don’t have to actually go to it in order to search it. One of its features is full Spotlight integration, so thus at any point that I’m looking for information I can just hit CMD+Space, type in the query in Spotlight, and get search results for both files still on disk, and content in Yojimbo’s database. Currently my Yojimbo database is about 1.5GB and continuing to grow as I bring more documentation into it**. (In fact, I don’t store documentation on my filesystem any more – unless I’m being lazy, I put everything into Yojimbo as I get it now.) If I need to send a document I find to a customer or colleague, I can export it and drop it in an email in a matter of seconds.

The final bit of organisation I do is archiving. I don’t like deleting information – in the past I’ve suffered the consequences of deleting something that I later found was no longer available. (E.g., needing to access a software compatibility guide from say, 1999 due to ancient versions of software in use.) At the same time though, I don’t want searches for current issues and problems to be cluttered with matching keywords from documents that are so old that all they’ll do is hinder, not help me. So I keep out of reach of my day to day searches older, historical information. Usually that’s stored on a separate fileserver – it’s there, it’s protected, it’s available if I want to access it, but it’s not getting in the way of what I need to do today.

So there’s a rough overview of how I stay organised. I know it won’t help everyone, but if you’re drowning in information, it may just be the start of a lifeline.


* I had a boss once who called such disorganisation a “discussion feature” for when he had customers in his office. You can imagine what I thought of that.

** Of course, it gets backed up! (I had to learn some AppleScript in order to properly quit Yojimbo at a strategically appropriate time of the day, copy the files for subsequent backup, and then restart it.)

 

I know this is a minor quibble – and for the most part, minor quibbles sum up the issues that I have with NetWorker. However, it annoys the hell out of me.

Somewhere, someone in the development team at EMC got the bright idea for NetWorker 7.3 that for “usability” and “consistency” reasons, it would become necessary when depositing media to either:

  • Answer an inane question (i.e., sequence goes: put media in CAP, run nsrjb -d, get asked to answer ‘yes’ to whether you want to import media or not)
  • Remember to add a -Y option to the nsrjb -d command to automatically answer ‘yes’ to the inane question.

Now, I do have a problem with this. In the first case, core behaviour was changed, and I don’t like that. Nor do I see a valid consistency reason – in nsrjb you’ve always been required to answer ‘yes’ or to add a -Y to the command if you’re going to do something destructive, but depositing media shouldn’t be deemed a destructive action.

In the second case, administrators are going to get into the habit of automatically throwing a -Y option onto each nsrjb command they run. I’m the first to admit that where I need to, I do use -Y, but don’t advocate that people get into the habit of using it except for when it is really necessary.

Thus, my preference would be that some release of NetWorker would drop the inane question when a deposit is done, and just let the administrator or person running the deposit get on with the activity of moving tapes.

 

My partner reads a news/blog site called undrln.com, which can often link to some really interesting bits of information. One such item that the site linked to a couple of days ago is an article, 9 brain habits you didn’t realise you had. While there were a few things in there I was already aware of (hint: one of them wasn’t about the colour chartreuse!), the thing that most interested me was confirmation about the subconscious. I often found it weird that if I didn’t think about a particularly vexing problem for a while after gathering all the data, the answer could sometimes just pop into my head at the most bizarre of times. It seems it’s not too unlikely after all.

 

I’m a big fan of RFC-1178; thus, I’m not too keen on backup server names such as say, nsrserv, bckmast01, unxserv134, etc. I guess it’s partly proof of how much of a geek I am at times, but I think backup servers need good names.

Since backup is all about protection, I tend to look for names that reflect a general sense of protection. Over the course of the last decade or more, most of my backup servers have ended up with names that reflect that notion of protection, and out of a general sense of trivia I thought I’d mention some of them:

  • archon – a title used in some religions for ‘protector’
  • bastet – an African goddess of protection
  • bes – another African goddess whose roles included that of protection of children
  • diana – the Greek goddess of the hunt and protector of children
  • dryad – mythical woodland creatures that protected the forests
  • ent – borrowed from Tolkein, a protector of forests
  • gnome – mythical creatures that live in gardens and who are protectors of nature
  • isis – the Egyptian goddess of protection and magic
  • tara – the Tibetan goddess of peace and protection
  • venus – the Roman goddess of love and protector of gardens

These obviously all come from the one theme, and there’s plenty of more examples to be found.

© 2012 The NetWorker Blog Suffusion theme by Sayontan Sinha