2008/6/17 Rick Welykochy [EMAIL PROTECTED]:
Jamie Wilkinson wrote:
2008/6/12 Jeff Waugh [EMAIL PROTECTED]:
quote who=Rick Welykochy
I've always pondered where to draw the line between sys admin and
programmer /analyst.
Wherever you draw it, draw if very firmly. Sysadmins should not write
2008/7/1 Jamie Wilkinson [EMAIL PROTECTED]:
2008/6/17 Rick Welykochy [EMAIL PROTECTED]:
Leave programming in the large to analysts.
I still have to disagree with you.
snip
(Despite the two weeks I've had to think of more examples, I can only
think of one in the public eye. I do not
2008/6/12 Jeff Waugh [EMAIL PROTECTED]:
quote who=Rick Welykochy
I've always pondered where to draw the line between sys admin and
programmer /analyst.
Wherever you draw it, draw if very firmly. Sysadmins should not write code,
Bollocks.
coders should not administer systems. Heinous
Jamie Wilkinson wrote:
2008/6/12 Jeff Waugh [EMAIL PROTECTED]:
quote who=Rick Welykochy
I've always pondered where to draw the line between sys admin and
programmer /analyst.
Wherever you draw it, draw if very firmly. Sysadmins should not write code,
Bollocks.
I've yet to meet a
quote who=Rick Welykochy
I've always pondered where to draw the line between sys admin and
programmer /analyst.
Wherever you draw it, draw if very firmly. Sysadmins should not write
code,
Bollocks.
I've yet to meet a sysadmin who does not write code. But I classify it as
scripting.
[EMAIL PROTECTED] wrote:
What you are after is actually a programmer... who can write that sort
of thing..
Ya think?
I've always pondered where to draw the line between sys admin and
programmer /analyst.
Many sys admins I work with can whip up shell scripts and are whizzes
at handling
quote who=Rick Welykochy
I've always pondered where to draw the line between sys admin and
programmer /analyst.
Wherever you draw it, draw if very firmly. Sysadmins should not write code,
coders should not administer systems. Heinous crimes are committed when the
streams are crossed!
Many
Hi Rick,
Quoting Rick Welykochy [EMAIL PROTECTED]:
I've always pondered where to draw the line between sys admin and
programmer /analyst.
Well there's definitely a difference... but there are true sys-admins,
true programmers and some who seem to be able to do both.
Which raises the
[EMAIL PROTECTED] writes:
Quoting Rick Welykochy [EMAIL PROTECTED]:
I've always pondered where to draw the line between sys admin and
programmer /analyst.
Well there's definitely a difference... but there are true sys-admins,
true programmers and some who seem to be able to do both.
Like
Daniel Pittman wrote:
That said, don't discount the risk that a programmer might wander in
here as well. :)
You're talking (?) to one. I enjoy the SLUG list since I have
programmed some largish systems on Linux for the enterprise
and when I'm at the coal face I need sys admin skills, as
Hi all,
First, thanks to everyone who assisted with my
previous exploits. It appears the reason I
couldn't get the command to work was I had an
earlier version of Imagemagick. Again, thanks to
all, your assistance is very much appreciated -
not least of all by the relatives who 'stare in
2008/6/12 elliott-brennan [EMAIL PROTECTED]:
Hi all,
First, thanks to everyone who assisted with my previous exploits. It appears
the reason I couldn't get the command to work was I had an earlier version
of Imagemagick. Again, thanks to all, your assistance is very much
appreciated - not
Hi Amos,
And you are so right!!
Thanks for that. My fault. I should have read the
earlier posts.
Much appreciated.
Amos Shapira [EMAIL PROTECTED]
Thu, 12 Jun 2008 13:47:59 +1000
2008/6/12 elliott-brennan [EMAIL PROTECTED]:
Now, I have another goal I'm seeking assistance with.
snip
Elliott,
What you are after is actually a programmer... who can write that sort
of thing..
Usually there are two ways - pay with beer or cheques or other sort of
favours... :-)
I can't see any way past it...
you are in industrial-land... plenty of people out there who might
want to
14 matches
Mail list logo
