RE: Things are not what they seem - was RE: [xml-dev] Urgently n eeda reality check on the job market for XML development

["Bullard, Claude L (Len)" <clbullar@ingr.com>]

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 
jobs.

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...


Len
http://www.mp3.com/LenBullard

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: Sterin, Ilya [mailto:Isterin@ciber.com]
Sent: Friday, September 21, 2001 9:59 AM
To: Bullard, Claude L (Len); ''xml-dev@lists.xml.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 months
of work out of me or anyone else in this case.  Most companies that start IT
project, first hire a team of developers to complete, which is rarely over
two years, though of course depends on finances, etc...  Most of the
developers are later let go and only a few remain for system maintenance,
etc..., which I don't really consider development.  It includes making minor
changes as well as bug fixes.  So sitting there and waiting for something to
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 challenge is
conquered it's time to move on, or face not liking your job after a while.
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 life,
since challenges will always come.

Again I never said anything about leaving before the job is done, but rather
leaving when your services are no longer ***really*** needed.  Though most
prefer to sit and wait until they are laid off while acting as if they are
working on something.  Seen it plenty of times.  Even have seen developers
initiating a different project just to keep their job, although the project
was not needed nor challenging to anyone.