-You’ll better understand the medium you’re working in. If you know what database queries will be faster than others, you can make the right response time tradeoffs. If you know what’s easy to code and what’s difficult to code, you can get your ideas implemented faster (and more of them, since development time is a limited resource.) Understanding what your medium does well and where isn’t as effective makes for more informed design decisions.
-Knowing how to code helps you produce better prototypes. The best way to communicate a design idea to your teammates and clients is through an interactive prototype. Producing your own quick prototypes brings your ideas to life sooner, releasing that inner brilliance you’re carrying around and helping everyone see what your designs are really about.
-Knowing how to code helps you identify bugs and flaws in the production code. As your team’s designs start to come to life, you can play an essential role of helping the developers isolate interaction problems, which means your end product will be the best it can be. (Source)
If you’re a designer, imagine you had a chance to work with two development teams.
Team 1: One team has top-notch developers who know virtually nothing about design. They can code miracles, but the designs of their applications are horrible and frustrating to use. And they show no desire to learn anything about design — how it’s done, why it’s important, and what makes a good design versus a bad design.
Team 2: The second team also has world-class developers, but these guys are hungry to learn about design. They’ve already taught themselves a fair amount and are truly interested in learning more. In addition to producing amazing code, they are regularly producing applications that look good, work well, and delight users.
As a designer, which team do you think would more fun to work with? The team that has no interest in designing or the one that really enjoys it?
Practically every designer I’ve talked to about this choice has told me, without hesitation, they would love to work with a development team that appreciates good design and wants to learn more about it. Those designers won’t be constantly battling for the simplest of design choices, instead be focusing on the hard problems with a group that wants to see the best outcomes.
Guess what? Developers feel the same way. If they had a choice, they’d rather work with a design team that understands development and craves to learn more, than with a team that doesn’t make any effort to learn what development is all about. Not just simple front-end coding either. They want to work with designers who understand the architecture and infrastructure, who can relate to the challenges they are up against and can appreciate it when the team has pulled off something amazing.
Learning to code doesn’t just give you new skills, it makes you a more desirable team member.
How do I get a huge hunk of metal in the air to fly across the ocean? I must design a way. How do I get someone to signup for my service they don’t know anything about? I must design a way. Both of the questions could be answered with ugly solutions. They could find old and archaic ways to solve the problems, but that isn’t what design is about. The elegant solution takes into account all aspects of the design. Taking the practical solution, the function, and adding the aesthetically appealing aspect to it, the form, and there you have a solution to the problem of ‘how do I?’
One of the early graphical web browser that got really popular was Mosaic, developed at National Center for Supercomputing Applications (NCSA). Some folks from the team, along with SGI founder Jim Clark, decided that it’s worth a venture and formed a company, originally called Mosaic Communication and then later renamed to Netscape Communication.
Netscape’s flagship desktop product was a much more advanced web browser than Mosaic. Jamie Zawinski coined the name "Mozilla", as it was supposed to be Mosaic Killer (Mozilla = Mosaic + Godzilla). At the later stage, the final browser was widely known as Netscape Navigator. For browsing the web, obviously you need a navigator.
"But cases protect my phone! What if I drop it?!". Especially with an iPhone, where cases don’t even cover the screen, if you drop your phone, it’s breaking. The second that thing hits concrete, the screen is cracking no matter what you have on it’s back. And if you drop it some place and it doesn’t break in some way, then it wouldn’t have broken if there was no case on it either.
Solar panel concrete was a thing of the past, now scientists are driving on glass…