Vitaliy wrote:
> Have you ever worked with contractors/been a contractor yourself? 

Been a contractor twice...

#1: The Database
I was asked to develop a database. The goal was basically to have something 
that would track what engineers were working on a given job, what parts they'd 
used, and how much to bill the customer (including VAT calculations). On top 
of this, it had to be accessible from the engineers' mobile phones and/or laptops.
Biggest mistake: starting without a well-defined spec. Customer kept adding 
stuff, and adding stuff (more like emailing me and asking "can you do X as 
well, it's probably only a small thing"). It took about five weeks to get a 
90% working prototype, which passed all the Baseline and Financial tests 
(basic functionality and "it calculates numbers properly"). After that, two 
more weeks to get far enough through the "additional functionality" list that 
the client would consider paying. Even after the app was "done", it took 
another four weeks to get the client to pay. They've asked for work since, but 
don't seem interested in answering my questions ("we want it to print job 
labels too" / "what printer are you using and what do you want on the label" / 
<silence>). Then I usually get an email two weeks later -- "Why are you 
ignoring us?"

#2: The Simulator
A local council was doing energy-efficiency "audits" (probably the wrong word, 
but there you go). Basically going into people's houses on request, and 
checking over the heating boiler and timer controller, helping the occupiers 
get their bills down and so on. Problem is, people don't read manuals, and 
their existing "demo box" (used to teach people how to program the timer 
switches) was basically a timer controller, two lightbulbs, and a bit of wire. 
"Demo" used in the loosest term -- there was no way to make the clock on the 
switch run faster, so you basically had to set it a few minutes after the 
current time, and wait. Not exactly ideal.
In this case, I had a 2-hour meeting with the managers who wanted this doing, 
and left with an A4 refill pad full of notes, a timer-switch and a couple of 
batteries (turns out the switches worked off mains or DC -- quite odd). Two 
weeks later I sent them a preliminary design, and a work estimate (rough time 
taken, hourly rate, estimated total cost including 15% margin of error and a 
disclaimer to the effect of "this is not a final estimate and should not be 
considered binding"), and was told "we were under the impression you were 
doing this as part of your university coursework" (read: we want it doing for 
free). Um, nope. "Well, we won't be pursuing the contract then. Thanks for the 
design documents though."

At this point, I've basically given up on contracting...

-- 
Phil.
piclist@philpem.me.uk
http://www.philpem.me.uk/
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist