CSS - Css & Rapid Developemnt: Workflows?

Hi there,

I'm working with a developer on a Ruby web app - me doing the webdesign programming - and we've had some arguments on workflows. So I'd be interested in learning how this issue is treated anywhere else

For the prototype presentation we agreed on an easy 2-column-layout. So I revised the developer's "dirty" html into valid xhtml and created the initial stylesheet, which works nicely. We have sort of an incremental work routine: The developer adds new features or controls to the view almost daily and I update the xhtml/css.

This way we've run into quite a lot of arguments: The developer complains that the layout is "unpredictable" because he doesn't understand css positioning. Elements he adds to the view don't appear where he wants them to, overlap, aren't shown at all... and so on.

Finally he demanded that I'd establish the layout as a table (Apple people do it this way! see http: //developer.apple.com /internet/ webcontent/ bestwebdev.html), which he knows his way around.

Since we do have accessibility guidelines at our company, my problem is that, eventually, I'll have to turn this ugly table thingy back into p-css.

Apart from that, the developer hasn't understood yet that the css-table-model doesn't really work as in the good html4.01-times...

So I'm wondering what kind of workflow we could establish taking both our needs into account...