[tpm] So I've got an idea for a web site ..

[arocker at Vex.Net]

> application -- but I'd rather have someone else deal with the outter skin,
> whether that's the web application (which I could manage) or the actual
> HTML/CSS (which I could also do, but then again, I'm a left-brained guy,
> and my web page design reflects that).
>

Assuming that the application is something worthwhile (to the prospective
users), and whatever underlying data structures and process paths are
coded reasonably, the UI is likely to be the key to the project's success
or failure.

It's also the one bit the suits (think they) understand, and will be
tempted to "contribute". That's why I'd prefer to have a defined API
between it and anything I do. (My tolerance for revisions has
boundaries...) In fact, it's necessary to build flexibility into the
design, so that it can evolve with experience.

Abigail's talk at YAPC (2010?) about Booking.com's experience with site
design, (even though it was nominally about the limitations of Scrum), was
interesting.