RE: Security and iSeries Navigator Management Central

["Don" <dr2@xxxxxxxx>]

Dennis,

I'll take your comment a leap further.  It's REALLY NICE when a developer
knows more about the big picture they're working in besides how to write
code.  

DR2

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Friday, July 23, 2010 1:54 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Security and iSeries Navigator Management Central

Spoken like a true developer.  :)

The roles are interrelated, but neither is a subset of the other.  A
developer, for example, probably shouldn't ---depending upon environment---
need to understand what users are defined on the system, how much memory is
available, how taxed the CPUs are at the present time, what configuration
parameters are used for a certain object, what IP address(es) the system
uses, et cetera.

A properly configured system should be workable from a developer standpoint
without any of this knowledge (and so much more!).

But it is good when the developer and the admin know as much as possible
about each other's responsibilities.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Always live within your income, even if you have to borrow money to do so."
        -- Josh Billings 


> > Hey what can I say, I'm not the admin here....just a lowly
> > developer...so of course I can't know anything about admin or
> > security.  :/
>
> A developer should always be a superset of what an admin knows. After
> all, when developing an application, security should always come
> first. At least that's my understanding.