<?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>Tooling on Conall O&#39;Brien</title>
    <link>https://writings.conall.dev/tags/tooling/</link>
    <description>Recent content in Tooling on Conall O&#39;Brien</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Jul 2026 09:00:00 +0100</lastBuildDate>
    <atom:link href="https://writings.conall.dev/tags/tooling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Coding Interview Pattern Drill</title>
      <link>https://writings.conall.dev/posts/coding-interview-pattern-drill/</link>
      <pubDate>Wed, 15 Jul 2026 09:00:00 +0100</pubDate>
      <guid>https://writings.conall.dev/posts/coding-interview-pattern-drill/</guid>
      <description>&lt;p&gt;LeetCode-style interview prep has a hidden assumption baked in: that for any unfamiliar problem, you can quickly spot which algorithmic pattern applies — even though most problems admit more than one valid approach.&lt;/p&gt;
&lt;p&gt;Grinding through exercises doesn&amp;rsquo;t really train that skill on its own. So I built a small tool to practice it directly: it pulls problems from LeetCode, then quizzes you multiple-choice style on which pattern fits before you ever write code.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
