Quote:
Hmm. Sounds the same as several projects that recruiters and contract
brokers tried to persuade me to take on (often they would have liked a
fixed-fee): *"Shouldn't take more than two weeks, it's 90% done, just finish
it and write a few reports."
Translation: "This customer's previous contractor fled screaming into the
night, they don't have any idea of what has been done, nor do they have any
documentation on what they want. *Just sign on this dotted line for a
lifetime of indentured servitude."
I'd put a <GRIN> in here, but it's not funny. *In some of those cases, I
know that unwary developers new to the contracting business actually tookon
the project -- with results that you and I can predict from the preceding
paragraph. |
Ha ha. This was my first Access developer hire on. It had started as a
paradox db. They hired a guy to convert it into Access but he left
without completing it. They then needed me to 'finish it' ie what he
started and didn't complete.
I had to accept the 1 month they gave to 'complete' the project. When
I told them I was rewriting it from scratched they asked why I wasn't
using the previous guy's design. I told them - because it will never
work.
Seven years later - they are still using that db I designed and
completed in 1 month. I've added a few reports since then but that's
about it. If I had the chance I would rewrite it differently only
because I have a different style now, but it works the way it's meant
to and provides automation of tasks the paradox db didn't handle.
This is the reason I love Access and in turn love vba/vb6. It's easy
to understand, easy to read, and doesn't ask for a lot of unneeded
complexity. I just wish they'd improve it on the code and editor level
but I'm probably just going to have to learn JavaScript and HTML5 -
which is a more realistic goal than trying to get a grip on .NET (for
me).