<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Learning on Rabid Curiosity</title><link>https://blog.thomas-bray.com/tags/learning/</link><description>Recent content in Learning on Rabid Curiosity</description><generator>Hugo</generator><language>en-us</language><copyright>Thomas Bray</copyright><lastBuildDate>Tue, 17 Mar 2026 10:05:00 -0500</lastBuildDate><atom:link href="https://blog.thomas-bray.com/tags/learning/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Fundamental Technical Knowledge</title><link>https://blog.thomas-bray.com/posts/building-fundamental-technical-knowledge/</link><pubDate>Tue, 17 Mar 2026 10:05:00 -0500</pubDate><guid>https://blog.thomas-bray.com/posts/building-fundamental-technical-knowledge/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;There&amp;rsquo;s a pattern in technical work where people become highly skilled at the surface layer of a technology—the tools, the interfaces, the workflows—without developing any understanding of what&amp;rsquo;s underneath. This works fine until it doesn&amp;rsquo;t. When something breaks in an unexpected way, or when the tool changes, or when you need to make a non-obvious decision, the lack of fundamentals shows. This post is about why fundamentals matter and how to actually build them.&lt;/p&gt;</description></item><item><title>Reflecting on My Past as a Student</title><link>https://blog.thomas-bray.com/posts/reflecting-on-my-past-as-a-student/</link><pubDate>Tue, 17 Mar 2026 09:35:00 -0500</pubDate><guid>https://blog.thomas-bray.com/posts/reflecting-on-my-past-as-a-student/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Looking back at yourself as a student is a strange exercise. You&amp;rsquo;re trying to understand someone who had less information, fewer skills, and a different set of pressures than you do now—but who was also making decisions that shaped everything that followed. This post is a reflection on what I got right, what I got wrong, and what I wish I had understood earlier about how to actually learn.&lt;/p&gt;</description></item><item><title>On Reading Widely, Deeply, Exploring, Exploiting</title><link>https://blog.thomas-bray.com/posts/on-reading-widely-and-deeply/</link><pubDate>Tue, 17 Mar 2026 09:20:00 -0500</pubDate><guid>https://blog.thomas-bray.com/posts/on-reading-widely-and-deeply/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;The explore/exploit tradeoff is a concept from computer science and decision theory: when do you keep searching for something better versus committing to what you&amp;rsquo;ve found? It maps surprisingly well onto how we read. Wide reading is exploration—building a broad map of ideas. Deep reading is exploitation—extracting full value from a rich vein. Both matter, and the tension between them shapes what kind of thinker you become.&lt;/p&gt;
&lt;h2 id="key-points"&gt;Key Points&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The explore/exploit framework and how it applies to reading and learning&lt;/li&gt;
&lt;li&gt;What wide reading provides that deep reading can&amp;rsquo;t, and vice versa&lt;/li&gt;
&lt;li&gt;How to recognize when you&amp;rsquo;re stuck in a rut versus appropriately going deep&lt;/li&gt;
&lt;li&gt;The role of serendipity in intellectual development&lt;/li&gt;
&lt;li&gt;Building a personal reading practice that balances both modes&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;The best readers do both. Exploration keeps you from becoming a narrow specialist who misses the bigger picture. Exploitation keeps you from becoming a dilettante who knows a little about everything and a lot about nothing. The skill is knowing when to switch.&lt;/p&gt;</description></item></channel></rss>