My 360|Flex presentation
“What's in a name? That which we call a rose By any other name would smell as sweet.” - W. Shakespeare
Until recently, the title for my 360|Flex San Jose presentation next month was “Designer Last Development Architecture”. But that has just changed.
In “Confessions of a Public Speaker” Scott Berkun says “Start with a strong title”. I wish he'd told me that sooner. “Designer Last Development Architecture” is not a strong title. It's more like a jumble of words. Fortunately, it's not too late to change it.
While planning the presentation, two alternative titles have occurred to me.
Empowering your designers with smart components
This title sounds strong. But it's still not right unless you know what smart components are, and since that's a name I made up it's unlikely you will know.
Transforming the designer-developer workflow
This gets to the heart of what the session is about. It also uses terms that most readers will understand, which is always a good idea.
It does leave out the technical aspects of architecture, components and code (I'll be doing some live coding to show you how easy this architecture is to work with), but since 360|Flex is a technical conference, I trust you'll expect lots of code anyway.
Perhaps the strongest way to express what my presentation will be about is with a picture.
And that's the transformation I'll be talking about, with architecture, code, and anecdotes from my own experience.
So at 360|Flex San Jose, the session formerly known as “Designer last application architecture” will henceforth be known as “Transforming the designer-developer workflow”.
If you want to know how to transform your designer-developer workflow, what smart components are and how to write them, how to empower your designers, how to free your developers from the client project cycle, and why this makes development more enjoyable, come join me at 360|Flex San Jose.
The slides from this presentation are now online here.
Also in the collection Conferences