<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dpe on CTOMultiplier</title><link>https://ctomultiplier.com/tags/dpe/</link><description>Recent content in Dpe on CTOMultiplier</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 25 Sep 2025 22:12:26 +0200</lastBuildDate><atom:link href="https://ctomultiplier.com/tags/dpe/feed.xml" rel="self" type="application/rss+xml"/><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></channel></rss>