Bruce,
I would regard SP as the "inside" job, designing, writing, testing, and
integrating code to accomplish some well-defined purpose. An SE would be
on the interface between "inside" and "outside", meeting with TPTB and
the end users to arrive at a set of specs that would then be reviewed
and/or revised with the SP to assess cost and schedule, thus defining
the purpose of the SP's effort.
In the dawn of history, an SE was the IBM sales team member who would
provide on-site training and act as the level 1 contact for solving
problems. By 1965 the SE became not much more than the guy you called to
order manuals, as all of them with half a brain were pulled into the
S/360 development effort.
Just my opinion and recollections...
Steve Samson
Bruce McKnight wrote:
Greetings all,
What is the difference between a systems engineer and a systems
programmer? I'm referring to the tradtional tech support staff members
in a regular company using mainframes for business purposes, not ISV
software houses or the like. It seems from the job postings I've seen,
there is no real consensus on the job title for our role.
I've seen a lot of job postings that don't align with what we do as
well. One job posting said "MVS Systems Programmer" but it was clearly
for an applications development role. "MVS Systems Administrator" has
shown up a few times with a role definition that was nearly a 100%
match.
TIA,
Bruce
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
