<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Robert DeLanghe — Writing</title>
  <subtitle>Senior software engineer building the controls for shipping AI-written code — capability-scoped agents, signed delivery, and contracts enforced as build failures.</subtitle>
  <link href="https://robertdelanghe.dev/feed.xml" rel="self"/>
  <link href="https://pubsubhubbub.appspot.com/" rel="hub"/>
  <link href="https://robertdelanghe.dev/blog"/>
  <id>https://robertdelanghe.dev/blog</id>
  <updated>2026-07-04T00:00:00.000Z</updated>
  <author><name>Robert DeLanghe</name></author>
  <entry>
    <title>How I build my résumé — and how mapping it to Google Docs got my account disabled</title>
    <link href="https://robertdelanghe.dev/blog/resume-pipeline-google-docs-incident"/>
    <id>https://robertdelanghe.dev/blog/resume-pipeline-google-docs-incident</id>
    <updated>2026-07-04T00:00:00.000Z</updated>
    <summary>A JSON Resume source of truth renders to a site, a PDF, and a native Google Doc for review. The Google Docs leg's publish cycle looked enough like a bot to get the account behind it disabled.</summary>
  </entry>
  <entry>
    <title>How to keep agent-authored code from drifting</title>
    <link href="https://robertdelanghe.dev/blog/agent-authored-code-drift"/>
    <id>https://robertdelanghe.dev/blog/agent-authored-code-drift</id>
    <updated>2026-06-22T00:00:00.000Z</updated>
    <summary>When agents write modules in parallel, the modules stop agreeing with each other. That is a contract-enforcement problem, and you can make CI catch it.</summary>
  </entry>
</feed>
