|
Seems to me like it has an abstract keyword appended to it. You're not having any thing to do, but still you're the base for doing everything. Wow!
Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem
~! Firewall !~
|
|
|
|
|
How about "The idiot who claims to know everything but is always busy for work."? 
I want that as my title, FFS.
|
|
|
|
|
Overseer lord of IT?
New version: WinHeist Version 2.1.0 Beta
Have you ever just looked at someone and knew the wheel was turning but the hamster was dead?
Trying to understand the behavior of some people is like trying to smell the color 9.
I'm not crazy, my reality is just different than yours!
Not my circus not my monkey's!
|
|
|
|
|
|
Everything sounds better with the word 'President' in it! But your colleagues will probably shoot down 'President (or Vice President) of Information Management Systems.' 
|
|
|
|
|
Amr Abdel Majeed wrote: No internal development, all projects assigned to vendors, closed box with no source code. (Boo  )
I work for a bank who did EXACTLY what yours is doing in the 90s, The absolutely WORST decision they have made in IT. Look for another employer, you will not be happy overseeing vendors unless you have a bent for it (management bleh).
A bank, or any large organisation needs internal developers, they MUST retain the IP to the system they are reliant on, not necessarily the big, core systems but the small gluey ones that make them unique, reporting and analysis mostly. These must be handled internally.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Amr Abdel Majeed wrote: what do you call a software developer, that doesn't do any development,
redundant
PooperPig - Coming Soon
|
|
|
|
|
Probably The Man.
Or the Project Trampoline. 
|
|
|
|
|
|
You are missing Ace of Spades on your list 
Anyway, I would go with something that has 'implementation' in its name.
Most probably 'Implementation Officer' (or even Manager, depending on whether you have or have not the decision making power).
'System Analyst' does not sound that bad either.
I saw some companies call similar people 'Product managers'...
|
|
|
|
|
|
|
May consider some religious terms: IT overseer, IT elder, IT bishop... 
IT project manager may be ok.
TOMZ_KV
|
|
|
|
|
Ive been given many titles in my 35+ yr it career on my business cards (when I was a wage slave), but when people ask 'what do you do' I always reply 'Computer programmer' (even though I do a lot more) coz most people have an idea what you mean, and it isn't as pretentions as some of the titles people give themselves. I had a self employed acquaintance who introduced himself as an 'IT director' for instance, or know salesmen who call themselves 'Business developers' when they mainly box-shift. (think of bin men calling themselves 'waste disposal technicians'). I think in your case 'IT Systems Analyst' has the right feeling and gets the message across. GL
|
|
|
|
|
Geek
probably though, Program Manager or Project Manager/Technology Implementation
AS someone else mentioned. If you are a programmer by heart. Start looking
To err is human to really mess up you need a computer
|
|
|
|
|
Amr Abdel Majeed wrote: So what do you call a software developer, that doesn't do any development, is involved in the technical aspect of projects and is on the receiving end of projects ?
Sounds like a project manager to me.
|
|
|
|
|
Project Coordinator; or something with "Quality Assurance" in it.
|
|
|
|
|
To me, it sounds like the Scrum role, Product(s) Owner.
Owners get paid a lot, right?
|
|
|
|
|
As an "owner", I would not put up with any of this nonsense.
|
|
|
|
|
Innovative Quality Usefulness (of) Information Technologist - IQUIT for short.
We used a variation of that at my last job.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
DEREK.
Tell everyone it's an acronym, and look at them as if they're stupid for not knowing it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I don't agree with your view of support. I worked mostly on projects for many years, but always managed to do some support as well. Apart from helping people who would have been helped much more slowly (if at all) by the formal processes it gave me the following benefits.
1. A better understanding of what is really going on in the user community
2. Often, a problem / investigation is also a learning experience
3. It widened my contacts within the business so whenever I needed help from someone in country X or function Y, I had a good chance of finding it quickly and easily.
So by all means work mainly on projects, but never give up support completely.
Roger
|
|
|
|
|
The Grand Poobah of Systems Analysis and Integration
You're welcome.
|
|
|
|
|
|
Isn't it telling you that it's configuring? 
Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem
~! Firewall !~
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
