<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Prompt and Pray</title>
    <link>https://prompt-and-pray.ai/</link>
    <description>Recent content on Prompt and Pray</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://prompt-and-pray.ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agentic CEO</title>
      <link>https://prompt-and-pray.ai/posts/ceo/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://prompt-and-pray.ai/posts/ceo/</guid>
      <description>&lt;p&gt;Sitting at my kitchen table, on an uncomfortable chair, in the middle of the day, my laptop in front of me, for no good reason whatsoever, I have decided turn AI into my manager CEO.&lt;/p&gt;&#xA;&lt;p&gt;You may be wondering about the motivation. It is quite simple. I have a ton of unfinished projects. It’s that simple. Over the years, I have started a lot of software projects. Some of them are half finished, some are done. Some were personal utilities, some could have been full successful startups. What they all share in common is that none were shared with the broader audience. The reason was simple as well. I was always constrained for time. All of these projects were side-projects. They were developed over prolonged time-horizons, after work hours and on weekends. The agentic experience changes the calculus of time for me. It makes a lot of things possible again without having a dedicated team, fund raising or hiring people to help out.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About</title>
      <link>https://prompt-and-pray.ai/about/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://prompt-and-pray.ai/about/</guid>
      <description>&lt;p&gt;This blog is a field journal, not a polished publication. Expect rough edges, failure reports, whacky ideas and the occasional thing that actually worked.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;What I write about:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Eval experiments — testing model claims against real tasks&lt;/li&gt;&#xA;&lt;li&gt;Tooling and workflows — building with LLMs, not just talking to them&lt;/li&gt;&#xA;&lt;li&gt;Lab notes — shorter observations that don&amp;rsquo;t warrant a full post&lt;/li&gt;&#xA;&lt;li&gt;Math - occasionally, I dabble in mathematics and write some stuff here&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;If something here is useful to you, I&amp;rsquo;d love to hear about it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Model self-checking</title>
      <link>https://prompt-and-pray.ai/posts/self-check/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://prompt-and-pray.ai/posts/self-check/</guid>
      <description>&lt;p&gt;Giving coding agents an ability to self-check their own work is one of the most useful techniques I came across. I develop a lot of numerical software in my free time and most models are very helpful here but no model has earned my complete trust. They simply don’t consult with me presence of uncertainty and rely too much on the parametric knowledge instead of consulting external sources. The usual runaround happens when the model states that it knows the answer to some problem, codes the algorithm, and the algorithm looks plausibly correct but doesn’t really work. A lot of debugging follows and the result is a lot of wasted time and frustration.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
