hello,
I've been doing web design for a couple of years now. As much as I feel that I have learned I continue to get blindsided by frustrating technical problems. I try to proof, test, proto-type all the things that I think might be an issue, but the issues end up being things I never would have thought of.
Like:
My JavaScript won't work in browser x on platform x when the trigger event it is placed in an image map.
Or the flash animation that worked so smoothly in browser x plays jerky in browser y.
etc.
So, my questions are:
Do these problems become fewer and fewer the more experience you acquire? Is this just the nature of the beast? Is the answer 'just stay away from the bleeding edge'? What methods do you use to side step problems like these, and if you fail to side step the problem how do you deal with it in the middle of production?
Discuss amongst yourselves.
Jaxon
I've been doing web design for a couple of years now. As much as I feel that I have learned I continue to get blindsided by frustrating technical problems. I try to proof, test, proto-type all the things that I think might be an issue, but the issues end up being things I never would have thought of.
Like:
My JavaScript won't work in browser x on platform x when the trigger event it is placed in an image map.
Or the flash animation that worked so smoothly in browser x plays jerky in browser y.
etc.
So, my questions are:
Do these problems become fewer and fewer the more experience you acquire? Is this just the nature of the beast? Is the answer 'just stay away from the bleeding edge'? What methods do you use to side step problems like these, and if you fail to side step the problem how do you deal with it in the middle of production?
Discuss amongst yourselves.
Jaxon