<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by douglas nunes de mello on Medium]]></title>
        <description><![CDATA[Stories by douglas nunes de mello on Medium]]></description>
        <link>https://medium.com/@dnmello?source=rss-6321a989659f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tI5dIfV7qx1QHYmseV-c_A@2x.jpeg</url>
            <title>Stories by douglas nunes de mello on Medium</title>
            <link>https://medium.com/@dnmello?source=rss-6321a989659f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:40:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dnmello/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Engineering Productivity Theater (tickets on sale)]]></title>
            <link>https://medium.com/digital-business-services/the-engineering-productivity-theater-tickets-on-sale-746c00ca6e58?source=rss-6321a989659f------2</link>
            <guid isPermaLink="false">https://medium.com/p/746c00ca6e58</guid>
            <category><![CDATA[engineering-productivity]]></category>
            <dc:creator><![CDATA[douglas nunes de mello]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 17:33:14 GMT</pubDate>
            <atom:updated>2025-12-03T13:47:27.326Z</atom:updated>
            <content:encoded><![CDATA[<p>A Tragi-Comedy in Five Acts Based on Empirical Data</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B_2KvxsZgQzzDew9pnNqEw.png" /><figcaption>The developer’s flow-state recovery.</figcaption></figure><p>Let’s explore the difference between <strong><em>feeling</em> busy</strong> and <strong>shipping value</strong>.</p><h3>Act I: The Illusionist’s Trick (The “Vibes” vs. The Clock)</h3><p><strong>Scene:</strong> A developer prompts an AI, watches code pour onto the screen, and smiles, convinced they are finished by lunch.</p><p><strong>The Facts:</strong></p><p>According to the <strong>METR (Becker et al., 2025)</strong> study, developers forecasted that AI would speed them up by <strong>24%</strong>. After the task, they <em>felt</em> they had been sped up by <strong>20%, but </strong>they actually took <strong>19% longer</strong> to complete the tasks.</p><p><strong>The Takeaway:</strong></p><p>We are confusing “typing speed” with “thinking speed.” The theater creates an illusion of velocity because the screen fills up faster, even if the destination is further away.</p><h3>Act II: The Cast of Characters (Juniors vs. Seniors)</h3><p><strong>Scene:</strong> A Junior Developer becomes a superhero, while a Senior Developer becomes a janitor.</p><p><strong>The Facts:</strong></p><p><strong>Cui et al. (2025)</strong> and <strong>Peng et al. (2023)</strong> both confirm a massive “leveling up” effect. Less experienced developers see high adoption rates and massive gains. However, for Senior devs working on complex architectures (as seen in the <strong>METR</strong> study), the AI becomes a distracting intern.</p><p><strong>The Takeaway:</strong></p><p>For a Senior Engineer, the “Theater” consists of spending hours reviewing code generated in seconds. The productivity gain isn’t universal; it’s a wealth transfer from the senior’s patience to the junior’s output.</p><h3>Act III: The Set Design (Complexity &amp; Context)</h3><p><strong>Scene:</strong> The AI tries to navigate a 10-year-old codebase full of “spaghetti logic” and hallucinations ensue.</p><p><strong>The Facts:</strong></p><p>The <strong>Anthropic Report (2025)</strong> suggests AI <em>can</em> save 80% of time on specific tasks, but it notes that “management” and “legal” tasks (high complexity) take significantly longer than simple “food prep” logic.</p><p>The <strong>METR study</strong> highlights that <strong>“Implicit Repository Context”</strong> is the villain. AI lacks the “tacit knowledge” of why the code was written that way 5 years ago.</p><p><strong>The Takeaway:</strong></p><p>The Theater falls apart when the script gets complicated. AI excels at the “standard” (boilerplate), but fails at the “specific” (your company’s weird legacy code).</p><h3>Act IV: The Trial-and-Erros Loop (Quality &amp; Maintenance)</h3><p><strong>Scene:</strong> The curtain falls, the code is shipped, and the bugs start crawling out from backstage.</p><p><strong>The Facts:</strong></p><p><strong>Cui et al. (2025)</strong> found a <strong>38% increase in “Builds”</strong> (compilations). This implies developers are shifting from “think, then code” to “generate, fail, retry, fail, retry.”</p><p>The <strong>METR study</strong> noted developers spent less time coding, but significant time “waiting on AI” and “reviewing AI output.”</p><p><strong>The Takeaway:</strong></p><p>We aren’t necessarily coding better; we are just playing a slot machine more frequently, hoping for a jackpot (a successful build).</p><h3>Act V: Exiting the Stage (True Productivity)</h3><p><strong>Scene:</strong> The developer turns off the hype, stops performing for the audience, and actually solves the problem.</p><p><strong>The Resolution:</strong> How to use the tools without getting lost in the drama.</p><p><strong>The Facts:</strong></p><p>Synthesis of <strong>Cui et al.</strong> and <strong>Becker et al.</strong>: AI is a tool, not a replacement for expertise.</p><p>True productivity comes from identifying <em>which</em> tasks are suited for AI (low context, high boilerplate) and which require deep work (high context, architecture).</p><p><strong>The Moral:</strong></p><p>The theater of engineering productivity will survive long after the hype fades. What artificial intelligence truly changes is the amplitude of that theatre… <strong>it magnifies the discipline of strong teams and the chaos of weak ones.</strong> And in that amplification lies the real divide between future winners and losers.</p><p>But this amplification doesn’t have to be left to chance. With the right technical foundations, disciplined engineering practices, and mature delivery frameworks, AI becomes a force that elevates clarity rather than noise.<br>This is exactly where <a href="https://dbservices.pt/">DBS</a> come in &gt; helping organizations turn AI’s acceleration into sustainable engineering excellence, not more theater.</p><p>Source:<br><a href="https://arxiv.org/abs/2507.09089">https://arxiv.org/abs/2507.09089</a><br><a href="https://arxiv.org/abs/2302.06590">https://arxiv.org/abs/2302.06590</a><br><a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4945566">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4945566</a><br><a href="https://www-cdn.anthropic.com/e5645986a7ce8fbcc48fa6d2fc67753c87642c30.pdf">https://www-cdn.anthropic.com/e5645986a7ce8fbcc48fa6d2fc67753c87642c30.pdf</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=746c00ca6e58" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-business-services/the-engineering-productivity-theater-tickets-on-sale-746c00ca6e58">The Engineering Productivity Theater (tickets on sale)</a> was originally published in <a href="https://medium.com/digital-business-services">DBServices - Digital Business Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering Productivity: The Power of DORA Metrics]]></title>
            <link>https://medium.com/digital-business-services/engineering-productivity-the-power-of-dora-metrics-ddd6da9233eb?source=rss-6321a989659f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddd6da9233eb</guid>
            <dc:creator><![CDATA[douglas nunes de mello]]></dc:creator>
            <pubDate>Mon, 09 Jun 2025 19:16:05 GMT</pubDate>
            <atom:updated>2025-06-09T19:27:17.236Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hO-9_9RKgns7spYAQavrqw.png" /><figcaption>DORA Research Program</figcaption></figure><p>In today’s fast-paced technology landscape, measuring software delivery performance is crucial to achieve high stakes. Companies leveraging precise performance metrics gain the capability to optimize their processes, enhance agility, and drive innovation. This is where <a href="https://dora.dev/">DORA Metrics</a> come into play, offering actionable insights for engineering teams aiming for excellence.</p><h3>Velocity &amp; Stability</h3><p>Typically, the faster the engineering teams deliver is the lower the stability of the code in production. Velocity metrics focus on the speed and frequency of software deployments, while stability metrics emphasize the quality and reliability of those deployments. By leveraging these grouped insights, engineering teams can achieve a balanced approach, ensuring both rapid innovation and robust operational stability.</p><ol><li><strong>Deployment Frequency (DF)</strong><br>This metric indicates how often an organization successfully releases software to production or end-users.<br>Why does DF matter?<br>- Frequent deployments correlate strongly with increased agility and responsiveness.<br>- It signals healthy DevOps practices, such as continuous integration and continuous deployment (CI/CD).</li><li><strong>Lead Time for Changes (LTC)</strong><br>This measures the time it takes for code to move from commit to deployment in production.<br>Why does LTC matter?<br>- Shorter lead times imply efficiency and a streamlined development cycle.<br>- Long lead times can indicate bottlenecks or inefficiencies, reducing competitive responsiveness.</li><li><strong>Change Failure Rate (CFR)</strong><br>Change failure rate reflects the percentage of deployments causing incidents, requiring immediate attention or rollback.<br>Why does CFR matter?<br>- Low failure rates demonstrate reliability in the development and deployment processes.<br>- High failure rates might suggest insufficient testing or risky deployment practices.</li><li><strong>Mean Time to Recovery (MTR)</strong><br>This metric tracks the average time required to restore a service after a failure or incident.<br>Why does MTR matter?<br>- Quick recovery minimizes downtime, significantly enhancing customer satisfaction.<br>- Longer recovery times negatively impact user experience and overall business performance.</li></ol><p>The goal is to achieve the highest Velocity with the lowest acceptable Stability.</p><h3>Conclusion</h3><p>Effectively leveraging DORA metrics positions organizations to significantly enhance their software delivery capabilities, achieving both velocity and stability. For companies aiming to swiftly adopt these insights and unlock their full potential, DBServices Portugal provides the specialized <a href="https://dbservices.pt/lets-talk/"><strong>Automation and DevOps Assessment</strong></a> service. This comprehensive service evaluates your current practices, identifies critical bottlenecks, and proposes targeted solutions to accelerate deployments, increase reliability, and optimize overall software quality. By partnering with DBServices Portugal, organizations ensure they remain at the forefront of DevOps excellence and continuous innovation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddd6da9233eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-business-services/engineering-productivity-the-power-of-dora-metrics-ddd6da9233eb">Engineering Productivity: The Power of DORA Metrics</a> was originally published in <a href="https://medium.com/digital-business-services">DBServices - Digital Business Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From the Shift-Left to the Shift-Down Approach: What are the benefits ?]]></title>
            <link>https://medium.com/digital-business-services/from-the-shift-left-to-the-shift-down-approach-what-are-the-benefits-2d4602965232?source=rss-6321a989659f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d4602965232</guid>
            <category><![CDATA[shift-down-testing]]></category>
            <category><![CDATA[shift-left-testing]]></category>
            <category><![CDATA[dbservices]]></category>
            <category><![CDATA[engineering-productivity]]></category>
            <category><![CDATA[cognitive-load]]></category>
            <dc:creator><![CDATA[douglas nunes de mello]]></dc:creator>
            <pubDate>Tue, 29 Apr 2025 20:32:14 GMT</pubDate>
            <atom:updated>2025-04-29T20:32:14.856Z</atom:updated>
            <content:encoded><![CDATA[<h3>From the Shift-Left to the Shift-Down Approach: What are the benefits ?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-iFoDc9lCTLEOvAzZnzjMQ.png" /></figure><p>Shifting down in software development, particularly in contrast to the shift left approach, emphasizes leveraging existing platforms and tools to automate or simplify tests, rather than burdening individual developers with new approaches to validade quality. It aims to reduce the cognitive load on developers by offloading responsibilities to the platform, like automating testing, security checks, performance tests, and more.</p><p><strong>Shift-Left:</strong></p><ul><li>This approach traditionally involves moving testing, security, or other activities earlier in the software development lifecycle, closer to the coding phase. The goal is to catch and fix issues early, reducing costs and improving quality.</li></ul><p><strong>Shift-Down:</strong></p><ul><li>Instead of shifting responsibilities to individual developers, the shift down approach focuses on moving tasks to lower-level teams or platforms. This means leveraging existing tools, platforms, and infrastructure to automate or streamline processes.</li></ul><p><strong>Benefits of Shifting Down:</strong></p><ul><li><strong>Reduced Cognitive Load:</strong> Developers don’t need to learn new tools or technologies for every task, allowing them to focus on core development.</li><li><strong>Increased Efficiency:</strong> Automation and platform-driven processes can significantly speed up workflows.</li><li><strong>Improved Collaboration:</strong> Lower-level teams and platforms can handle complex tasks, facilitating smoother collaboration between developers and other stakeholders.</li><li><strong>Faster Time to Market:</strong> By streamlining processes and reducing the cognitive load on developers, the shift down approach can accelerate the software delivery process.</li></ul><p><strong>Example:</strong></p><ul><li>Instead of having each developer manually run tests, a shift down approach might involve a platform that automatically integrates this checks into the CI/CD pipeline.</li></ul><p><strong>In essence:</strong></p><ul><li>Shifting down is about optimizing the software development process by leveraging the power of platforms and automation, rather than relying solely on individual developers to “shift left”.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d4602965232" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-business-services/from-the-shift-left-to-the-shift-down-approach-what-are-the-benefits-2d4602965232">From the Shift-Left to the Shift-Down Approach: What are the benefits ?</a> was originally published in <a href="https://medium.com/digital-business-services">DBServices - Digital Business Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveraging AI for Software Engineering Productivity: Best Practices for Cost Reduction and Revenue…]]></title>
            <link>https://medium.com/digital-business-services/leveraging-ai-for-software-engineering-productivity-best-practices-for-cost-reduction-and-revenue-9d87633b8031?source=rss-6321a989659f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d87633b8031</guid>
            <category><![CDATA[quality-engineering]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[financial-engineering]]></category>
            <category><![CDATA[code-quality]]></category>
            <category><![CDATA[engineering-productivity]]></category>
            <dc:creator><![CDATA[douglas nunes de mello]]></dc:creator>
            <pubDate>Wed, 05 Mar 2025 16:48:20 GMT</pubDate>
            <atom:updated>2025-03-05T16:48:20.815Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iw7KPT2ucOuq4rql_jJspQ.png" /><figcaption>Relative distribution of code operations by year — GitClear AI Code Quality Research.</figcaption></figure><h3>Leveraging AI for Software Engineering Productivity: Best Practices for Cost Reduction and Revenue Growth</h3><p>Artificial Intelligence (AI) is transforming software engineering by accelerating development cycles and enhancing productivity. The GitClear AI Code Quality Research 2025, analyzing 211 million lines of code from 2020 to 2024, reveals that while 63% of developers use AI tools like GitHub Copilot, this speed comes at a cost: <strong>increased defects and long-term maintenance challenges.</strong> For businesses, this dual-edged sword presents both a risk and an opportunity. By strategically leveraging AI, companies can reduce development costs, minimize technical debt, and drive revenue growth through faster, higher-quality product releases. This article outlines five refined practices to achieve these goals, blending insights from GitClear with new perspectives driving your business on success.</p><h3>1. Prioritize Refactoring to Minimize Technical Debt and Reduce Long-Term Costs</h3><h3>The Insight</h3><p>The research data shows a 39.9% year-over-year decline in “Moved” code (indicative of refactoring) in 2024, dropping to 9.5% of changed lines from 24.1% in 2020. Meanwhile, “Added” lines rose from 39.2% to 46.2%, signaling that AI tools often prioritize new code generation over consolidating existing logic. This trend increases technical debt — duplicate code and poor maintainability inflate future debugging and refactoring expenses. For businesses, unchecked technical debt can lead to ballooning costs, with Gartner estimating that technical debt remediation can consume up to 40% of IT budgets in poorly managed systems.</p><h3>The Practice</h3><p>Refactoring should be a cornerstone of AI-assisted development to curb long-term costs. By focusing on reuse and consolidation, teams can reduce the volume of code requiring maintenance, directly lowering operational expenses. For example, consolidating duplicate code into reusable modules can decrease debugging time by 20–30%, according to studies like those cited in GitClear’s report (e.g., Ran Mo et al., 2023). This cost saving allows companies to allocate resources toward innovation rather than remediation, potentially accelerating time-to-market for revenue-generating features.</p><p><strong>Actionable Steps:</strong></p><ul><li>Schedule biweekly refactoring sprints to consolidate AI-generated code, targeting a “Moved” code ratio of at least 15%.</li><li>Execute assessments to identify areas with high duplication and prioritize them for refactoring, reducing future maintenance costs.</li><li>Calculate the cost savings from reduced debugging time (e.g., hours saved x developer hourly rate) and reinvest those savings into growth initiatives like new feature development.</li></ul><h3>2. Mitigate Code Duplication to Lower Defect-Related Costs and Boost Product Reliability</h3><h3>The Insight</h3><p>The research reports a 10x surge in duplicated code blocks from 2022 to 2024, with 6.66% of commits containing duplicates in 2024 versus 0.45% in 2022. This duplication correlates with higher defect rates — 57.1% of co-changed clones in deep learning projects were bug-prone, per Ran Mo et al. (2023). For businesses, defects translate into costly downtime, customer churn, and lost revenue. A 2023 report by CISQ (Consortium for IT Software Quality) estimates that software bugs cost the global economy $2.41 trillion annually, with downtime and rework being major contributors.</p><h3>The Practice</h3><p>Proactively addressing code duplication can significantly cut defect-related costs while improving product reliability — a key driver of customer retention and revenue growth. By using tools like Sonar to detect duplicates early, teams can prevent bug propagation, reducing the need for expensive post-release fixes. Reliable software also enhances customer satisfaction, leading to higher retention rates and upselling opportunities. For instance, reducing defect rates by 10% can improve customer retention by 5%, per industry benchmarks, directly impacting recurring revenue streams.</p><p><strong>Actionable Steps:</strong></p><ul><li>Integrate duplicate block detection into CI/CD pipelines using tools like SonarQube, catching issues before they escalate into costly bugs.</li><li>Set a team goal to reduce duplicate block prevalence to below 3% within six months, tracking cost savings from fewer defect-related incidents (e.g., reduced support tickets x average handling cost).</li><li>Leverage improved reliability to market your product as a premium offering, justifying higher pricing or subscription tiers to drive revenue growth.</li></ul><h3>3. Balance Speed with Stability to Optimize Development Costs and Accelerate Delivery</h3><h3>The Insight</h3><p>The Google’s 2024 DORA report, showing that a 25% increase in AI adoption correlates with a 7.2% decrease in delivery stability. While AI boosts productivity — developers added 46.2% of lines in 2024, up from 39.2% in 2020 — it also increases churn (26% YoY rise) and defects. For businesses, unstable delivery means delayed releases and higher rework costs. Conversely, faster, stable delivery accelerates time-to-market, enabling quicker revenue realization. McKinsey estimates that reducing time-to-market by 20% can increase revenue by up to 15% through earlier customer adoption and competitive positioning.</p><h3>The Practice</h3><p>Balancing speed with stability is critical for cost optimization and revenue growth. GitClear warns against measuring productivity solely by “lines added,” as AI inflates this metric through duplication. Instead, track quality metrics like defect rates and churn percentages alongside delivery speed. By maintaining stability, teams can avoid the costs of rework (e.g., 10 hours of rework per defect x developer rate) and deliver features faster, capturing market opportunities sooner. For example, a SaaS company delivering a new feature one month earlier could gain an additional $500k in monthly recurring revenue, assuming a 5% customer growth rate.</p><p><strong>Actionable Step:</strong></p><ul><li>Define a balanced scorecard with metrics like defect rate (&lt;5%), churn (&lt;4%), and delivery frequency (e.g., biweekly releases) to guide AI usage.</li></ul><h3>4. Foster Human Oversight to Optimize AI Utilization and Maximize Developer Efficiency</h3><ul><li>Implement Detect to Correct strategies using small teams to execute smoke-tests over pre-production versions (e.g., using Test Automation Squads or CoE Quality services).</li></ul><h3>The Insight</h3><p>The research highlights that AI struggles with deep contextual tasks like refactoring, with “Moved” code dropping to 9.5% in 2024 due to limited context windows (e.g., 4–8k tokens for GitHub Copilot). This inefficiency can lead to over-reliance on AI, inflating development costs through redundant work. However, human oversight can optimize AI utilization, ensuring tools are used for high-ROI tasks like initial code drafts while developers focus on high-value refactoring and innovation. A 2024 study by Forrester suggests that optimized human-AI collaboration can reduce development costs by 15–20% while improving output quality.</p><h3>The Practice</h3><p>Position human developers as strategic overseers to maximize AI efficiency, reducing wasted effort and costs. By assigning senior developers to refine AI-generated code, teams can avoid unnecessary iterations, lowering the cost per feature delivered. Moreover, humans excel at identifying opportunities for innovation — such as new features that address unmet market needs — which can drive significant revenue growth. For example, a well-refactored codebase might enable a 25% faster rollout of a new AI-driven analytics feature, capturing a $1M market segment previously inaccessible due to delays.</p><p><strong>Actionable Steps:</strong></p><ul><li>Allocate 20% of senior developer time to review and refactor AI-generated code, targeting a 10% reduction in iteration cycles (e.g., saving 5 hours per feature x developer rate).</li><li>Use AI for low-context tasks (e.g., boilerplate generation) and humans for high-context tasks (e.g., system architecture), optimizing resource allocation.</li><li>Identify revenue opportunities enabled by cleaner codebases, such as faster prototyping of new features, and prioritize them in sprint planning.</li></ul><h3>5. Incentivize Long-Term Maintainability to Reduce Operational Costs and Drive Scalable Growth</h3><h3>The Insight</h3><p>The research warns that when productivity is measured by short-term metrics like “tickets solved,” AI takes the path of least resistance — duplicating code (12.3% of changes in 2024) rather than simplifying it. This increases operational costs as technical debt accumulates, potentially consuming 30–40% of IT budgets, per Gartner. Conversely, maintainable codebases enable scalability, allowing businesses to onboard new developers faster and release features more efficiently. A scalable codebase can support 50% faster feature growth, per McKinsey, translating into higher revenue through expanded product offerings.</p><h3>The Practice</h3><p>Realign team incentives to prioritize long-term maintainability, reducing operational costs and enabling scalable growth. By rewarding practices like code reuse and duplication reduction, companies can lower the cost of maintaining software over time. For instance, reducing duplicate blocks by 10% could save $100k annually in maintenance costs for a mid-sized firm (assuming 500k lines of code and $0.20 per line maintenance cost). A maintainable codebase also accelerates onboarding and feature development, allowing businesses to scale product lines and capture larger market shares — potentially increasing revenue by 20% through diversified offerings.</p><p><strong>Actionable Steps:</strong></p><ul><li>Set KPIs rewarding maintainability, such as achieving a “Moved” to “Copy/Pasted” ratio of 1:1 or reducing duplicate blocks by 20% annually, and tie them to cost-saving targets.</li><li>Use reporting tools to track maintenance cost reductions (e.g., hours spent on tech debt x developer rate) and redirect savings into R&amp;D for new revenue streams.</li><li>Leverage maintainability to scale product offerings faster, such as launching a new module in half the time, and market it to new customer segments to drive growth.</li></ul><h3>Conclusion: Harnessing AI for Cost-Effective, Revenue-Driving Development</h3><p>AI offers immense potential to revolutionize software engineering, but as GitClear’s 2025 research underscores, its benefits must be balanced with a focus on quality to avoid costly pitfalls. By prioritizing refactoring, mitigating duplication, balancing speed with stability, fostering human oversight, and incentivizing maintainability, businesses can reduce development and operational costs while accelerating revenue growth. For instance, cutting defect-related costs by 15% could save a company $150k annually, while faster feature delivery might add $1M in new revenue through early market entry.</p><p>The future lies in a strategic partnership between AI and human ingenuity. The conclusion, “developers should emphasize their still-uniquely human ability to ‘simplify’ and ‘consolidate’ code” and blending AI’s speed with human foresight, companies can not only optimize costs but also position themselves for scalable, revenue-driven growth in an increasingly competitive landscape.</p><p><strong>Whoever Learns To Take Advantage Of AI First Will Master The Roadmap.</strong></p><p><strong>References:</strong></p><ul><li>GitClear AI Code Quality Research v2025.2.5, February 2025.</li><li>Google DORA 2024 Report: Accelerate State of DevOps.</li><li>Stack Overflow 2024 Developer Survey.</li><li>Gartner, “Managing Technical Debt,” 2023.</li><li>CISQ, “The Cost of Poor Software Quality,” 2023.</li><li>McKinsey, “Accelerating Time-to-Market for Growth,” 2024.</li><li>Forrester, “Human-AI Collaboration in Software Development,” 2024.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d87633b8031" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-business-services/leveraging-ai-for-software-engineering-productivity-best-practices-for-cost-reduction-and-revenue-9d87633b8031">Leveraging AI for Software Engineering Productivity: Best Practices for Cost Reduction and Revenue…</a> was originally published in <a href="https://medium.com/digital-business-services">DBServices - Digital Business Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 Practices for Quality Continuous Integration (QCI) Pipelines]]></title>
            <link>https://medium.com/digital-business-services/top-5-practices-for-quality-continuous-integration-qci-pipelines-f8d0a8ca893d?source=rss-6321a989659f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8d0a8ca893d</guid>
            <dc:creator><![CDATA[douglas nunes de mello]]></dc:creator>
            <pubDate>Mon, 16 Dec 2024 11:38:07 GMT</pubDate>
            <atom:updated>2024-12-16T11:38:07.832Z</atom:updated>
            <content:encoded><![CDATA[<p>One step ahead for lead engineering companies is to have a fast, reliable and straight-to-the-point CI pipeline. According with <a href="https://services.google.com/fh/files/misc/2024_final_dora_report.pdf">DORA Report 2024</a> (DevOps Four-Key Metrics) CI practices reduce the cost of ongoing software development and maintenance, in addition to increase the productivity of the teams.</p><p>The objective of a CI pipeline is to improve the <strong>Software Engineer Full-Potential</strong>, by the way we have some aspects that contribute with the DevEx (Developer Experience) to achieve this goal:</p><ul><li><strong>Reduce the Cognitive Load Tasks:</strong> Using CI tools that support well-known or familiar programming languages, like YAML or SDKs in developers’ preferred languages, helps reduce the cognitive load caused by unfamiliar DSLs — <em>less new things, more the same.</em></li><li><strong>Keep the Developer Flow State:</strong> Simplified CI tools and targeted training help developers maintain flow state by streamlining deployment workflows and reducing the cognitive burden of managing rarely-used tools — <em>a music and a great headphone.</em></li><li><strong>Increase the Feedback Loops:</strong> Improving CI pipeline observability, building a knowledge base of common errors, and integrating an LLM-based bot can accelerate feedback loops and enable developers to troubleshoot issues independently — <em>logs is the new old feedback.</em></li></ul><figure><img alt="A typical Continuous Integration Pipeline focused on Quality Assurance." src="https://cdn-images-1.medium.com/max/745/1*lrWi5JuVYTQkje-rfDiujQ.png" /><figcaption>A typical Continuous Integration Pipeline focused on Quality Assurance.</figcaption></figure><p>For now, we split at five stages of a CI pipeline to put in practice a good DevEx for your teammates:</p><ol><li><strong>Automate Builds: </strong>Automated builds ensure new changes integrate with the existing code and verify your dependencies. With a well-configured CI pipeline, the build step prevent a codification error from being merged into the main branch, protecting the work of other team members who depend on a stable codebase. When a build is successful, it qualifies the application for further testing.<br>Example tools: <a href="https://gradle.org/">Gradle</a>, <a href="https://maven.apache.org/">Maven</a>.</li><li><strong>Shift-Left Testing: </strong>In a CI pipeline, anticipating defects is a paramount and there are tools that can do this even on the developer’s machine during coding time. However, having a second defense in the pipeline can be a winning strategy.<br>Example tools: <a href="https://www.sonarsource.com/products/sonarlint/">SonarQube IDE</a>.</li><li><strong>Automate Tests: </strong>Tests it&#39;s the midway of a CI pipeline. We have classic Test Pyramid for this stage, starting with <strong>Unit Tests</strong> (focused on faster and rapid feedback for developer), <strong>Integration Tests</strong> (focused on testing the another part of the code without changed) and <strong>End-to-End Tests</strong> (focused on Priority-Zero-Test strategy: balance with critical flows and great coverage).<strong><br></strong>Example tools: <a href="https://pytest.org/">Pytest</a> and <a href="https://jestjs.io/">Jest</a> (for Unit), <a href="https://testcontainers.com/">TestContainers</a> and <a href="https://mochajs.org/">Mocha</a> (for Integration), <a href="https://www.cypress.io/">Cypress</a> and <a href="https://robotframework.org/">Robot Framework</a> (for E2E).</li><li><strong>Quality Check: </strong>Test Observability Dashboards can produce a bird’s eye view of the release, comparing it to previous versions, showing flaky tests, presenting new areas in the code contain new defects.<strong><br></strong>Example tools: <a href="https://www.datadoghq.com/">Datadog</a> or <a href="https://grafana.com/">Grafana</a>.</li><li><strong>Security Scan: </strong>Integrating security checks into your CI pipeline ensures your code stays maintainable and secure. Tools like SonarQube can automatically scan your codebase to identify issues such as bugs, code smells and technical debt, supporting a great feedback loop for the developer. <strong><br></strong>Example tools: <a href="https://snyk.io/">SNYK</a> or <a href="https://www.sonarsource.com/products/sonarqube/">SonarQube</a>.</li></ol><blockquote>All of these practices take a certain amount of effort to implement, but once done, it doesn’t take much effort to maintain — Martin Fowler.</blockquote><p><a href="https://martinfowler.com/articles/originalContinuousIntegration.html">Continuous Integration (original version)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8d0a8ca893d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-business-services/top-5-practices-for-quality-continuous-integration-qci-pipelines-f8d0a8ca893d">Top 5 Practices for Quality Continuous Integration (QCI) Pipelines</a> was originally published in <a href="https://medium.com/digital-business-services">DBServices - Digital Business Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Key-Topics About Software Development Levels]]></title>
            <link>https://medium.com/digital-business-services/3-key-topics-about-software-development-levels-54eb403b5a96?source=rss-6321a989659f------2</link>
            <guid isPermaLink="false">https://medium.com/p/54eb403b5a96</guid>
            <dc:creator><![CDATA[douglas nunes de mello]]></dc:creator>
            <pubDate>Thu, 04 Apr 2024 10:15:33 GMT</pubDate>
            <atom:updated>2024-04-04T11:00:32.410Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R6NZyaT_jsIktc6bBAUo9Q.png" /></figure><p>At DBServices, <strong>Test Automation &amp; DevOps</strong> are a cornerstone of our approach to advancing our customers’ Software Development Maturity Levels. While recognizing the uniqueness of each scenario, but we return to the same topics when we perform Assessments and Audits.<br>Forget all about buzzwords at the first image — just to get your attention . We have identified three pivotal elements that always feature in our discussions aimed at fostering improvement:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Gbebvysfd9z8NjEzuDWvWg.png" /><figcaption>Trunk-Based Development</figcaption></figure><p><strong>1 - Version Control (VC)</strong><br>Version control is a set of <strong>Practices &amp; Tools</strong> for managing codebases. Software Engineers use version control to keep on-track every line of code, share, review, and synchronize changes with your team. <strong>GIT</strong> is the most popular version control tool, created by Linus Torvalds to support the open-source development of Linux, It uses a distributed repository model that can efficiently handle projects of any size.<br>One of the most practices used for version control is the <strong>Trunk-Based Development</strong>, is a branching model where most of the work takes place in a single trunk, usually called master, or main. The trunk receives daily merges from all engineers in the team. This practices simplify the version control, because the trunk is a single source of truth, minimizing chances of merge conflict.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ZapTgHqd8R8BGCVuCPlclw.png" /><figcaption>Continuous Integration Pipeline</figcaption></figure><p><strong>2 - Continuous Integration &amp; Continuous Delivery (CI/CD)</strong><br>Continuous Integration (CI) is a software development practice where software engineers — following the trunk-based model — merge their changes to the main branch many times per day. CI is supported by <strong>Automated Tests</strong> that runs them on every change. As a result, failures are made visible as soon as possible introducing shift-left testing practices fixing the problems in advance.<br>Continuous Delivery (CD) is an extension of CI. Its goal is to automate every step required to package and release a software feature. CD is supported by <strong>Pipelines</strong> and the output takes the form of a deployable binary, package or container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rIBn_buqxtK0dzteQ6UEOA.png" /><figcaption>Test Automation Levels (TAL) by DBServices</figcaption></figure><p><strong>3 - Test Automation (TA)</strong><br>Test Automation is integral to and inseparable from CI. The main benefit teams get from TA is the continuous feedback. Developers set up tests in the CI to check that their code behaves according to expectations and requires that all tests are automated without human intervention.<br>Automation Frameworks like Cypress, Robot Framework, Playwright and others accelerate the <strong>Feedback Loops</strong> and reduce the risk of introducing failures, creating a preventive approach. To do this well, it&#39;s nice to have a <strong>TA Foundation</strong>, which will ensure best practices for creating and maintaining these test scenarios.</p><p><strong>Conclusion<br></strong>These three pillars (VC+CI/CD+TA) are daily-basis to implement small improvements with our customers. With a Detect to Correct Approach, we have experts consultants to increase your software development maturity focused on Commit-&gt;Test-&gt;Deploy loop.<br><a href="https://dbservices.pt/lets-talk/">Let’s talk.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54eb403b5a96" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-business-services/3-key-topics-about-software-development-levels-54eb403b5a96">3 Key-Topics About Software Development Levels</a> was originally published in <a href="https://medium.com/digital-business-services">DBServices - Digital Business Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking Advanced Security Solutions with GitHub and DBServices]]></title>
            <link>https://medium.com/digital-business-services/unlocking-advanced-security-solutions-with-github-and-dbservices-abbf2e7d6664?source=rss-6321a989659f------2</link>
            <guid isPermaLink="false">https://medium.com/p/abbf2e7d6664</guid>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[devops-tool]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[douglas nunes de mello]]></dc:creator>
            <pubDate>Fri, 22 Mar 2024 12:28:09 GMT</pubDate>
            <atom:updated>2024-03-22T12:28:09.520Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s digital landscape, security is paramount. With the rise of cyber threats and data breaches, organizations are continually seeking robust solutions to safeguard their assets. GitHub, a leading platform for software development and collaboration, offers advanced security features to protect code repositories and mitigate risks effectively. Let’s delve into GitHub’s advanced security capabilities and explore how they align with the services provided by DBServices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XduFO8f6-Lrsk643rkKQ_w.png" /><figcaption>Advanced Security Features - GitHub.</figcaption></figure><h3>GitHub Advanced Security: A Brief Overview</h3><p>GitHub Advanced Security provides a comprehensive suite of tools designed to enhance the security posture of software development projects. It encompasses features such as:</p><ol><li><strong>Code Scanning:</strong> GitHub’s code scanning capability helps identify potential security vulnerabilities in codebases. It integrates with various static analysis tools to analyze code as it’s written, providing early detection of issues.</li><li><strong>Secret Scanning:</strong> This feature scans repositories for exposed credentials and other sensitive information, helping prevent accidental leaks that could compromise security.</li><li><strong>Dependency Graph:</strong> GitHub’s dependency graph automatically identifies and alerts users to known vulnerabilities in project dependencies, enabling proactive management of third-party code.</li><li><strong>Security Advisories:</strong> GitHub aggregates security advisories from various sources, providing users with insights into known vulnerabilities affecting their projects and guidance on remediation.</li><li><strong>Security Policies:</strong> Organizations can enforce security policies within their repositories, ensuring compliance with industry standards and best practices.</li></ol><h3>Leveraging DBServices for Enhanced Security Solutions</h3><p>DBServices, a reputable provider of IT solutions, complements GitHub’s advanced security offerings with a range of services tailored to meet the evolving needs of businesses. Here’s how DBServices’ offerings align with GitHub’s security features:</p><ol><li><strong>Assessment and Audit:</strong> DBServices conducts comprehensive assessments to identify pain points across IT infrastructures. This aligns with GitHub’s code scanning and secret scanning capabilities, providing organizations with a holistic view of their security posture.</li><li><strong>Test Automation:</strong> By simulating real-world, DBServices’ testing services help uncover weaknesses in systems and applications. This proactive approach (with Test Automation Levels — TAL) parallels GitHub’s emphasis on early detection and mitigation of erros and failures.</li><li><strong>Software Development Lifecycle (SDLC) Consulting: </strong>DBServices assists organizations in implementing development practices, aligning with GitHub’s security policies feature. By establishing and enforcing security guidelines, businesses can reduce the risk of introducing vulnerabilities into their codebases.</li><li><strong>Automation Academy with Software Engineering Best Practices: </strong>Unlock the potential of your team through DBServices training focused on Automation &amp; DevOps. Empower your engineers with the latest tools and practices on the market, generating a competitive advantage by increasing the frequency of deployment in production.</li></ol><h3>Conclusion</h3><p>As organizations navigate the complex landscape of threats, the integration of advanced security solutions becomes imperative. GitHub’s Advanced Security features provide developers with powerful tools to proactively identify and address security vulnerabilities throughout the software development lifecycle. When coupled with DBServices’ expertise in assessments, consulting, academy and engineering, organizations can fortify your teams and mitigate risks effectively.</p><p>By leveraging the synergies between GitHub’s advanced security capabilities and DBServices’ comprehensive software engineering solutions, businesses can enhance their resilience against evolving cyber threats and safeguard their valuable assets. Together, GitHub and DBServices empower organizations to embrace innovation with confidence, knowing that their digital ecosystems are fortified against potential risks.</p><p>Let&#39;s talk: <a href="https://dbservices.pt/lets-talk/">https://dbservices.pt/lets-talk/</a></p><h3>References</h3><p><a href="https://resources.github.com/ghazdo/">GitHub Advanced Security &amp; Azure DevOps</a></p><p><a href="https://learn.microsoft.com/en-us/azure/devops/repos/security/configure-github-advanced-security-features">Configure GitHub Advanced Security for Azure DevOps</a></p><p><a href="https://docs.github.com/en/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning-with-codeql">About code scanning with CodeQL</a></p><p><a href="https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning">About secret scanning</a></p><p><a href="https://docs.github.com/en/code-security/dependabot/dependabot-alerts/about-dependabot-alerts">About Dependabot alerts</a></p><p><a href="https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review">About dependency review</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abbf2e7d6664" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-business-services/unlocking-advanced-security-solutions-with-github-and-dbservices-abbf2e7d6664">Unlocking Advanced Security Solutions with GitHub and DBServices</a> was originally published in <a href="https://medium.com/digital-business-services">DBServices - Digital Business Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Remove Yourself from Operations and Scale 10x Faster:]]></title>
            <link>https://medium.com/digital-business-services/how-to-remove-yourself-from-operations-and-scale-10x-faster-9cd4ad30e1cb?source=rss-6321a989659f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cd4ad30e1cb</guid>
            <dc:creator><![CDATA[douglas nunes de mello]]></dc:creator>
            <pubDate>Sat, 25 Mar 2023 09:30:56 GMT</pubDate>
            <atom:updated>2023-03-25T09:45:31.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZJf6BIZ0bXbviwXZPxmz3g.jpeg" /><figcaption>Azenhas do Mar (Portugal)</figcaption></figure><p>Matt Gray, founder &amp; CEO at <a href="http://herb.co/">herb.co</a> talks about how growth your business with a focused small team with results-oriented:</p><ol><li><strong>Track Your Time on 15-Minute Intervals</strong> — using a timer, reviewing the list and identifying tasks to be OUTSOURCED.</li><li><strong>Mark Tasks That Can Be Delegated</strong> — This task is core? It’s repeatable? Delegated It’s possible?</li><li><strong>Value Your Time at $2k/Hour</strong> — filter the tasks to outsourced for people/companies to expend less time.</li><li><strong>Hire a Assistance to Scale Your Workflow</strong> — hire a service with years of experience, efficiency and full context to increase your workflow step-by-step.</li><li><strong>The Quality Assistance Criteria </strong>— use the reliability and experience of your specialists to construct requirements to be a solid hire.</li><li><strong>Onboard Your Team</strong> — how often you meet, how you communicate (slack, asana, others), how they should track and update you on completed tasks.</li><li><strong>Create Systems for Each Task</strong> — create how-to&#39;s, draft best practices and record loom videos to effective communication = smooth operations.</li><li><strong>Review Systems and Performance Weekly </strong>— create new process, new templates and change an existing process.</li></ol><p>Using our services like Automation Squad, QA-as-a-Service, DevOps Consulting Services, Automation &amp; DevOps Assessment and others, we’ll release you and your crew to focus on what really matters and reach the full potential of your company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cd4ad30e1cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-business-services/how-to-remove-yourself-from-operations-and-scale-10x-faster-9cd4ad30e1cb">How to Remove Yourself from Operations and Scale 10x Faster:</a> was originally published in <a href="https://medium.com/digital-business-services">DBServices - Digital Business Services</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>