As an experiment, I will concede the language and narrow things to that notion of output.
Aaron Weyenberg

Does this sound about right? Because it’s what I believe:

  • More knowledge is never a bad thing
  • Understanding how code works is a benefit, even if you can’t code
  • Understanding code doesn’t diminish one’s creative abilities
  • But trying to be both designer and production coder on a project can introduce risks that a clear division of labor—designer + developer—would avoid
  • And the primary risk it introduces is that you might not be able to deliver what you’ve designed, or you may not design what you think is best because of your limitations
  • But that risk doesn’t mean one shouldn’t learn to code, only that one doesn’t need to code to be a good designer