<?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>Posts on MJ Moshiri</title><link>https://mjmoshiri.com/posts/</link><description>Recent content in Posts on MJ Moshiri</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://mjmoshiri.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Before You Build a Harness</title><link>https://mjmoshiri.com/posts/before-you-build-a-harness/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mjmoshiri.com/posts/before-you-build-a-harness/</guid><description>What the harness engineering guides assume, and how to get it.</description></item><item><title>Going back to AI Sweet Spot: Part 1 - Confession</title><link>https://mjmoshiri.com/posts/ai-sweet-spot-part-1-confession/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mjmoshiri.com/posts/ai-sweet-spot-part-1-confession/</guid><description>&lt;p&gt;I have always been an early adopter of new technologies. As Barney Stinson once said, “&lt;a href="https://www.youtube.com/watch?v=1SNRULEnTVQ" target="_blank" rel="noopener noreferrer"&gt;new is always better.&lt;/a&gt;”&lt;/p&gt;
&lt;p&gt;By the time ChatGPT came out, I was already using GitHub Copilot beta. Before that, I had used Tabnine. I had also been following OpenAI for years, first through their Dota 2 reinforcement learning project, where their agents beat some of the best players in the world. Later, I used their Davinci models in the OpenAI Playground to help with essays and document completion. So when ChatGPT arrived, I did not need much convincing. I jumped in immediately.&lt;/p&gt;</description></item><item><title>Going back to AI Sweet Spot: Part 2 - Not Good Enough</title><link>https://mjmoshiri.com/posts/ai-sweet-spot-part-2-not-good-enough/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mjmoshiri.com/posts/ai-sweet-spot-part-2-not-good-enough/</guid><description>&lt;p&gt;Before I write about how I am mitigating the issues I have with AI, I have to talk about the issues themselves.&lt;/p&gt;
&lt;p&gt;There are many great writings out there, that explains the shortcomings of AI agents, such as Addy Osmani’s &lt;a href="https://addyo.substack.com/p/the-70-problem-hard-truths-about" target="_blank" rel="noopener noreferrer"&gt;70% Problem&lt;/a&gt;, Armin Ronacher’s &lt;a href="https://lucumr.pocoo.org/2026/1/18/agent-psychosis/" target="_blank" rel="noopener noreferrer"&gt;Agent Psychosis&lt;/a&gt;, and these tweets by Mitchell Hashimoto: &lt;a href="https://x.com/mitchellh/status/2055380239711457578" target="_blank" rel="noopener noreferrer"&gt;Companies with AI Psychosis&lt;/a&gt; and &lt;a href="https://x.com/mitchellh/status/2060088112257372610" target="_blank" rel="noopener noreferrer"&gt;Fake Optimization&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;So, in the interest of not repeating, and with a confession that I don&amp;rsquo;t have concrete &lt;code&gt;shareable&lt;/code&gt; examples for every single item I have seen, but trusting PG’s point in &lt;a href="https://paulgraham.com/know.html" target="_blank" rel="noopener noreferrer"&gt;How to Know&lt;/a&gt;, I am going to share what I felt here.&lt;/p&gt;</description></item><item><title>Workspace Hygiene: The Real Multiplier</title><link>https://mjmoshiri.com/posts/workspace-hygiene-the-real-multiplier/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mjmoshiri.com/posts/workspace-hygiene-the-real-multiplier/</guid><description>&lt;p&gt;In my opinion, workspace hygiene is the single biggest factor that determines what number actually sits in front of the “x” when people talk about Nx engineering with AI agents. Prompting skill and model choice matter, but they are secondary. A clean, well-structured workspace with strong guardrails, clear contracts, reproducible environments, and reliable memory dramatically reduces how often you have to step in and correct the agent. Every hour you don’t spend fixing hallucinations, architectural regressions, repeated mistakes, or environment issues is an hour the agent stays in flow — and that compounds directly into real productivity multipliers.&lt;/p&gt;</description></item></channel></rss>