<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development on CTOMultiplier</title><link>https://ctomultiplier.com/tags/development/</link><description>Recent content in Development on CTOMultiplier</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 23 Mar 2026 21:05:53 +0100</lastBuildDate><atom:link href="https://ctomultiplier.com/tags/development/feed.xml" rel="self" type="application/rss+xml"/><item><title>How to Adopt AI in a Software Team</title><link>https://ctomultiplier.com/how-to-adopt-ai-in-a-software-team/</link><pubDate>Sun, 16 Nov 2025 13:15:38 +0000</pubDate><guid>https://ctomultiplier.com/how-to-adopt-ai-in-a-software-team/</guid><description>&lt;p&gt;Does your AI adoption strategy consist of giving out Copilot, Cursor, or Claude licenses and letting them figure out how to use them?&lt;/p&gt;
&lt;p&gt;Over the past year, I&amp;rsquo;ve found this to be a widespread strategy in software companies, whose teams face high workloads and, due to lack of knowledge and time, see AI as just another technology that can be learned self-taught by each developer.&lt;/p&gt;
&lt;p&gt;When I start working with a client who has followed this approach, the first thing I do is measure the actual use and impact the initiative has had, and what I observe is the following:&lt;/p&gt;</description></item><item><title>Guide to robust development with AI: Cursor and Github Copilot</title><link>https://ctomultiplier.com/guide-to-robust-development-with-ai-cursor-and-github-copilot/</link><pubDate>Wed, 14 May 2025 15:48:12 +0000</pubDate><guid>https://ctomultiplier.com/guide-to-robust-development-with-ai-cursor-and-github-copilot/</guid><description>&lt;p&gt;AI code assistants have recently spread due to the power they offer to speed up software development. However, learning to use them is not as simple as writing a simple prompt. The learning curve to fully take advantage of what they offer is not as small as we might think. If we underestimate it, we risk a) producing poor quality code with errors and security flaws or b) making limited use of the capabilities and obtaining fewer benefits than those available.&lt;/p&gt;</description></item></channel></rss>