Recap: Dynamic Duo
June 10, 2011 Samantha Metheny
For our June 1 event, Lori Patton and Zerek Welz discussed how to avoid strangling your fellow teammate and finish projects with more then just spirit fingers. If you were unable to attend or need a refresher, we've got you covered:
Web designers don't just make things pretty. They understand the concept and purpose of developers' jobs. And they focus on the details; the pixels.
A tip for designers: it's always a good idea to design appropriately for the project so the developers have a clear path for putting together what you're creating.
On the other side of the coin, developers have to deal with technicalities like cross-browser rendering, in order to work out all the quirks and bugs that come with making a design look wonderful across all browsers. For this skill, developers definitely have to keep up with what's current in their field.
To work together cohesively, the web designer and web developer have respect for each other. The designer knows that the developer is an expert, and the developer knows that the designer is an expert. Each person respects the other's expertise. And both keep up with trends and web standards.
To facilitate the relationship even further, make sure you ask questions about if something is appropriate. Both parties should understand and agree what the end result is, and if there are any questions or hesitations along the way, you should speak up. Communication is key!
And, as the project progresses, stay involved and in close communication with each other! From start to finish. That way, you can fix something right off the bat to avoid snowballing or other issues that may arise. (Add a swift kick in the ass when needed!)
How does the designer/developer relationship begin at the inception of a project? Well, it's a good idea to start by brainstorming and sharing ideas. Ask, "What can the designer design that can realistically be developed?"
Continue by discussing the functionality and goals of the design. Do this so that, if a problem arises, each person can consult the other about a solution.
Next in the process, for both the designer and the developer, is to be on the same page!! Take care to understand the needs of the client and make sure the goals are being met.
It's important to remember that the developer doesn't come in just at the end of the design. They are not a separate entity by any means. If both parties stay involved from the get-go, the timeline of the project won't be increased overall. And, the products of both the designer and the developer will then remain within the scope of the project.
Along the way, it becomes obvious that the designer and the developer speak different languages. But, the commonalities are: web standards, functionality, usability, happy clients, accessibility, and awesome-sauce (or your power-word of choice!)
Mid-Year Software Winner
In addition to the "Dynamic Duo" presentation, we also had our mid-year software drawing at our June event. Congratulations to our winner, Brooks Walch, who is now the proud owner of a copy of Adobe CS5.5 Web Premium!
Rate Our Speakers
If you attended the event and have not yet rated our speakers, please head over to SpeakerRate and let Lori Patton and Zerek Welz know you what thought.
Your input and feedback are essential for helping Webuquerque provide the best content possible. Be sure to tell us what you thought!
The slide deck is available on SlideShare:
Photos are available on Flickr:
Thanks to All Our Volunteers!
Webuquerque just wouldn't be the same without helping hands from our community members:
Want to help? Let us know if you'd like to lend a hand. Interested in speaking? Let us know that too!
Stay Tuned for Our Next Event!
- Twitter and Flickr services
Let Us Know What You Think
As always, we want to know what's on your mind so we can do the best to ensure Webuquerque is all you want it to be. Make sure to let us know if you have any suggestions, comments or complaints.