<?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/2026/03/why-its-still-valuable-to-learn-to-code/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2026/03/why-its-still-valuable-to-learn-to-code/</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>Why It&#8217;s Still Valuable To Learn To Code</title>
        <link>https://elezea.com/2026/03/why-its-still-valuable-to-learn-to-code/</link>
        <pubDate>Fri, 06 Mar 2026 22:47:32 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/2026/03/while-its-still-valuable-to-learn-to-code/</guid>
        <description>
          <![CDATA[Carson Gross's essay on AI and junior programmers applies just as much to product managers: you can't build an effective AI-powered workflow until you've spent years developing the underlying judgment it's meant to amplify.]]>
        </description>
        <content:encoded>
          <![CDATA[<p>Carson Gross <a href="https://htmx.org/essays/yes-and/">has a good essay on whether junior programmers should still learn to code</a> given how capable AI has become. His core warning to students:</p>
<blockquote>
<p>Yes, AI can generate the code for this assignment. Don&#8217;t let it. You <em>have</em> to write the code. I explain that, if they don&#8217;t write the code, they will not be able to effectively <em>read</em> the code. The ability to read code is certainly going to be valuable, maybe <em>more</em> valuable, in an AI-based coding future. If you can&#8217;t read the code you are going to fall into <a href="https://www.youtube.com/watch?v=m-W8vUXRfxU">The Sorcerer&#8217;s Apprentice Trap</a>, creating systems <a href="https://www.youtube.com/watch?v=GFiWEjCedzY">you don&#8217;t understand and can&#8217;t control</a>.</p>
</blockquote>
<p>And on what separates senior engineers who can use AI well from those who can&#8217;t:</p>
<blockquote>
<p>Senior programmers who already have a lot of experience from the pre-AI era are in a good spot to use LLMs effectively: they know what &#8216;good&#8217; code looks like, they have experience with building larger systems and know what matters and what doesn&#8217;t. The danger with senior programmers is that they stop programming entirely and start suffering from brain rot.</p>
</blockquote>
<p>This maps directly onto what I&#8217;ve been writing about with <a href="https://elezea.com/2025/12/ai-for-product-management/">AI for product work</a> and the <a href="https://elezea.com/2025/12/how-my-ai-product-second-brain-evolved/">second brain setup I&#8217;ve built</a>. The system works because I spent years writing and reading PRDs, strategy docs, and OKRs—enough to develop actual opinions about what good looks like. You have to do the work first, <em>then</em> the second brain is worth building.</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>