<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bennett Clement</title>
    <link>https://www.benclmnt.com/</link>
    <description>Recent content on Bennett Clement</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <managingEditor>ben@benclmnt.com (Bennett)</managingEditor>
    <webMaster>ben@benclmnt.com (Bennett)</webMaster>
    <lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.benclmnt.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automated Testing of Electron Apps</title>
      <link>https://www.benclmnt.com/testing-electron-apps/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate><author>ben@benclmnt.com (Bennett)</author>
      <guid>https://www.benclmnt.com/testing-electron-apps/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been building my personal photoculler this past week without reading and writing any of the code. Left unattended, coding agents produce slop. I wanted to see if I could prevent them from collapsing under their own slop.&lt;/p&gt;&#xA;&lt;p&gt;A few weeks ago, I saw a demo of Software Dark Factory &lt;a href=&#34;https://factory.strongdm.ai/techniques&#34;&gt;techniques&lt;/a&gt; from ex-StrongDM folks. The premise is simple: coding agents need rich feedback if they&amp;rsquo;re going to operate autonomously.&lt;/p&gt;&#xA;&lt;p&gt;Electron wraps around Chromium, so it can be tested using Chrome CDP. To get started, I reused an agent skill I built to &lt;a href=&#34;https://www.benclmnt.com/baby-steps-with-agents/&#34;&gt;test websites&lt;/a&gt; and asked my coding agent to use &lt;a href=&#34;https://github.com/benclmnt/pi-stuff/tree/e162794/skills/electron-testing&#34;&gt;this skill&lt;/a&gt; to test photoculler. The agent can now start the electron app and click through basic user flows. Most of the time, it can verify its own feature, although it sometimes struggles. At the end of a testing session, I ask the agent to reflect on what it struggled with and what could have made its testing session smoother. I use most of its suggestions and ask it to improve the testing skill.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Baby Steps with Agents</title>
      <link>https://www.benclmnt.com/baby-steps-with-agents/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><author>ben@benclmnt.com (Bennett)</author>
      <guid>https://www.benclmnt.com/baby-steps-with-agents/</guid>
      <description>&lt;p&gt;I recently built a podcast serving and generation system for &lt;a href=&#34;https://commoncog.com/c/&#34;&gt;Commoncog Case Library&lt;/a&gt; while experimenting with coding agent workflows. Here is a report of how I built a moderately large system on top of our existing system using agents! Note that this was done in April - May 2026, and was representative of my approach then. I suppose it’s a testament to how quickly models and harnesses improve that my current development process &lt;em&gt;today&lt;/em&gt; is wildly different compared to what it was when I built this system.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
