<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="https://elezea.com/wp-content/themes/elz_2023/styles/pretty-feed-v3.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:slash="http://purl.org/rss/1.0/modules/slash/" >
  <channel>
    <title>Elezea by Rian van der Merwe - RSS Feed</title>
    <atom:link href="https://elezea.com/2015/01/code-or-be-left-behind/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2015/01/code-or-be-left-behind/</link>
    <description>A personal blog about product, technology, and interesting things that are worth sharing.</description>
    <lastBuildDate>Thu, 02 Apr 2026 17:43:52 +0000</lastBuildDate>
    <language></language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>https://wordpress.org/?v=6.9.4</generator>
          <item>
        <title>Left Behind: Designers Who Don&#8217;t Code Edition</title>
        <link>https://elezea.com/2015/01/code-or-be-left-behind/</link>
        <pubDate>Tue, 20 Jan 2015 23:24:54 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=5160</guid>
        <description>
          <![CDATA[Another year, another debate about whether or not designers should learn to code.]]>
        </description>
        <content:encoded>
          <![CDATA[<p>So I guess it&#8217;s quarterly &#8220;Designers should learn to code&#8221; day on Twitter. This appears to be the crux:</p>
<blockquote class="twitter-tweet" lang="en">
<p>Good discussion today w/ friends who are &quot;designers that code.&quot; It&#39;s no longer even a question of &quot;Should designers learn to code?&quot;</p>
<p>&mdash; Nathan Smith (@nathansmith) <a href="https://twitter.com/nathansmith/status/557603260459388931">January 20, 2015</a></p></blockquote>
<p><script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script></p>
<blockquote class="twitter-tweet" lang="en">
<p>Because that ship has sailed. It&#39;s more like… If you&#39;re a designer that doesn&#39;t code, you&#39;ll just be left behind. Not even a debate anymore.</p>
<p>&mdash; Nathan Smith (@nathansmith) <a href="https://twitter.com/nathansmith/status/557603388360499200">January 20, 2015</a></p></blockquote>
<p><script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script></p>
<p>I have two questions.</p>
<h2>1. What is a &#8220;designer&#8221;?</h2>
<p><img decoding="async" style="display: block; margin-left: auto; margin-right: auto;" title="" src="http://gif.elezea.com/who-am-i.gif" border="0" alt="" /></p>
<p>I don&#8217;t mean that in the metaphorical sense. I mean literally, how do you <em>define</em> design in this context? Is it visual design? User experience design? Product design? Content strategy, or any or all of the <a href="https://elezea.com/2012/04/definition-user-experience-design/">other things that make up well-rounded design</a>?</p>
<p>Because here are the things I&#8217;m currently trying to get better at by reading books and practicing and writing and working it into projects:</p>
<ul>
<li>Usability testing and ethnography</li>
<li>Information architecture across multi-platform experiences</li>
<li>iOS native app design</li>
</ul>
<p>I&#8217;m a little busy right now, so I&#8217;d like to know: which of these things should I drop to learn to code?</p>
<h2>2. What does &#8220;left behind&#8221; mean?</h2>
<p><img decoding="async" style="display: block; margin-left: auto; margin-right: auto;" title="" src="http://gif.elezea.com/left-behind.gif" border="0" alt="" /></p>
<p>Does it mean designers who don&#8217;t code won&#8217;t get hired in The Future? I don&#8217;t know about that. I spend a lot of time with designers. Some of them code, some don&#8217;t. Those who <em>don&#8217;t</em> specialize in something else that those who code aren&#8217;t good at, and that makes for stronger teams where work can be distributed more evenly and more effectively.</p>
<p>Let me put this another way: once every designer can code (since it&#8217;s &#8220;not even a debate any more&#8221;), who&#8217;s going to make sure we build the <em>right</em> things? Who&#8217;s going to discover user needs, create IAs that work for target personas, and design scalable holistic systems that work across devices and contexts?</p>
<p>What I mean to say is this:</p>
<ul>
<li>Heaven help us if we become a community of <em>executors</em> at the expense of all the <em>planners</em> out there. We need both.</li>
<li>It&#8217;s really, really dangerous to tell people they&#8217;ll be &#8220;left behind&#8221; if they don&#8217;t become part of a homogenous group of people all focused on the same thing. That has never worked out well for anyone, in the history of mankind.</li>
</ul>
<p>So go forth, follow the design thing you&#8217;re most interested in. If that&#8217;s coding, awesome. If it&#8217;s how to best understand user needs and translate that into design systems, go do that. As long as you do it well, you won&#8217;t be left behind.</p>
          <br>
          <br>
          <hr>
          Thanks for still believing in RSS! Get in touch <a href="https://elezea.com/contact">here</a> if you'd like.]]>
        </content:encoded>
                      </item>
      </channel>
</rss>