Orchid XP v8 wrote:
> Tom Austin wrote:
>> I wish we were hiring ;-)
> 
> Hahahaha!
> 
> Well, that *would* make my task rather easier, yes. ;-)
> 
> (Altough... which random part of the planet do *you* live in? It's 
> always important to check this when speaking on teh interwebs.)
> 

some place you said you hated to visit

Post a reply to this message

Mike Raiford wrote:
> housing industry weren't in the toilet,

That actually makes it an excellent time to rent a place. All the people 
who need to get out of the house will take money from you to live in the 
house they can't use right now anyway.

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message

Orchid XP v8 wrote:
> What do we think of this then?

Muuuch better!

Just a few nits:

Personally, I'd leave "bright" in there. You'll have to decide. :-)

"Learned Tcl/Tk in a week" is misspelled.

Instead of "(see next point)", I'd write "(including those described 
next)".  This implies there are many you did, but the next ones are most 
important.

I'm not sure I'd use the word "routine" in "routine recording of 
changes". It sounds mundane. "Proactive recording of changes" perhaps, 
or something like that. Something implying it's not just mundane, but 
important to be consistent. "Consistent and proactive recording of all 
changes in configuration and procedures."

"fault-finding" is maybe a poor choice of words? It sounds like 
"figuring out who to blame" to my ears, even tho I know it's the right 
term. "fault tracing" perhaps?

Get rid of "(particularly backup and restore)". Seconded. :-)

Year 1: "soft systems analysis and design"?  Did you mean "software 
systems"?

"Caving" is technically called "spelunking". Not sure if you want to 
change that, tho.
http://www.postimage.org/aVjnTir-3282b5978015eb66e807f0718a013507.gif

Overall, yes, much better. I'd hire that one. :-)

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message

On 21-Nov-08 14:52, Orchid XP v8 wrote:
> OK, so I *think* I've taken nearly everybody's suggestions on-board. 
> What do we think of this then?
> 
> (The information about my degree is incomplete and possibly incorrect; I 
> can't seem to find the transcript right now.)
> 
> I've basically dumped in everything that seems remotely relevant. 
> Presumably before I finalise this document I'll need to trim it back 
> down again a little.
> 
Better. I am still missing the games group you are in. At least I 
suppose that is a hobby of yours. Tcl/Tk is in point 5 but not in 3.
I don't like the 'expensive' terms. That is rather obvious and therefor 
unnecessary to stress. In fact weakens the point in my opinion.

I think it is correct to keep the p.o-t and invisible-me out of it at 
least until your posts about your current company are expired. Many 
employers may not be so glad to know how you talk about your current 
management.

If you would apply for a job more in my field then you may tell a bit 
more about what your company does. 'policy and procedure documents' are 
one thing, but for work in a medical lab you may be much more qualified 
than most.

Post a reply to this message

I haven't read the CV over yet myself, but a couple of comments on 
Darren's comments:

On Fri, 21 Nov 2008 11:32:08 -0800, Darren New wrote:

> I'm not sure I'd use the word "routine" in "routine recording of
> changes". It sounds mundane. "Proactive recording of changes" perhaps,
> or something like that. Something implying it's not just mundane, but
> important to be consistent. "Consistent and proactive recording of all
> changes in configuration and procedures."

"Change management documentation" is a phrase that I've seen used for 
this sort of thing.

> "fault-finding" is maybe a poor choice of words? It sounds like
> "figuring out who to blame" to my ears, even tho I know it's the right
> term. "fault tracing" perhaps?

"Troubleshooting" is a good general term for this, or "problem diagnosis 
and resolution".

Jim

Post a reply to this message

andrel wrote:

> Better.

That's usually a good start...

> I am still missing the games group you are in. At least I 
> suppose that is a hobby of yours.

Didn't seem highly relevant. (I suppose you could attempt to pretend 
that this illustrates teamworking or social skills or something... but 
mainly it involves shooting things!)

> Tcl/Tk is in point 5 but not in 3.

It's in point 2 though.

> I don't like the 'expensive' terms. That is rather obvious and therefor 
> unnecessary to stress. In fact weakens the point in my opinion.

Yeah, it does kinda look like I'm trying to invent ways to sound important.

> If you would apply for a job more in my field then you may tell a bit 
> more about what your company does. 'policy and procedure documents' are 
> one thing, but for work in a medical lab you may be much more qualified 
> than most.

Our lab doesn't do diagnostic stuff, only quantitation.

(Actually, all the mass spectrometers say "NOT FOR DIAGNOSTIC USE" on 
them in big lettering. I'm not sure why... Presumably if you want to do 
diagnostic work, they sell you an identical machine for 12x the price.)

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

Post a reply to this message

Jim Henderson wrote:

> "Troubleshooting" is a good general term for this, or "problem diagnosis 
> and resolution".

Troubleshooting is the term I'd go with.

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

Post a reply to this message

Darren New wrote:

> Personally, I'd leave "bright" in there. You'll have to decide. :-)

OK. Fair enough.

> "Learned Tcl/Tk in a week" is misspelled.

Damn. Now I have to figure out why it's misspelt...

> Instead of "(see next point)", I'd write "(including those described 
> next)".  This implies there are many you did, but the next ones are most 
> important.

Heh. You really do enjoy subtly implying that I'm more important than I 
really am, eh? ;-)

> I'm not sure I'd use the word "routine" in "routine recording of 
> changes". It sounds mundane. "Proactive recording of changes" perhaps, 
> or something like that. Something implying it's not just mundane, but 
> important to be consistent. "Consistent and proactive recording of all 
> changes in configuration and procedures."

How about "rigourous recording of changes"?

> Get rid of "(particularly backup and restore)". Seconded. :-)

It's gone.

> Year 1: "soft systems analysis and design"?  Did you mean "software 
> systems"?

"Soft systems" being opposite to "hard systems".

Hard systems are things with specific, typically scientific or 
mathematical requirements. E.g., programming the robotics for an 
assembly line would be a hard problem.

Soft systems are warm, fuzzy things that are ill-defined. The kind of 
thing where figuring out exactly what you're trying to do is usually the 
hard part.

> Overall, yes, much better. I'd hire that one. :-)

Mathematical Orchid, I CHOOSE YOU!!

Now Mathematical, windowed-sinc convolution!

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

Post a reply to this message

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

>> (Altough... which random part of the planet do *you* live in? It's 
>> always important to check this when speaking on teh interwebs.)
> 
> some place you said you hated to visit

Well, that narrows it down... not much, but... hey, I guess that's the 
important information! ;-)

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

Post a reply to this message