Proof of Concept | David Hoang | Substack

At some point in a designer’s career, the age-old question is asked: "Should designers code?" My direct answer for people who design software interfaces is yes. This is a belief held my entire career. Despite my stance, I don't like the question. It might be the wrong question to focus on and variers on who is asking it. Designers feel like they are doing multiple jobs, so if someone outside our practice prowokes the question, it feels like we're being asked to do more without being rewarded for the work. At its core, design is taking an idea and making it tangible. Building your designs is a continuation and extension of that tangibility. Ignore the question of whether designers should code and look this way: Designers build. Building your designs doesn’t assume production code. Less than 5% of the code I've written in my career made it to production (that’s a good thing), but 100% of it was considered in the software development process. One of my favorite use cases to build my desig

saved by

• Kelly Chong