<?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>Build-in-Public on Raja Sleem</title><link>https://www.rajasleem.com/tags/build-in-public/</link><description>Recent content in Build-in-Public on Raja Sleem</description><image><title>Raja Sleem</title><url>https://www.rajasleem.com/images/rajasleem-og-thumbnail-1200x630.png</url><link>https://www.rajasleem.com/images/rajasleem-og-thumbnail-1200x630.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 26 Aug 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://www.rajasleem.com/tags/build-in-public/index.xml" rel="self" type="application/rss+xml"/><item><title>Vibe Coding Is Not a Yes or No Question</title><link>https://www.rajasleem.com/posts/vibe-coding-is-not-a-yes-or-no-question/</link><pubDate>Wed, 26 Aug 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/vibe-coding-is-not-a-yes-or-no-question/</guid><description>I had a hunch the vibe coding debate was all blanket verdicts. So I counted 51 takes before publishing mine. I was half wrong, and the half I was wrong about made the real pattern more interesting.</description></item><item><title>Trust, but Grep: The Plan Was Perfect and the Premise Was False</title><link>https://www.rajasleem.com/posts/agentic-workflow-part-8-trust-but-grep/</link><pubDate>Wed, 19 Aug 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/agentic-workflow-part-8-trust-but-grep/</guid><description>Almost half the questions my AI pipeline stopped to ask me were already answered on the hard drive. The plan reasoned flawlessly, from a premise nobody spent five seconds checking.</description></item><item><title>The Paperwork Outweighed the Product: What Testing My Own Pipeline Cost</title><link>https://www.rajasleem.com/posts/agentic-workflow-part-7-the-paperwork-problem/</link><pubDate>Wed, 12 Aug 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/agentic-workflow-part-7-the-paperwork-problem/</guid><description>I finally pointed my autonomous pipeline at two real repos. One paid 4.7x more per line of code than the other, and the culprit was not the model. It was my own specs.</description></item><item><title>Obedience Is Futile: The Guardrail You Build Against Your Own Limited Context Window</title><link>https://www.rajasleem.com/posts/agentic-workflow-part-6-obedience-is-futile/</link><pubDate>Tue, 04 Aug 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/agentic-workflow-part-6-obedience-is-futile/</guid><description>The bottleneck in an agentic workflow is still you. Not your attention this time, your context window. Here is the guardrail I built so my own limits stop quietly steering what I build.</description></item><item><title>Two Ways to Run a Loop: Portable Agents vs Dynamic Workflows</title><link>https://www.rajasleem.com/posts/agentic-workflow-part-5-two-ways-to-run-a-loop/</link><pubDate>Wed, 22 Jul 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/agentic-workflow-part-5-two-ways-to-run-a-loop/</guid><description>I have an autonomous build loop. Now there are two ways to run it: a portable setup of agents and skills, or a dynamic workflow that spins up many agents at once. I&amp;#39;m testing both.</description></item><item><title>Letting It Run: Toward an Autonomous Build Loop</title><link>https://www.rajasleem.com/posts/agentic-workflow-part-4-letting-it-run/</link><pubDate>Wed, 15 Jul 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/agentic-workflow-part-4-letting-it-run/</guid><description>Once agents could build to a shared contract and be checked against it, I stopped driving every step by hand. This is the loop that runs a batch of features mostly on its own.</description></item><item><title>When Agents Diverge: The Code Contract</title><link>https://www.rajasleem.com/posts/agentic-workflow-part-3-when-agents-diverge/</link><pubDate>Mon, 06 Jul 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/agentic-workflow-part-3-when-agents-diverge/</guid><description>Run several agents on the same project and they each build something reasonable that doesn&amp;#39;t match the others. Here&amp;#39;s the fix: write the rules down once, before anyone builds.</description></item><item><title>Surviving the Context Window</title><link>https://www.rajasleem.com/posts/agentic-workflow-part-2-surviving-the-context-window/</link><pubDate>Sun, 07 Jun 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/agentic-workflow-part-2-surviving-the-context-window/</guid><description>One Claude session is never enough for real work. This is how I hand off between sessions, push work onto sub-agents to save context, and finally see all the planning files at a glance.</description></item><item><title>From Prompts to a Process: Making Claude Code Repeatable</title><link>https://www.rajasleem.com/posts/agentic-workflow-part-1-from-prompts-to-a-process/</link><pubDate>Mon, 01 Jun 2026 09:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/agentic-workflow-part-1-from-prompts-to-a-process/</guid><description>The first thing I fixed about working with an LLM wasn&amp;#39;t the model. It was me starting from scratch every session. Here&amp;#39;s the simple process that changed that.</description></item><item><title>AI Fatigue Is Real</title><link>https://www.rajasleem.com/posts/ai-fatigue/</link><pubDate>Sun, 31 May 2026 12:00:00 -0400</pubDate><guid>https://www.rajasleem.com/posts/ai-fatigue/</guid><description>The tools got faster. My brain didn&amp;#39;t. Why four hours of building with an LLM wipes me out, and why I doubt the &amp;#39;spin up 200 agents&amp;#39; future.</description></item></channel></rss>