[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Things are not what they seem - was RE: [xml-dev] Urgently n eeda reality check on the job market for XML development
- From: "Sterin, Ilya" <Isterin@ciber.com>
- To: "'Bullard, Claude L (Len) '" <firstname.lastname@example.org>,"'''email@example.com ' ' '" <firstname.lastname@example.org>
- Date: Fri, 21 Sep 2001 10:01:40 -0600
Jerry, this is in response to your private email as well as some more
Definitely as many have pointed out, your hobbies and what you do outside of
work is a great concern to many employers. Sure anyone can put on a one
hour act at the interview and most can do it for 8 hours a day, though
everyone wants to know what you do outside of that. First by showing that
you are involved in some projects outside of work (like open source
development, etc...) you are showing them that you enjoy your job and you
are not doing in for one sole purpose of gaining finances. That's a great
plus. If you are not currently involved in anything outside of work, maybe
you should investigate and get involved, see www.sf.net for some projects.
Also stating that you enjoy reading, researching, etc..., about your line of
work, in this case IT, also won't hurt you.
Definitely the problem is and has been, that most of the people who do the
hiring are not developers themselves and never have been. They rely either
on other standards which are not relevant to IT, or go by something they've
been told or have briefly encountered while reading. I think this is a
problem for IT folks as well as companies that are involved in any IT
development, since it decreases the quality of an employee since they
haven't been adequately tested. I can only recall a few interview where an
interviewer actually asked me technical (low level) questions to test my
development skills. Others stay on a high level project overview, which is
easily conquered by any candidate who has common sense and is willing to
prepare for the interview.
Again, I really don't think that the numerous projects which you have been
involved in will make a big impact on your job search. But if you still
believe it does, you might want to include some outside project that you
have been involved in or any research which has been long term. A good
example would be if you are interested in XML and is a regular on the list
for the past so many years and constantly follow the new proposals, etc...,
this can definitely be included in the hobbies section.
From: Bullard, Claude L (Len)
To: Sterin, Ilya; ''email@example.com ' '
Sent: 9/21/01 9:35 AM
Subject: RE: Things are not what they seem - was RE: [xml-dev] Urgently n
eed a reality check on the job market for XML development
For sure. Problem is, some systems are never "done",
they change with requirements, platform and infrastructure.
We need people who understand that and can live with it.
Even this isn't the problem. There are domains in which
the hard expertise is the subject matter expertise. Not
how to program, but "what". Given overlapping
responsibilities, an employer might favor someone who
can demonstrate both technical skills, fast learning,
good ability to analyze previously unfamiliar material,
and so on. And some jobs are not challenging. There
are probably more opportunities for grunt programming
than exciting innovative work. Someone with a low
boredom threshhold is not a good candidate for those
But Bray has the rules of thumb down pretty well,
particularly, what do you do in your spare time.
I'm interested in knowing that a bad day at the
office can be undone by a good night at the
<insert your hobby here>. Mental health...
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Sterin, Ilya [mailto:Isterin@ciber.com]
Sent: Friday, September 21, 2001 9:59 AM
To: Bullard, Claude L (Len); ''firstname.lastname@example.org ' '
Subject: RE: Things are not what they seem - was RE: [xml-dev] Urgently
n eed a reality check on the job market for XML development
Well actually you learn as you work, so you'll get way more than six
of work out of me or anyone else in this case. Most companies that
project, first hire a team of developers to complete, which is rarely
two years, though of course depends on finances, etc... Most of the
developers are later let go and only a few remain for system
etc..., which I don't really consider development. It includes making
changes as well as bug fixes. So sitting there and waiting for
break or for someone to approve a small change, is not my kind of
excitement. I work on projects that challenge me, so after the
conquered it's time to move on, or face not liking your job after a
Now I understand if you work for a software company, which initiates new
projects all the time, then yes, you can probably work there all your
since challenges will always come.
Again I never said anything about leaving before the job is done, but
leaving when your services are no longer ***really*** needed. Though
prefer to sit and wait until they are laid off while acting as if they
working on something. Seen it plenty of times. Even have seen
initiating a different project just to keep their job, although the
was not needed nor challenging to anyone.