Comments on: Vanity naming conventions for software engineers http://brainsnorkel.com/2006/02/04/vanity-naming-conventions-for-software-engineers/ Manifesto-driven development. Eclectic thoughts. Tue, 14 Feb 2012 13:12:08 +0000 hourly 1 By: Chris http://brainsnorkel.com/2006/02/04/vanity-naming-conventions-for-software-engineers/comment-page-1/#comment-4882 Chris Mon, 20 Feb 2006 09:16:53 +0000 http://brainsnorkel.com/?p=235#comment-4882 <blockquote> 7. IT Systems Engineer (Because Engineering complained that they already had someone with title Systems Engineer) </blockquote> Hah. So many times I've had that problem. Recruiting, setting up teams, integrating other teams... systems engineering is all things to all people :)

7. IT Systems Engineer (Because Engineering complained that they already had someone with title Systems Engineer)

Hah. So many times I’ve had that problem. Recruiting, setting up teams, integrating other teams… systems engineering is all things to all people :)

]]> By: Tony http://brainsnorkel.com/2006/02/04/vanity-naming-conventions-for-software-engineers/comment-page-1/#comment-4880 Tony Mon, 20 Feb 2006 07:24:51 +0000 http://brainsnorkel.com/?p=235#comment-4880 hehehe I haven't had too many job titles (that I can remember) from first to last: 1. Trainee computer operator (hehehe and I changed tapes ;) ) 2. Computer Operator 3. Industrial Trainee (systems programming using cobol of all things) 4. Operations Supervisor/Trainee Systems programmer 5. Job with no title at all how sucky is that!! (writing data conversion programs for Mainframe to Unix migration) 6. Systems Engineer 7. IT Systems Engineer (Because Engineering complained that they already had someone with title Systems Engineer) Tony. hehehe I haven’t had too many job titles (that I can remember)

from first to last:

1. Trainee computer operator (hehehe and I changed tapes ;) )
2. Computer Operator
3. Industrial Trainee (systems programming using cobol of all things)
4. Operations Supervisor/Trainee Systems programmer
5. Job with no title at all how sucky is that!! (writing data conversion programs for Mainframe to Unix migration)
6. Systems Engineer
7. IT Systems Engineer (Because Engineering complained that they already had someone with title Systems Engineer)

Tony.

]]> By: Tony http://brainsnorkel.com/2006/02/04/vanity-naming-conventions-for-software-engineers/comment-page-1/#comment-4873 Tony Sat, 18 Feb 2006 07:41:36 +0000 http://brainsnorkel.com/?p=235#comment-4873 hehehe I haven't had too many job titles (that I can remember) from first to last: 1. Trainee computer operator (hehehe and I changed tapes ;) ) 2. Computer Operator 3. Industrial Trainee (systems programming using cobol of all things) 4. Operations Supervisor/Trainee Systems programmer 5. Job with no title at all how sucky is that!! (writing data conversion programs for Mainframe to Unix migration) 6. Systems Engineer 7. IT Systems Engineer (Because Engineering complained that they already had someone with title Systems Engineer) Hopefully this one won't be blocked as SPAM!! Tony. hehehe I haven’t had too many job titles (that I can remember)

from first to last:

1. Trainee computer operator (hehehe and I changed tapes ;) )
2. Computer Operator
3. Industrial Trainee (systems programming using cobol of all things)
4. Operations Supervisor/Trainee Systems programmer
5. Job with no title at all how sucky is that!! (writing data conversion programs for Mainframe to Unix migration)
6. Systems Engineer
7. IT Systems Engineer (Because Engineering complained that they already had someone with title Systems Engineer)

Hopefully this one won’t be blocked as SPAM!!

Tony.

]]>