how about "Paid Nerd I" and "Paid Nerd II" ???

>Attributes of titles:
>
>1. No one understands the significance of your title- this gives your position a sense of mystery.
>
>2. Titles are given in place of financial compensation.
>
>3. You can wear two or more neck ties with a new title.
>
>4. A title gives you self-importance – no one else cares.
>
>5. When applying for a new job previous titles can be a hindrance to the applicant. Each company calls a position by a different term. If you do not use the correct term used in house surely you do not have the correct qualifications! That is a basic rule of HR, and add to that Head Hunters! Neither have a clue about reality. They are only interested in the Empire they have created.
>
>By the way I have had many titles while working as a software developer. I presently enjoy the title of “Staff Specialist”. What the hay is a “Staff Specialist” you ask? Why I am a senior programmer!
>
>How about the titles given over the last twenty years to the industry that we are a part of? MIS / IS / IM / IT. Each of these variations has given we mere mortals a feeling of self-esteem. By changing the title of our industry you insure our importance to the world. Change your present job title and feel the rush!
>
>During the mid 1960’s I was in the Air Force. A cup of coffee was five cents! We had a joke that went, “For a nickel and all my Air Force medals, I could buy a cup of coffee”! What can you buy with a title?
>
>Tom
>
>
>
>
>
>
>>We are in the process of redoing our job titles, and I need a little help. There are only two of us developers in this small company. With recent changes, I am now the senior developer/analyst having been here 1.5 years while the other guy (who reports to me) has been here about 5 months (for most of which, he was a temp). He's full-time now. We both do design/development while I handle most of the day-to-day support as well as some managerial/supervisory duties (although I'm not a manager, technically). I head the development aspect, but I report to the Network Admin. It's strange, I know.
>>
>>Originally, I was thinking of being the Systems Analyst and him being the Software Engineer. The problem with that is that the Systems Analyst typically isn't involved in much development (at least from what I've read). Also, the Systems Analyst/Software Engineer relationship seems disjoint. What I mean is that the two don't seem to fit in the hierarchy that we have (where he reports to me). Then we were thinking Systems Analyst II and Systems Analyst. That solves the problem of the hierarchy, but the other remains. Also, it seems odd for a company so small (less than 20 employees) to have two Systems Analysts.
>>
>>I know job titles are almost technicalities, but I just wanted to get as much info on this as possible before deciding. Does Programmer/Analyst and/or System Architect fit in with these others? Previously, I was the "Applications Programmer Analyst" and he was an "Assistant Programmer", but we have long outgrown those titles, especially considering our recent promotions.
>>
>>Thanks
>>
>>-Nirav