 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
pNichols Guest
|
Posted: Sun Jan 18, 2004 1:35 am Post subject: Re: What comes first - Analysts and then programmers ... |
|
|
Nick Rambarransingh wrote:
| Quote: | Good Day All,
I have a question. Someone suggested to me that an Application
Developer is
higher in the "HIEARCHARY" than a Systems Analyst. Now, I will admit I
have not
been in school for a while, but I am sure this is not the case. Can
anyone clarify and put these skills in the proper order, from, lets say
cradle to grave - sot o speak.
Programmer
Programmer/Analyst
Developer
Application Developer
Systems Developer
Systems Analyst
Systems Engineer
Architect
Application Architect
Network Specialist
Network Engineer
I do not know if you can apply a general hierarchy by titles altogether. |
Different shops apply different categories and heirarchies. In fact you
will find most shops have their own nomenclature and hierarchal structure.
General (rough) rule in most IT companies I worked were (bottom to top)
Jr Level Programmer
Programmer
Programmer Analyst
Sr. Programmer Analyst
Team or Section Leader
Dept. or Section Manager
IT Manager
Assistant CTO
CTO
I am leaving out Project Managers, because their funtions are different.
They may be in the hierarchy as well, but since they are not usually
involved in the programming duties, but rather design, they are really in a
different class, although they may have supervisory duties as well.
I also left out DBAs, since their job duties are different, but the work
very closly with the PMs and programmers.
System Analyst usually have something to do with Network and/or System
Adminitration duties( ie configuring servers, Mainframes, scheduled
updates, coding and develping system utils, benchmarking plans, etc). Of
course, some may include these people in the Programmer's heirarchy. They
are usually, highly trained and skilled in several areas, such as
programming, Network administration, and security. In smaller shops, they
may be in the programmers general group and function not only as system
level programmers, but also form a utilities group. In larger IT shops,
they generally are assigned the duties as I described.
|
|
| Back to top |
|
 |
Nick Rambarransingh Guest
|
Posted: Sun Jan 18, 2004 3:22 am Post subject: What comes first - Analysts and then programmers ... |
|
|
Good Day All,
I have a question. Someone suggested to me that an Application Developer is
higher in the "HIEARCHARY" than a Systems Analyst. Now, I will admit I have not
been in school for a while, but I am sure this is not the case. Can anyone
clarify and put these skills in the proper order, from, lets say cradle to grave
- sot o speak.
Programmer
Programmer/Analyst
Developer
Application Developer
Systems Developer
Systems Analyst
Systems Engineer
Architect
Application Architect
Network Specialist
Network Engineer
Some of these do not belong together, and I am sure I am missing a few. So,
that being said, how should I sort & categorise these.
Thanks, Nick
Borland Forever ...
|
|
| Back to top |
|
 |
JD Guest
|
Posted: Mon Jan 19, 2004 9:24 pm Post subject: Re: What comes first - Analysts and then programmers ... |
|
|
Nick Rambarransingh <NRambarransingh (AT) Videotron (DOT) ca> wrote:
| Quote: | [...] Can anyone clarify
|
In a mainframe environment, skills are more specialized and a
Systems Analyst would be higher up because they would be the
one working with the end users and the programmers and the
techies.
They may not be writing the code, but they get everyone on the
same page as far as what's possible, what's not and what's
unexceptable. A Systems Analyst is usually the most skilled of
all of the others because of their duties and since skill
comes with experience, their usually the most senior (besides
management) and thus are by default higher up.
In contrast, the skills for a good Windows programmer mirror
those of a Systems Analyst simply because it's impossible to
write code without getting into every little thing that an
Application Programmer can avoid on a mainframe.
~ JD
|
|
| Back to top |
|
 |
Chris Gordon-Smith Guest
|
Posted: Mon Jan 19, 2004 11:52 pm Post subject: Re: What comes first - Analysts and then programmers ... |
|
|
Nick Rambarransingh wrote:
| Quote: | Good Day All,
I have a question. Someone suggested to me that an Application
Developer is
higher in the "HIEARCHARY" than a Systems Analyst. Now, I will admit I
have not
been in school for a while, but I am sure this is not the case. Can
anyone clarify and put these skills in the proper order, from, lets say
cradle to grave - sot o speak.
Programmer
Programmer/Analyst
Developer
Application Developer
Systems Developer
Systems Analyst
Systems Engineer
Architect
Application Architect
Network Specialist
Network Engineer
Some of these do not belong together, and I am sure I am missing a few.
So,
that being said, how should I sort & categorise these.
|
I'll refrain from attempting to put these into some kind of order of
precedence. However, I would like to say that your list of roles does not
reflect the increasing degree to which IT work is being outsourced from
developed countries to developing countries, particularly India.
This means that many roles are tending to move from the developed world to
the developing world, and there is now an increasing number of people in
developed countries whose job it is to manage the various categories of
work that have been outsourced to developing countries. Many of these
people may have skills that fall into some of the categories you list, but
the ability to manage work being done in a different continent is a skill
that is becoming increasingly important in a range of roles.
--
Chris Gordon-Smith
London
Homepage: http://graffiti.virgin.net/c.gordon-smith/
Email Address: Please see my Home Page
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|