Skip to content

RailsConf: UI in Rails

by Topper on May 30th, 2008

The talk is highly geared to working with designers that already know HTML and CSS. Unfortunately, that’s a limited subset. I’ve been lucky enough to work with a lot of them. I wonder how you convince designers not working in HTML to start picking it up.

One of my favorite points is that developers should be talking to the design side about things like REST and some domain modeling. Currently, we tend to name and model things on the dev side which can make talking about products more difficult.

Part of any complicated process should be explaining the higher-level doctrines of rails as best we can and then getting into the nitty-gritty of the domain we’re targeting. I think sometimes both sides tend to forget about the need to just be able to fluidly discuss the project we’re working on.

I wonder if it’s possible to take the idea of small iteration and apply it to the more walled metaphor of photoshop -> html -> rails -> designer -> photoshop -> rails

From → Social Web

  • Mike

    OK, I had to look up REST (“Representational State Transfer”) but is this new? What am I missing? Could be I haven’t found a good definition of it.