<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Programming on CTOMultiplier</title><link>https://ctomultiplier.com/tags/programming/</link><description>Recent content in Programming on CTOMultiplier</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 26 Sep 2025 12:33:04 +0200</lastBuildDate><atom:link href="https://ctomultiplier.com/tags/programming/feed.xml" rel="self" type="application/rss+xml"/><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><item><title>Do you know what DPE is?</title><link>https://ctomultiplier.com/do-you-know-what-dpe-is/</link><pubDate>Wed, 27 Sep 2023 07:23:39 +0000</pubDate><guid>https://ctomultiplier.com/do-you-know-what-dpe-is/</guid><description>&lt;p&gt;DPE stands for Developer Productivity Engineering and is the name of a new discipline that aims to improve developer productivity through automation, observability and tool enhancement.&lt;/p&gt;
&lt;p&gt;The work of a developer when programming has three phases: code -&amp;gt; build -&amp;gt; test, the developer repeats this sequence tens or even hundreds of times a day. And in many cases the build and test phases can take in the order of minutes. For example: if the build of an application takes 5 minutes and the developer does 10 builds per day, that&amp;rsquo;s 50 minutes that the developer has to wait per day. Similarly, the testing phase can increase the developer&amp;rsquo;s waiting time. Multiply that by the number of developers in a company and the cost is significant.&lt;/p&gt;</description></item><item><title>Guide to do Code Reviews in your team</title><link>https://ctomultiplier.com/guide-to-do-code-reviews-in-your-team/</link><pubDate>Tue, 25 Jul 2023 15:42:32 +0000</pubDate><guid>https://ctomultiplier.com/guide-to-do-code-reviews-in-your-team/</guid><description>&lt;p&gt;Code reviews are a practice that has become widespread in recent years, where one or more developers review the new code implemented by another colleague, with the aim of detecting code quality issues, bugs, vulnerabilities, bad practices, etc&amp;hellip; . This allows feedback loops to be shortened, which we know is very beneficial because the later a problem is discovered, the higher the cost of fixing it and the greater the potential business impact.&lt;/p&gt;</description></item><item><title>When abstractions leak</title><link>https://ctomultiplier.com/when-abstractions-leak/</link><pubDate>Thu, 15 Jun 2023 18:47:25 +0000</pubDate><guid>https://ctomultiplier.com/when-abstractions-leak/</guid><description>&lt;p&gt;In the software world we constantly use abstractions to make our work easier, as they abstract us from other domains and significantly reduce the complexity we have to deal with. An example of abstraction is ORMs. An ORM allows us to abstract the application from the database being used. Instead of having to write queries (specific to the database engine) to access the data, the ORM allows us to use the programming language we are using to code the application, also to access the data. Anyone who has used ORMs knows that in many cases the abstraction works well and brings a lot of value, but when the application requires us to get multiple related entities, among other examples, is when we start to see the limitations. In these cases, it is common that ORMs do not always generate the optimal queries, or that they require us to write excessively complex code, so that sometimes we end up writing queries directly in the language of the underlying DB. This means setting aside abstraction for such cases.&lt;/p&gt;</description></item></channel></rss>