<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI on Al Banna</title><link>https://albanna.id/tags/ai/</link><description>Recent content in AI on Al Banna</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 28 May 2026 10:00:00 +0700</lastBuildDate><atom:link href="https://albanna.id/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Three meetings before lunch, or why I built my own minutes generator</title><link>https://albanna.id/posts/three-meetings-before-lunch/</link><pubDate>Thu, 28 May 2026 10:00:00 +0700</pubDate><guid>https://albanna.id/posts/three-meetings-before-lunch/</guid><description>&lt;p&gt;My calendar does not wake up at 07:00 whispering: &lt;em&gt;“One meeting today. Take it easy.”&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;What it usually means is &lt;strong&gt;three or four calls before lunch&lt;/strong&gt;, each with its own transcript, its own cast, and—if you draw the short straw on documentation—a deadline that does not care whether you have eaten anything yet.&lt;/p&gt;
&lt;p&gt;At that point, meeting minutes stop being “an important document.” They become a &lt;strong&gt;sprint&lt;/strong&gt;. You type while replaying who said what, while praying no application module or budget figure slipped through, while hoping the output still sounds like something a director would read—not a very long WhatsApp recap wearing a tie.&lt;/p&gt;</description></item></channel></rss>