I’ve been reading a lot about design lately; specifically information architecture, interface design and industrial design. It seems that design comes in at a specific point in a given production process. In software, a developer is able to create a program, script or application that solves some specific problem; namely that of accomplishing some set of tasks or achieving some result.
Design in software also creates a solution to a problem: how a program, script or application will interact with other entities. Specifically, UI design defines the interaction between software and humans. It seems clear then that in order for design to occur, there must first be some software to design. Usually there is some plan or concept in addition to functional requirements that a designer can use to produce a useful result. The point being that design necessarily follows software development, whether as concept or working code.
It is also true that many developers get started by tinkering with simple scripts at an early age in order to solve some problem or accomplish some simple goal. A developer is usually then compelled to learn more about software in general and will sometimes master several programming languages to write different and better programs. Does it then make sense that the advanced software developer should learn design, the next step in the application production process?
The first desire is to create something with a computer that can help solve a problem for a developer, so it might make sense that the second desire be to create something that will help others interface with a program that solves a problem. I like the idea of progressing through a line of different skills in one larger process, learning different trades that relate and give new perspectives. Learning only one trade and relying on it for a lifetime seems boring and possibly even unwise.
There are too many opportunities and potential experiences in the world to choose one skill, one career or one path. It seems wise to experience and learn as much as possible, which for the software developer might mean learning to design.
There aren’t words to describe how strongly I feel about the importance of good design. Anyone tasked with the job of communicating/interfacing with other human beings should strive to communicate/interface effectively.
In my mind, the importance of a programmer learning how to design (or at least how to appreciate design enough to work with designers), is as important as an author learning how to write (or how to work with an editor). Especially for a programmer seeking to create software that should require zero training to a wide variety of users.
In fact, to extend the analogy, why don’t I just cave in and quote the dudes at 37 Signals (fanboy alert!). In the “Wordsmiths” chapter of Getting Real they quote Michael A. Covington, Professor of Computer Science at The University of Georgia who says:
“Good writing is partly a matter of character. Instead of doing what’s easy for you, do what’s easy for your reader.”
The same goes for design. Taking the time and making the effort to make things easier for those around you doesn’t just make a nicer product, it makes the world a better place. I’M NOT KIDDING!
Oh, and design is possibly more important than writing because it stands to transcend language.