On Tue, Mar 30, 2010 at 11:14:52PM -0400, Steve Bertrand wrote: > Hi all, > > This is perhaps a rather silly question, but one that I'd like to have > answered. > > I'm young in the game, and over the years I've imagined numerous job > titles that should go on my business card. They went from cool, to > high-priority, to plain unimaginable. > > Now, after 10 years, I reflect back on what I've done, and what I do > now. To me, if a business is loose-knit with no clear job descriptions > or titles (ie. too small to have CXO etc), I feel that a business card > should reflect what one feels is the primary job responsibility, or what > they do the most (or love the most). > > For instance, I like to present myself as a 'network engineer'. I have > never taken formal education, don't hold any certifications (well, since > 2001), and can't necessarily prove my worth. > > How does the ops community feel about using this designation? Is it > intrusive or offensive to those who hold real engineering degrees? I'm > content with 'network manager', given that I still do perform (in my > sleep) numerous system tasks and have to sometimes deal with front-line > helpdesk stuff. > > Instead of acting like I'm trying to sell myself out, I'll leave out > what I actually do and ask those who sig themselves with 'network > engineer' what they do day-to-day to acquire that title, and if they > feel comfortable with having it. > > Steve
I solve that problem this way: 1 set of Business cards with "Senior System Architect", an arbitary title the company gave me at some point 1 set of Business cards with "Senior Monkey for almost everything" -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://www.Alameda.net/~ulf/resume.html
