aetles + development + developer   1

On Being a Designer and a Developer: Not Quite Unicorn Rare by Diogenes Brito
As Austin Bales says in a great talk, good designers and good developers actually have a lot in common. The crossover really even shows itself in our language when we use (appropriate) terms like "social engineering" for techniques designers use to illicit certain behaviors, or "software design" for the planning and creation of programming code. Both designers and developers put a premium on simplicity and clarity. Both are trying to make their creations as easy to intuit and work with as possible. Developers refactor their code as requirements change and complexity increases the same way designers redesign interfaces to make room for new or changing functionality. They have similar traits, skills, and motivations, they just work in different mediums and have different specialties. Designers tend to specialize and focus on the beginning of the creation process, whereas engineers specialize on the end or latter half of the process. I say a more accurate representation of a single person's skills might look something like this:

Each person has a certain level of skill in the designer and/or developer subject areas, where many of the skills and habits that would make you excel in either area would help in both. People may have a tendency to lean towards one area over the other, but no one has a "type" that would prevent them from learning and improving as a designer or a developer. What matters is the time and effort put into learning. World class designers and developers have put in lots and lots of dedicated practice: their (proverbial) 10,000 hours.
design  developer  development  designers  developers 
may 2013 by Aetles

Copy this bookmark:



description:


tags: