 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
Attachments:
Download 'cv-v6-programmer-minimal.pdf' (41 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
>
I wish we were hiring ;-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
>
Actually.... remove the (particularly backup and restore) from the
Oracle DB part.
It looks good - sounds a lot like my credentials - learning programming
languages and the like.
Tom
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tom Austin wrote:
> Actually.... remove the (particularly backup and restore) from the
> Oracle DB part.
OK.
Actually, I'm kinda repeating myself here, aren't I? I said I "developed
several scripts", and then further down I say I "developed a remote
backup script that saved us money". Hmm...
> It looks good - sounds a lot like my credentials - learning programming
> languages and the like.
I rather suspect there's quite a few computer experts in this newsgroup. ;-)
Damn, employers should be hiring from here!! o_O
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> OK, so I *think* I've taken nearly everybody's suggestions on-board.
> What do we think of this then?
Oooh much better :-)
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.
- 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.
- The remote backup script, add something like "This is in use daily to
ensure all blah blah files are correctly backed up" or whatever.
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!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v8 <voi### [at] dev null> 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.
>
Getting better
Personally I would miss out the word bright from
I am a bright computing graduate …
How about;
I am a computing graduate BSc (Hons) …
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v8 wrote:
>
> Damn, employers should be hiring from here!! o_O
>
If you were willing to get a work Visa and live in the U.S., and the
housing industry weren't in the toilet, then I'm sure I could find a
place for you to fit in here.
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Raiford wrote:
> If the housing industry weren't in the toilet,
Oh. You as well? :-D
Over here, prices seem to have gone on a more or less vertical climb for
the last few years now. Presumably at some point people will stop
actually buying, and prices will fall through the floor... In fact, for
all I know, maybe they already are?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v8 wrote:
> Mike Raiford wrote:
>
>> If the housing industry weren't in the toilet,
>
> Oh. You as well? :-D
>
> Over here, prices seem to have gone on a more or less vertical climb for
> the last few years now. Presumably at some point people will stop
> actually buying, and prices will fall through the floor... In fact, for
> all I know, maybe they already are?
>
People here aren't building, and values are sliding ... giving that, and
the whole sub-prime mortgage thing, yeah ... not a good thing.
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v8 wrote:
> Darren New wrote:
>> Personally, I'd leave "bright" in there. You'll have to decide. :-)
> OK. Fair enough.
For my thinking, it's telling them something about how you see yourself.
Certainly if you put "dedicated" or "loyal" or something in there, it
would be saying something else.
>> "Learned Tcl/Tk in a week" is misspelled.
>
> Damn. Now I have to figure out why it's misspelt...
My copy says "leaned Tcl/Tk." Unless *I* misread it. :-)
> Heh. You really do enjoy subtly implying that I'm more important than I
> really am, eh? ;-)
That's part of what you have to do.
> How about "rigourous recording of changes"?
Good.
> 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.
Uh, OK. Never heard that term. Maybe it's a British term.
"Underspecified" might be the term I'd use, but again you take a look
and decide. It just struck me as odd.
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 21-Nov-08 21:47, Orchid XP v8 wrote:
> 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!)
It does illustrate that you are not the social inept moron that you are
trying to pretend. Remember: they asked you to be on the team. You even
met IRL and you were not thrown out immediately. (The reason they asked
nor the reason why they keep up with you does matter, so don't give your
version in a job interview).
>> Tcl/Tk is in point 5 but not in 3.
>
> It's in point 2 though.
sorry missed that. That is probably a good sign.
>
>> 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.
irrelevant IMO, our lab is in a constant transition to more regulation
(partly because of the hype of the time and partly because the type of
research is changing) you seem to know at least partly what kind of
regulations are out there *and* you know how to implement such measures.
If someone here notices that they might even create a job description
for you just to get you in. Pity you seem to be stuck in that hole in
the UK.
> (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.)
I know a company that does do the labeling and the reason is simply that
they a) don't want to get sued for misdiagnoses because their system
happened to be in the same room. b) they are a small company that can
not afford expenses associated with the testing. and c) their
administration of the development and production is not even remotely
resistant to an medical grade audit. Not everybody can afford an Andy,
you know.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v8 wrote:
> OK, so I *think* I've taken nearly everybody's suggestions on-board.
> What do we think of this then?
One more comment by the way. Nowhere does it actually say "Windows", as
far as I can remember. You might want to mention you administered AD,
and that some of your scripts were work-arounds for design flaws in
roaming profiles, for example.
(What, you think nobody remembers what you complain about? :-)
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 Nov 2008 20:48:12 +0000, Orchid XP v8 wrote:
> Jim Henderson wrote:
>
>> "Troubleshooting" is a good general term for this, or "problem
>> diagnosis and resolution".
>
> Troubleshooting is the term I'd go with.
It's a good one; "problem isolation" is another that I've seen.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 21 Nov 2008 23:00:59 -0500, Jim Henderson wrote:
> On Fri, 21 Nov 2008 20:48:12 +0000, Orchid XP v8 wrote:
>
>> Jim Henderson wrote:
>>
>>> "Troubleshooting" is a good general term for this, or "problem
>>> diagnosis and resolution".
>>
>> Troubleshooting is the term I'd go with.
>
> It's a good one; "problem isolation" is another that I've seen.
Another that gets attention is "root cause analysis".
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 22 Nov 2008 00:43:08 -0500, Jim Henderson <nos### [at] nospamcom> wrote:
>On Fri, 21 Nov 2008 23:00:59 -0500, Jim Henderson wrote:
>
>> On Fri, 21 Nov 2008 20:48:12 +0000, Orchid XP v8 wrote:
>>
>>> Jim Henderson wrote:
>>>
>>>> "Troubleshooting" is a good general term for this, or "problem
>>>> diagnosis and resolution".
>>>
>>> Troubleshooting is the term I'd go with.
>>
>> It's a good one; "problem isolation" is another that I've seen.
>
>Another that gets attention is "root cause analysis".
>
Personally, I'd say fault finding ;)
Seriously, on this side of the Pond. The simpler the word or phrase the better.
I'd rather hire someone who could do a good job rather than talk a good job.
"Troubleshooting" is acceptable but it would be more applied to whole system
problems not individual equipment faults.
I think it's interesting that "fault finding" sounds like a "blame game" to
Darren. Here a phrase like "root cause analysis" would get the CV passed around
so everyone could have a good snigger. Again two countries separated by a common
language :)
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
>
Much better.
Many people have further comments about what could be improved. Some I
agree with, some I don't. You decide.
However it is now at the stage where the major improvements have been made.
I'd be much more likely to interview somebody based on this version.
Your original I would have declined without even reading it all the way
through.
So, stage 2 - Get applying.
Cheers.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 22 Nov 2008 08:32:56 +0000, Stephen wrote:
> On 22 Nov 2008 00:43:08 -0500, Jim Henderson <nos### [at] nospamcom> wrote:
>
>>On Fri, 21 Nov 2008 23:00:59 -0500, Jim Henderson wrote:
>>
>>> On Fri, 21 Nov 2008 20:48:12 +0000, Orchid XP v8 wrote:
>>>
>>>> Jim Henderson wrote:
>>>>
>>>>> "Troubleshooting" is a good general term for this, or "problem
>>>>> diagnosis and resolution".
>>>>
>>>> Troubleshooting is the term I'd go with.
>>>
>>> It's a good one; "problem isolation" is another that I've seen.
>>
>>Another that gets attention is "root cause analysis".
>>
> Personally, I'd say fault finding ;)
>
> Seriously, on this side of the Pond. The simpler the word or phrase the
> better. I'd rather hire someone who could do a good job rather than talk
> a good job.
>
> "Troubleshooting" is acceptable but it would be more applied to whole
> system problems not individual equipment faults.
See, over here, we troubleshoot everything from system-wide faults to
individual hardware component failures.
> I think it's interesting that "fault finding" sounds like a "blame game"
> to Darren. Here a phrase like "root cause analysis" would get the CV
> passed around so everyone could have a good snigger. Again two countries
> separated by a common language :)
Ain't that the truth. :-)
"Fault finding" to me does imply "blamestorming" as well - the result of
"fault finding" is that "it's your fault", so has a very negative
connotation in most parts of the US IME.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 22 Nov 2008 12:05:15 -0500, Jim Henderson <nos### [at] nospamcom> wrote:
>
>See, over here, we troubleshoot everything from system-wide faults to
>individual hardware component failures.
>
Lordy, lordy you'll have me speaking 'Merican yet. :)
>> I think it's interesting that "fault finding" sounds like a "blame game"
>> to Darren. Here a phrase like "root cause analysis" would get the CV
>> passed around so everyone could have a good snigger. Again two countries
>> separated by a common language :)
>
>Ain't that the truth. :-)
>
Tell me about it!
>"Fault finding" to me does imply "blamestorming" as well - the result of
>"fault finding" is that "it's your fault", so has a very negative
>connotation in most parts of the US IME.
I suppose that differentiate it by saying someone is finding fault.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 22 Nov 2008 23:08:31 +0000, Stephen wrote:
> On 22 Nov 2008 12:05:15 -0500, Jim Henderson <nos### [at] nospamcom> wrote:
>
>>See, over here, we troubleshoot everything from system-wide faults to
>>individual hardware component failures.
>>
> Lordy, lordy you'll have me speaking 'Merican yet. :)
One by one. ;-)
>>> I think it's interesting that "fault finding" sounds like a "blame
>>> game" to Darren. Here a phrase like "root cause analysis" would get
>>> the CV passed around so everyone could have a good snigger. Again two
>>> countries separated by a common language :)
>>
>>Ain't that the truth. :-)
>>
> Tell me about it!
Well, you see, you're in the UK, I'm in America, we both speak English
but we can't understand each other. I thought you understood that, but I
hope this clears things up a bit. ;-)
>>"Fault finding" to me does imply "blamestorming" as well - the result of
>>"fault finding" is that "it's your fault", so has a very negative
>>connotation in most parts of the US IME.
>
> I suppose that differentiate it by saying someone is finding fault.
I think the evolution of language, though, means that one who finds fault
engages in fault finding. ;-)
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
