Getting to the build phase

<h1>A stale debate</h1> Whether or not designers should learn to code is an old debate that has taken on new life recently in online design circles. Wading into this thorny conversation is a great way to generate engagement on LinkedIn, but the frenzied back-and-forth rarely yields a satisfying answer, in part because we lose sight of why we’re asking the question in the first place. Instead of parties on both sides digging into defensive positions, we should be having an honest conversation about what problem we’re trying to solve. In my view, knowing how to code well as a designer is less important than being around the code. The camp that insists designers must code is overlooking the value of team collaboration, the efficiency gained from a division of labor, and the simple fact that people can’t learn every skill, so learning to code does in fact have an opportunity cost for a designer who might benefit from learning something else instead. The camp that insist designers don’t need to code comes across as defensive and out of touch with the reality of how software gets made. It’s quite clear that neither side has legitimate claim to the truth. There are companies that have designer/coder hybrid roles, and many more in which designers know zero code and programmers do all of the implementation. The idea that either is required for all companies doesn’t hold up when you examine the state of the industry. <a href="https://medium.com/@SkylerSchain/getting-to-the-build-phase-87784f1a87cb">Visit Now</a>