<?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>Ai on Czech the Data</title>
    <link>https://czechthedata.com/tags/ai/</link>
    <description>Recent content in Ai on Czech the Data</description>
    <image>
      <title>Czech the Data</title>
      <url>https://czechthedata.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://czechthedata.com/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.151.2</generator>
    <language>en</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://czechthedata.com/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title></title>
      <link>https://czechthedata.com/notes/slack_mcp/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://czechthedata.com/notes/slack_mcp/</guid>
      <description>&lt;p&gt;One of my favourite new tricks is to be a little more verbose in Slack and then use Claude and &lt;a href=&#34;https://slack.com/intl/en-gb/help/articles/48855576908307-Guide-to-the-Slack-MCP-server&#34;&gt;Slack MCP&lt;/a&gt; to generate a pull request from the discussion. That way, ideas from our Slack discussions make their way into the product almost immediately!&lt;/p&gt;
&lt;p&gt;It’s a small example of how software engineering is becoming less about producing code and more about collaboratively shaping the product.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
