Re-Architecting the Designer-Developer Workflow

Richard Lord

Most application development follows a pattern where the designers design it then the developers build it. Any change in the design requires more work from the developers, who have to implement each change request.

It doesn’t have to be this way. By modifying the application architecture, we can enable the developer to do their work before the designer, leaving the designer free to alter the design as frequently as they wish without recourse to developer time.

This frees designers to respond to client requests in a timely manner and frees developers to work on a more strategic level, adding functionality to the tools the designers use without being bogged down in day-to-day client projects.

In this session I’ll describe this new architecture, how and why I developed it, the benefits and pitfalls of its use, and how to implement it using any of the current dependency injection frameworks.

This movie requires Flash Player 9

2 Responses to “Re-Architecting the Designer-Developer Workflow”

  1. Eric Hélier says:

    Very interesting, any chance to get the slides ? (very difficult to read in the video)

Leave a Reply