as someone that has experienced the pain of taking on jobs that other
developers abandonded and having to work with what they left, I would
absolutely not have a problem with what you left...i may not agree
with how you've done everything, but there is nothing there to say
that this code is unusable. it's even commented so i dont have to
spend time trying to figure out what you were thinking. I could post
some serious junk that ive inherited that you could compare that to
and you'd see a clear difference as to whats workable and whats not.
defintely agree with everything ryan said...I have a feeling either
these guys are scammers, which i have had the pleasure of working
with, or as stated above someone who is not an AS programmer looked at
the code, and saw "class", "public", "private" and "static" and
crapped their pants.
i'd say you definitely want to do what you can do to makee things work
out with the client, as long as they are being reasonable...after all,
you need to do what you can do to protect your reputation. but if
they are being unreasonable, cut your losses, and move on.
On 7/8/06, ryanm <[EMAIL PROTECTED]> wrote:
> I worked on it and squeezed it out narrowly by the deadline they had set.
> They were not happy at all. Supposedly the program is "not useable" by
> them
> (for reasons that haven't been explained to me, even though everything
> that
> was initially asked was implemented), and supposedly the code is "too
> complicated" for another programmer to continue work on it.
>
I played with it, it seems to do what it is intended to do, so as long
as what it does is what was defined in the spec, I don't see any problems.
Being too complicated for their other Flash guy is not your problem, unless
it was specifically mentioned in the specs that it should be done on the
timeline so that their guy can take over.
In my opinion, and I do enough freelance work to have experienced this a
time or two myself, you need to invoice them and tell them that if they want
further changes that it's a new project and will require a new quote. Tell
them you can only make it do the things they want if thery can tell you what
those things are, and you need to know *before* you start working on it in
order to be able to deliver it on time and within the budget. Make them
define "not usable" for you, and break it down to process flows that don't
work.
There is nothing wrong with the code that I could see. You delivered a
product, and you should get paid on it before you do anything else with that
client, IMO. If you value the client more than the cost of this one job,
then you might want to do some additional work to make them happy, but keep
in mind that once you set the precedent that you'll go above and beyond what
you were paid for, they will expect it in the future.
ryanm
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
