FilePro Programmer Needed

[Fairlight]

Only Dr. Martin would say something like:
> 
> Programmer needs to be able to read VB to understand how the FilePro 
> processing needs to be written. Must have program finished by end of June.

What self-respecting individual would commit to a deadline in advance of
applying for a position (or contracted job) without seeing the scope of the
project, or having done at least a summary analysis of the existing code?
Or at least having a description of what the program actually -does- in the
broadest context?  None that I know of.

"Must" is a dangerous word.  A place down in Florida wanted to do ecommerce
on their web site to hook into a fP-based PoS/Inventory/Accounting
system on which pretty much everything they do relies.  I was to do that
integration work along with the original fP programmer.  Client then
backtracked, said he HAD to have it by August 1 (it was mid-June when
he decided he'd send out RFP's instead of just having me work with the
developer--who had recommended me!--as planned), when I told him it was
not only unreasonable, but infeasible.  Common wisdom says that you don't
expect a transition of a major segment of a web site like that inside six
months to get through development, alpha, and beta, but he insisted he
"must" have it within 1.5.  I told him I'd take a pass, good luck with
those RFP's.  Nothing personal, it was technically infeasible.

So he went and got one of these fancy web design firms local to him.  They
redid his web site after a -year-.  It's been six years plus and running
and he -still- doesn't have online ordering for his fP-based solution, all
because he wouldn't listen in the first place.  The original fP developer
knew I knew what I was talking about, especially combined with what was
involved in coordinating (and we both had other clients to work with as
well).  And he backed me.  Actually, the fancy design place couldn't
-possibly- do what they promised and what was required, because they didn't
know fP, and the fP developer was suddenly too busy to work with
them--although they'd have made time for me had I been on the project.  It
-required- thorough knowledge of fP, or heavy collaboration.  They weren't
getting either.  fP knowledge isn't exactly readily available in most parts
of the computing world.  Be happy if they've even heard the name and
haven't confused it with FileMaker Pro.

But--I told him six months.  It's been more than twelve times that, and he
still doesn't have what he "NEEDED" in 1.5 months.  Apparently he's doing
just fine without it, too, as they're still very much in business.  And
every year, they're going to do this project, and every year they start far
too late for their proposed deadline.  I've given up hope of ever seeing
them actually -do- the project, honestly.  I don't think it'll ever happen.
And it's because they're approaching it backwards--deadline first,
mechanics second.

But this shows you what "must" really amounts to in most cases.  This is
typical thinking in this day and age--especially from people that have no
concept of what's really involved, but just haul off and make a decision
that something must be done, and done by 'x' to cap costs.  I've watched
more than a few places screw themselves into the ground that way--sometimes
quite expensively.

My point is that, going against a relatively standard industry metric,
you want a conversion from VB (fairly standard) into fP (NOT standard,
good luck finding anyone that wants to work with both at once that's not
already spoken for), of an unknown quantity and quality of features, by
a certain hard date, and stipulate that (in so many words) the qualified
applicant will be able to do the job within those constraints.  

Where is this psychic programmer that already knows what you have and
know they can do it "no matter what", without ever having seen byte one
of what you have in place?  They don't exist.  Ergo, your request is
counterproductive, as it makes assumptions about the prospects knowing
things they can't possibly know in advance of contacting you.

It's on grounds like these that a little red flag goes up for me and says,
"DANGER!  DANGER, WILL ROBINSON!"  And I rapidly back away from such
potentially nasty situations.

> Contact Dr. Martin at 602-615-7999 (cellular) or DrMartin at gamgroup.com if 
> you are interested in quoting this project. You may fax resume, background 
> to: 480-596-1031.

Interested in quoting on it? *chuckle* I shouldn't expect too many (if
any) serious inquiries, and I'd treat any you do get with the utmost of
skepticism.  It's the end of May right now.  You're giving one month to
something that, unless it's -really- trivial, probably needs far more than
that to be analysed in VB, plotted and flowed for fP, coded in fP, alpha'd,
beta'd, and finally given the seal of approval.  By the time they quote
on it, it goes back and forth for approval, etc., a week's generally gone
by one one side or both.  That leaves three weeks to do something...not
yet even narrowly defined, and get it right the first time.  Not going to
happen.  I can almost guarantee it.

And to top it off, you don't even say what the application currently
-DOES-.  Warning sign number one:  Prospectively client has many "needs"
and demands, yet has trouble elucidating -exactly- what is entailed, even
in the broadest context.

So yeah, anyone applying for this and saying they can do it in that time
frame--and oh, by the way, can they please see the code so they can quote
you a pricetag for their wizardry...  Yeah, I'd kinda of be wary of someone
that says they can deliver when they haven't even seen the existing part
of what they're working on.  I don't correspond with anyone nuts enough to
open that kind of can of worms.  Any any that do...well, you're inviting
the trouble yourself by the very nature of how you're approaching the
hiring/contracting process.

My advice:

First outline the project in at least -some- greater detail than you did
("a VB program" is NOT descriptive of even the -general- purpose of the
software), get someone that's interested in doing the project at all, then
get their opinion on how long it -should- take by -their- estimate.  If you
respect their judgement enough to consider them, you should respect their
estimate of what it will take.  If that's still not fast enough for you,
-then- apply the "must have by" constraint and watch the price probably
double or treble, possibly quadruple.  But at least you'd know the person
talking to you is going to be more reasonable than what you're inviting
with your current backwards approach.

Sure, I could apply for something totally unknown and promise the moon.
I'd be a dead liar if I did it with the original sight-unseen and nary
a description beyond "...a VB program".  Anyone would.  Which is my
very point--you're inviting (possibly expensive) failure.  You're actually
-asking- to be taken for a ride, honestly.

Good luck on that.

mark->