<?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>Technology on Rabid Curiosity</title><link>https://blog.thomas-bray.com/tags/technology/</link><description>Recent content in Technology 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/technology/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>Sam Altman on Productivity, and How AI Creates Time</title><link>https://blog.thomas-bray.com/posts/sam-altman-productivity-and-ai-creates-time/</link><pubDate>Tue, 17 Mar 2026 09:50:00 -0500</pubDate><guid>https://blog.thomas-bray.com/posts/sam-altman-productivity-and-ai-creates-time/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Sam Altman has written and spoken about productivity in ways that are worth taking seriously—not because he&amp;rsquo;s a productivity guru, but because he&amp;rsquo;s someone who operates at very high leverage and thinks carefully about where his time goes. His framing around AI is particularly interesting: the claim isn&amp;rsquo;t just that AI makes you faster, it&amp;rsquo;s that it qualitatively changes the relationship between effort and output. This post reflects on those ideas and what they actually mean for how ordinary people should think about their time.&lt;/p&gt;</description></item><item><title>Reflections on Trusting Trust</title><link>https://blog.thomas-bray.com/posts/reflections-on-trusting-trust/</link><pubDate>Tue, 17 Mar 2026 09:30:00 -0500</pubDate><guid>https://blog.thomas-bray.com/posts/reflections-on-trusting-trust/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Ken Thompson&amp;rsquo;s 1984 Turing Award lecture, &amp;ldquo;Reflections on Trusting Trust,&amp;rdquo; makes a deceptively simple argument: you cannot fully trust code you did not write yourself, because the compiler that built it might have been compromised. The implications reach far beyond computer security. Trust in complex systems is always, at some level, an act of faith—and understanding that shapes how you should build, operate, and rely on things you can&amp;rsquo;t fully verify.&lt;/p&gt;</description></item></channel></rss>