Steven Sacks wrote:
Please warn us when you are going to do this, since from the
tone of the
conversation, there is some sense that this will cause the end of
civilization as we know it.
Hacking the swf to increase the timeout is not the solution, it's a band-aid
on a gunshot wound.
Maybe he is only nicked and a band-aid might do the job. It is hard to
tell without reading all 50,000 lines of his code.
In the real world, sometimes you only need to fix the problem in the
current release and can fix the design in the next version. Patches are
allowed and many patches do not make it into the next release because
the underlying problem goes away with a redesign.
It is impossible to tell if his application will blow up after the
timeout is increased but it is unlikely that it will cause the rest of
us much of a problem.
Ron
I have over 20 years of programming experience including at
assembler level, advanced Java, etc, but thanks for trying to
put me in my place :-)
Let's say for argument's sake that it is a bug and it is all Macromedia's
fault and they won't fix it and life is unfair. That doesn't change the
fact that your application needs to work to your client's expectations. You
need to find a solution because that's what you're paid to do.
You hit the nail on the head here - "your application needs to work to
your client's expectations"; not to ours or not to be perfect.
As Danny Kodicek knows coming from a Director background, there were tons of
bugs in Director and workarounds had to be figured out to make certain
things work. John Dowdell, in his infinite wisdom, got on Direct-L and
posted that Director had no bugs, that there was just application behavior
that Director developers wished worked differently.
At the end of the day, I don't tell my client "Sorry, it's a bug and I can't
work around it". I figure out how to get it done, and so should you and
everyone else who does this for a living. The place I'm trying to put you
in is "Flash Developer". ;)
Noble sentiments but sometimes in the real world you have to tell a
client "Sorry it is a bug/design artifact in the underlying software and
I can not fix it or implement a work-around in the budget that you want.
Furthermore, the cost of fixing it exceeds the value to the organization."
In my work, I can not just charge clients money with no accountability.
They expect me to make reasonable judgements about the value of my
activities and not to just spend time because I have an ego-driven need
to get a "perfect" solution. I need to be able to explain my position
and to demonstrate how my recommendation is in the client's best
interest. I do not always know when to quit but not quiting or not
accepting a "good enough" solution is not a virtue (at least not in the
eye of the guy paying for it).
Ron
_______________________________________________
[email protected]
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
