🚀 go-pugleaf

Now, pay attention:  I said that Y2K is rapidly becoming an
untouchable problem; I did not say that Y2K is becoming an
unsolvable problem.

The reason I am characterizing Y2K thus is because too much
time is passing.  Capable programmers have enough intelligence
to turn down all Y2K job offers no matter how much green is
waved under their noses.  This is because they are savvy enough
to deduce that any installation which has waited this long to
address Y2K is probably plagued with untenable human resource
problems, particularly in management.

What capable programmer is going to be willing to leave his
current job to take the big risk of walking into a pit of an
environment where there is inept management, gross incompetence,
and the prospect of having to face 20,000,000 lines of code
that have to be converted yesterday?  I have witnessed situations
which were not to the liking of programmers who walked within
short order, sometimes in less than a day, and capable programmers
are the ones most likely to do so.

Now where will this leave installations that are pits of
environments?  Up the creek, that's where.  But there is
an alternative.

The work can be sent to India where people are very well
experienced with things of an untouchable nature.

We can have the "Open and Shut Window Technique" Y2K correction
code inserted into your programs with or w/o testing as desired!
No problem!  Reasonable rates!

The "Open and Shut Window Technique" can be found at url:
http://www.geocities.com/ResearchTriangle/3462/

If you have not seen the latest version of this web page which
includes the absolute value function in the sample code snippet,
then you are advised to pay a revisit.

Comments to: dashl...@geocities.com

Dash Langan
--
We're not yellow.  We go anywhere.