scott wrote:

> Oooh much better :-)

Well I'm glad you like it.

> I would fill up the empty space on the 2nd page by filling in some more 
> info from your current employment:
> 
> - Maybe expand the disaster recovery plan in a positive way, what does 
> it consist of, what sort of testing did you do? Just a couple of sentences.

Unplug stuff, check that the redundant hardware fails over or whatever 
correctly, check that alarms go off, check that the thing goes back to 
normal once I plug things back in, that kinda thing.

> - When you say you developed a range of tools and scripts, explain a bit 
> more.  What language? Are they still used regularly? Are they used 
> anywhere else? Did any particularly save time or money?  SHow that you 
> have used the languages you mention in the skills section.

Mmm, OK.

> - The remote backup script, add something like "This is in use daily to 
> ensure all blah blah files are correctly backed up" or whatever.

The scripts are a failsafe that copy the data from the mass spectrometer 
PCs to one of the fileservers. It's just so if one PC gets hit be a 
meteorite, we don't lose all our data. For most of the PCs, we wouldn't 
care because there's nothing interesting on the local HD, just the OS.

> Then just play about with the font size / margins to make it nicely fit 
> on 2 sides.  I wouldn't worry about repeating yourself or trimming it down.
> 
> But yeh, it looks really good now!

The current form is more or less a brain-dump. I scribbled down 
everything that seemed relevant, with the intension of making it make 
sense later.

Damn, it "feels" like I know way more programming languages and 
technologies than that! And yet, I can't think of anything else to add 
to the list... (Unless you start adding stuff I've "vaguely heard of" 
and would superficially recognise the syntax of.)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message