Re: Did I write a good (efficient) program?

On Thu, 03 Apr 2008 10:01:01 -0600, Howard Brazee <howard@[EMAIL PROTECTED]
>
wrote:

>On Thu, 03 Apr 2008 11:46:22 -0400, SkippyPB
><swiegand@[EMAIL PROTECTED]
> wrote:
>
>>Probably my fault.  I wasn't following the thread that closely and I
>>obviously missed the sarcasm.  I, however, can understand why
>>applications' programmers may have difficulty doing systems work.  If
>>you are knowledgeable in IBM Assembler, then systems work should not
>>be that difficult.  However if you've spent your whole career doing
>>COBOL, RPG etc, it would be difficult to make the transition.  
>>
>>Although nowadays there is little need to dive down into the nuts and
>>bolts of things like it used to be in the late 70's and early 80's
>>when I was doing that sort of thing.
>
>Just like everywhere else - we use bigger components.    But when the
>*system* now can include parts that aren't anywhere near the computer
>room, the scope is different.
>
>>On the other hand, a lot of systems programmers could graduate to
>>applications work though I think most would find it distasteful.
>
>Applications are what pay for everything.   But systems work now moves
>into interfacing with people, creating secure & private business
>practices and such.

True.  The systems people that I still talk with are more involved in
putting up secure networks than installating the latest release of
zOS.  Not that they don't do that, it is just that the operating
system changes and third party systems like schedulers, remote print,
transmissions, etc. etc. have fewer revisions per year and there are
more pressing needs.  Security and DASD management are highest on
their lists.  

Regards,
          ////
         (o o)
-oOO--(_)--OOo-

"Save the whales. Collect the whole set."
-- Steven Wright
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Remove nospam to email me.

Steve