<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
  <title>Gaetano Del Prete — Blog</title>
  <link>https://gaedelprete.it/en/</link>
  <description>I write when I have something useful to say. No aggressive newsletters.</description>
  <language>en</language>
  <item>
    <title>When a company really needs a CTO</title>
    <link>https://gaedelprete.it/en/blog/when-you-need-a-cto/</link>
    <guid>https://gaedelprete.it/en/blog/when-you-need-a-cto/</guid>
    <pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate>
    <description>Three signs it’s time, and two cases where you don’t need one at all.</description>
  </item>
  <item>
    <title>AI in the dev cycle: what to measure in the first three months</title>
    <link>https://gaedelprete.it/en/blog/ai-in-the-dev-cycle/</link>
    <guid>https://gaedelprete.it/en/blog/ai-in-the-dev-cycle/</guid>
    <pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate>
    <description>Speed, quality and trust: how to tell whether coding assistants are actually helping.</description>
  </item>
  <item>
    <title>Rescuing a project in trouble: the first two weeks</title>
    <link>https://gaedelprete.it/en/blog/rescuing-a-project/</link>
    <guid>https://gaedelprete.it/en/blog/rescuing-a-project/</guid>
    <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
    <description>What I look at first, what I freeze and what I leave alone.</description>
  </item>
  <item>
    <title>Technical due diligence: the questions I always ask</title>
    <link>https://gaedelprete.it/en/blog/technical-due-diligence/</link>
    <guid>https://gaedelprete.it/en/blog/technical-due-diligence/</guid>
    <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
    <description>A practical list for anyone assessing a software product before investing.</description>
  </item>
  <item>
    <title>Data rules before adopting AI</title>
    <link>https://gaedelprete.it/en/blog/data-rules-before-ai/</link>
    <guid>https://gaedelprete.it/en/blog/data-rules-before-ai/</guid>
    <pubDate>Tue, 03 Mar 2026 00:00:00 GMT</pubDate>
    <description>Why policies get written before the first incident, and where to begin.</description>
  </item>
</channel>
</rss>
