Here I am writing from the other side of the fence.
I find that some of the barriers to communication are rooted in the two
different 'cultures' of the two streams.
I recently had to work with a admittedly junior web developer to upgrade
static HTML pages associated with a web application which my group supports.
I mentioned to him that if he intended to change file structure he
needed to let me know right away so I could make parallel adjustments on
the application side.
Silence for 1 month followed by the return of the revised files in a
completely new file structure with all the the testing environment
dependent links changes to hard coded production links.
When challenged, he criticized the IT side for the slowness of posting
time. After all their web designers aim to get their changes made to
production in under 24 hours from the time they are requested.
SO... the whole job had to be done again - old file structure restored,
testing environment dependent links restored - and you can guess it
wasn't the 'web guy' doing it :)
These are the experiences that poison the well for worthwhile
co-operation. Both sides have stuff to learn from each other.
I feel fortunate that I have a foot on each horse. Somedays that
spangled suit I am wearing just doesn't seem that glamourous when trying
to explain to either side why they insist on doing things differently
from each other when judged by their own experiences it is patently
unnecessary. Aaaaagh.
Thanks for listening. Climbing down from my soapbox now :)
Mary Krieger
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
