<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Adrian Pilarczyk</title>
  <subtitle>Notes on software, documentation, developer experience, and the craft around shipping useful things.</subtitle>
  <link href="https://peelar.dev/" />
  <link href="https://peelar.dev/atom.xml" rel="self" type="application/atom+xml" />
  <id>https://peelar.dev/</id>
  <updated>2026-08-03T00:00:00.000Z</updated>
  <author>
    <name>Adrian Pilarczyk</name>
  </author>
  <entry>
    <title>Your agents should run your coding tools too</title>
    <link href="https://peelar.dev/ai-terminal-devtools" />
    <id>https://peelar.dev/ai-terminal-devtools</id>
    <published>2026-08-03T00:00:00.000Z</published>
    <updated>2026-08-03T00:00:00.000Z</updated>
    <summary type="html">Why the best tools for agentic coding give humans and agents the same programmable workbench.</summary>
  </entry>
  <entry>
    <title>The Post-Tokenmaxxing Engineering Team</title>
    <link href="https://peelar.dev/post-tokenmaxxing-engineering-team" />
    <id>https://peelar.dev/post-tokenmaxxing-engineering-team</id>
    <published>2026-06-09T00:00:00.000Z</published>
    <updated>2026-06-09T00:00:00.000Z</updated>
    <summary type="html">A practical look at where agentic coding helps engineering teams, where it creates review and risk bottlenecks, and why harnesses matter more than token spend.</summary>
  </entry>
  <entry>
    <title>How to turn tribal knowledge into an AI agent</title>
    <link href="https://peelar.dev/how-turn-tribal-knowledge-ai-agent" />
    <id>https://peelar.dev/how-turn-tribal-knowledge-ai-agent</id>
    <published>2026-03-04T00:00:00.000Z</published>
    <updated>2026-03-04T00:00:00.000Z</updated>
    <summary type="html">How I turned organizational and tacit knowledge into a local AI assistant that helps Saleor prepare approach documents faster.</summary>
  </entry>
  <entry>
    <title>Staying out of the LLM dumb zone with the Memento Pattern</title>
    <link href="https://peelar.dev/staying-out-of-the-llm-dumb-zone" />
    <id>https://peelar.dev/staying-out-of-the-llm-dumb-zone</id>
    <published>2025-12-08T00:00:00.000Z</published>
    <updated>2025-12-08T00:00:00.000Z</updated>
    <summary type="html">Why the best AI agents work like Guy Pearce in Memento (and what that means for your next project)</summary>
  </entry>
  <entry>
    <title>What a Polish novel from 1899 taught me about living through a technological shift</title>
    <link href="https://peelar.dev/polish-novel-technological-shift" />
    <id>https://peelar.dev/polish-novel-technological-shift</id>
    <published>2025-11-22T00:00:00.000Z</published>
    <updated>2025-11-22T00:00:00.000Z</updated>
    <summary type="html">I can&apos;t believe I am going to connect Władysław S. Reymont to Artificial Intelligence, but here we are.</summary>
  </entry>
  <entry>
    <title>Why Developer Advocacy Had to Grow Up</title>
    <link href="https://peelar.dev/why-developer-advocacy-had-to-grow" />
    <id>https://peelar.dev/why-developer-advocacy-had-to-grow</id>
    <published>2025-11-15T00:00:00.000Z</published>
    <updated>2025-11-15T00:00:00.000Z</updated>
    <summary type="html">A post-hype look at developer advocacy, why helping developers matters more than clout, and why DevRel has to be accountable to real product outcomes.</summary>
  </entry>
  <entry>
    <title>What I Learned from Building a Dev Tool</title>
    <link href="https://peelar.dev/what-i-learned-from-building-dev-tool" />
    <id>https://peelar.dev/what-i-learned-from-building-dev-tool</id>
    <published>2025-09-16T00:00:00.000Z</published>
    <updated>2025-09-16T00:00:00.000Z</updated>
    <summary type="html">Reflections from building Configurator from scratch, balancing developer instincts with product ownership and user feedback.</summary>
  </entry>
  <entry>
    <title>Pathfinding</title>
    <link href="https://peelar.dev/pathfinding" />
    <id>https://peelar.dev/pathfinding</id>
    <published>2025-08-06T00:00:00.000Z</published>
    <updated>2025-08-06T00:00:00.000Z</updated>
    <summary type="html">On becoming technical without leaving behind writing, storytelling, and the parts of yourself that make the path yours.</summary>
  </entry>
  <entry>
    <title>Further reading on URL state management</title>
    <link href="https://peelar.dev/url-state-links" />
    <id>https://peelar.dev/url-state-links</id>
    <published>2024-02-02T00:00:00.000Z</published>
    <updated>2024-02-02T00:00:00.000Z</updated>
    <summary type="html">A list of resources that I found useful when learning about URL state management.</summary>
  </entry>
  <entry>
    <title>Running multiple ngrok tunnels for free</title>
    <link href="https://peelar.dev/free-ngrok-tunnels" />
    <id>https://peelar.dev/free-ngrok-tunnels</id>
    <published>2024-01-22T00:00:00.000Z</published>
    <updated>2024-01-22T00:00:00.000Z</updated>
    <summary type="html">ngrok is a fantastic tool that allows exposing your local development environment to the internet. I wish I knew how to run multiple tunnels for free when I started using it.</summary>
  </entry>
  <entry>
    <title>My takeaways from &quot;Docs for Developers&quot;</title>
    <link href="https://peelar.dev/docs-for-developers-takeaways" />
    <id>https://peelar.dev/docs-for-developers-takeaways</id>
    <published>2023-07-17T00:00:00.000Z</published>
    <updated>2023-07-17T00:00:00.000Z</updated>
    <summary type="html">I recently read &quot;Docs for Developers: An Engineer’s Field Guide to Technical Writing&quot;. Here is what I learned.</summary>
  </entry>
  <entry>
    <title>Avoid self-inflicted MDX lock-in</title>
    <link href="https://peelar.dev/avoid-mdx-lock-in" />
    <id>https://peelar.dev/avoid-mdx-lock-in</id>
    <published>2023-07-10T00:00:00.000Z</published>
    <updated>2023-07-10T00:00:00.000Z</updated>
    <summary type="html">A cautionary tale about the cost of maintaining a blog with MDX.</summary>
  </entry>
  <entry>
    <title>Tools and techniques to overcome documentation writer’s block</title>
    <link href="https://peelar.dev/overcome-documentation-writers-block" />
    <id>https://peelar.dev/overcome-documentation-writers-block</id>
    <published>2023-07-04T00:00:00.000Z</published>
    <updated>2023-07-04T00:00:00.000Z</updated>
    <summary type="html">Documentation is a tricky form that doesn’t come easy even to seasoned writers. Its principles are well known: keep it short, user-focused, and simple. There is nothing simple about writing simple, though.</summary>
  </entry>
  <entry>
    <title>First look at Remix</title>
    <link href="https://peelar.dev/first-look-at-remix" />
    <id>https://peelar.dev/first-look-at-remix</id>
    <published>2021-11-23T00:00:00.000Z</published>
    <updated>2021-11-23T00:00:00.000Z</updated>
    <summary type="html">Created by a great team under React Router veterans Ryan Florence and Michael Jackson, Remix was meant to electrify the front-end landscape. Did it succeed?</summary>
  </entry>
  <entry>
    <title>The magic of CSS filter</title>
    <link href="https://peelar.dev/css-filter-magic" />
    <id>https://peelar.dev/css-filter-magic</id>
    <published>2021-09-04T00:00:00.000Z</published>
    <updated>2021-09-04T00:00:00.000Z</updated>
    <summary type="html">Filter is one of the most powerful properties that CSS gave us. Thanks to it, we can do absolute wonders to images: from turning them b&amp;w, blurring them, to going full Photoshop-style on those hues and contrasts. Allow me to walk you through it.</summary>
  </entry>
  <entry>
    <title>&lt;T&gt;, foobar, and other sins of building excessive naming abstractions</title>
    <link href="https://peelar.dev/case-against-foobar" />
    <id>https://peelar.dev/case-against-foobar</id>
    <published>2021-09-02T00:00:00.000Z</published>
    <updated>2021-09-02T00:00:00.000Z</updated>
    <summary type="html">Programming is abstract enough in its own right, and yet sometimes we choose to make it even more convoluted. Let&apos;s take it down a notch by thinking about how we name entities.</summary>
  </entry>
</feed>
