<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:content="http://purl.org/rss/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ahmed Arshe — Blog</title>
    <link>https://ahmedarshe.com/blog</link>
    <description>Progress updates on AI projects, cybersecurity experiments, and side builds.</description>
    <language>en-gb</language>
    <lastBuildDate>Wed, 27 May 2026 20:52:32 GMT</lastBuildDate>
    <atom:link href="https://ahmedarshe.com/blog/rss.xml" rel="self" type="application/rss+xml"/>
    
  <item>
    <title>Progress - What going on and what am I doing</title>
    <link>https://ahmedarshe.com/blog/progress-what-going-on-and-what-am-i-doing</link>
    <guid isPermaLink="true">https://ahmedarshe.com/blog/progress-what-going-on-and-what-am-i-doing</guid>
    <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
    <description>Testing my projects and working on new ideas. </description>
    <content:encoded><![CDATA[<p>Hi all, it’s me again!</p>
<p>It’s been a while since my last post.</p>
<p>Wanted to update you on how things are going!</p>
<h2 id="project-a" tabindex="-1"><strong>Project A</strong></h2>
<p>I’ve made some great headway with my ‘Local grammar/ spelling’ tool. It’s working as you would expect an MVP would work. Works amazingly in some areas, but crap in others.</p>
<p>I’m planning to beta test this with a small group of friends, but I need a bit of time to set this up, and I’m looking to manage/distribute this via Chrome Web Store.</p>
<p>Project A will be able to solve the following issues:</p>
<ul>
<li><strong>Spelling mistakes</strong>
Catches typos and misspellings as you write — whether it’s a fat-finger or a word you’ve always spelt slightly wrong.</li>
<li><strong>Grammar errors</strong>
Flags sentences that are grammatically incorrect — things like subject-verb disagreement (“the team <em>were</em> ready” vs. “the team <em>was</em> ready”) or incorrect verb tenses.</li>
<li><strong>Punctuation issues</strong>
Spots missing commas, incorrect apostrophes, and other punctuation slips that change how your writing reads.</li>
<li><strong>Style &amp; clarity improvements</strong>
Goes beyond correctness — suggests cleaner, more natural phrasing so your writing doesn’t just pass the grammar test, it actually sounds good.</li>
<li><strong>Sentence-level rewrites</strong>
For sentences that need more than a small fix, Project A can suggest a fully rewritten version that says the same thing, better.</li>
</ul>
<p>More features are being developed, and more will be written and deployed soon, so keep your eyes out for the next blog.</p>
<h2 id="project-b" tabindex="-1">Project B</h2>
<p>This was the new idea that I mentioned in the title.</p>
<p>I’m currently working on a Hermes agent bot that can use Postiz to help me post images I might have screenshotted from other posts on TikTok, Instagram, etc., so I can repost them onto my meme page.  I’m going to see if I can build traction with the Hermes agent and explore how it can support this side project of mine.  It’s Day One, so I don’t really have much to showcase, but I will come back next week and showcase more in terms of development and what I’m using.</p>
]]></content:encoded>
    <category>AI</category>
    <category>World building</category>
    <category>Creation</category>
  </item>
  <item>
    <title>Hello from the Blog — Building in Public with AI</title>
    <link>https://ahmedarshe.com/blog/hello-world</link>
    <guid isPermaLink="true">https://ahmedarshe.com/blog/hello-world</guid>
    <pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate>
    <description>Introducing my new blog where I&apos;ll share real progress updates on every AI project I&apos;m working on — what&apos;s working, what broke, and what I learned.</description>
    <content:encoded><![CDATA[<p>Welcome to the blog.</p>
<p>I’ve been building a lot of things lately — most of them with AI tools in the loop — and I’ve wanted a place to write up the messy, honest progress on each of them rather than just polishing things up for LinkedIn.</p>
<p>This is that place.</p>
<h2 id="what-ill-be-writing-about" tabindex="-1">What I’ll be writing about</h2>
<p>A mix of things, depending on the week:</p>
<ul>
<li><strong>AI project logs</strong> — step-by-step progress on whatever I’m prototyping, including the parts that break spectacularly</li>
<li><strong>Tool reviews in practice</strong> — how I actually use Claude, Cursor, and others in real workflows, not synthetic benchmarks</li>
<li><strong>Security x AI</strong> — observations from my day job as an Information Security Lead intersecting with the AI tooling wave</li>
<li><strong>Side builds</strong> — small experiments that may or may not turn into anything useful</li>
</ul>
<h2 id="why-write-at-all" tabindex="-1">Why write at all?</h2>
<p>Mostly accountability. I find I think more clearly when I write things down, and sharing it publicly adds just enough friction to actually finish a thought before publishing it.</p>
<p>Also, I’ve learned a huge amount from other people’s “build in public” posts and I’d like to contribute back to that pool.</p>
<h2 id="format" tabindex="-1">Format</h2>
<p>Posts will be short and frequent rather than long and occasional. I’ll aim for a few hundred words, a clear takeaway, and honesty about what I don’t know yet.</p>
<hr>
<p>If you’ve found this, thanks for reading. More to come shortly.</p>
]]></content:encoded>
    <category>AI</category>
    <category>Building in Public</category>
    <category>Meta</category>
  </item>
  </channel>
</rss>