# Maintainability

Maintainability is the degree to which a software product or system can be effectively and efficiently modified by its intended maintainers.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Measuring What Matters in the Age of AI: The Research Software Metrics Landscape

DevFeed: [Measuring What Matters in the Age of AI: The Research Software Metrics Landscape](<https://devfeed.tech/articles/measuring-what-matters-in-the-age-of-ai-the-research-software-metrics-landscape-142130.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23253>)

Author: Addi Malviya-Thakur, Reed Milewicz, Gregory R. Watson, Audris Mockus

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Code quality](<https://devfeed.tech/topics/code-quality.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [attribution](<https://devfeed.tech/tags/attribution.md>), [automation](<https://devfeed.tech/tags/automation.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [code](<https://devfeed.tech/tags/code.md>), [community](<https://devfeed.tech/tags/community.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-ce](<https://devfeed.tech/tags/cs-ce.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [data](<https://devfeed.tech/tags/data.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [development](<https://devfeed.tech/tags/development.md>), [effort](<https://devfeed.tech/tags/effort.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [era](<https://devfeed.tech/tags/era.md>), [guidance](<https://devfeed.tech/tags/guidance.md>), [health](<https://devfeed.tech/tags/health.md>), [maintainability](<https://devfeed.tech/tags/maintainability.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [research](<https://devfeed.tech/tags/research.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

A focused synthesis of 49 substantive references groups research software metrics into eight families, assessed by data source, claimed construct, validity evidence, automation potential, and susceptibility to misuse. It finds that widely used metrics can be partial signals but are weak standalone measures of scientific impact. AI-assisted development sharpens gaps in provenance, generated-code maintainability, reviewer effort, dependencies, reuse and community-health signals, and credit for human work. The authors recommend contextual, mixed-method use and provide decision guidance for RSEs, principal investigators, institutions, and funders. Findings are limited to the focused review; a 727-record triaged corpus and reproducible search protocol are presented as groundwork for a future systematic mapping study.

### Source excerpt

arXiv:2611.23253v1 Announce Type: new Abstract: Research software now serves as a primary instrument of science, but the methods the community uses to judge its quality, sustainability, reuse, and impact remain scattered across software engineering, open science, FAIR software, citation, and research-assessment literature. AI-assisted development sharpens the problem: code can be produced at rates that outpace human review capacity, provenance and attribution are harder to track, scholarly credit systems cannot keep pace, and existing metrics inherit assumptions about how research software gets developed that may no longer apply. To aid in navigating these challenges, we present a focused landscape synthesis of research software metrics based on 49 substantive references, organizing the recurring metrics into eight families described by data source, claimed construct, evidence of validity, automation potential, and susceptibility to misuse. Many widely cited research software metrics serve as partial signals but make weak standalone measures of scientific impact. The AI era opens or widens gaps around provenance, maintainability of generated code, reviewer effort, model and data dependencies, reuse and community-health signal inflation, and credit for human labor that AI does not perform. We argue for responsible, contextual, mixed-method use of research software metrics, and offer decision guidance for Research Software Engineers (RSEs), principal investigators, institutions, and funders selecting metrics that support better software, fairer credit, and more trustworthy science. All findings rest on the 49-reference focused review; a reproducible search-and-triage protocol and a 727-record triaged corpus accompany the paper as a transparency artifact for a future full systematic mapping study.

## Maintainers don't need more AI bug reports. They need fixes.

DevFeed: [Maintainers don't need more AI bug reports. They need fixes.](<https://devfeed.tech/articles/maintainers-don-t-need-more-ai-bug-reports-they-need-fixes-139419.md>)

Original publisher: [Read original article](<https://github.blog/open-source/maintainers/maintainers-dont-need-more-ai-bug-reports-they-need-fixes/>)

Author: Gregg Cochran

Published: 2026-11-17T18:29:29Z

Content type: news

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [ai-triage](<https://devfeed.tech/tags/ai-triage.md>), [alert](<https://devfeed.tech/tags/alert.md>), [autofix](<https://devfeed.tech/tags/autofix.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-reports](<https://devfeed.tech/tags/bug-reports.md>), [codename](<https://devfeed.tech/tags/codename.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [github](<https://devfeed.tech/tags/github.md>), [github-security-lab](<https://devfeed.tech/tags/github-security-lab.md>), [half](<https://devfeed.tech/tags/half.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-projects](<https://devfeed.tech/tags/open-source-projects.md>), [pilot](<https://devfeed.tech/tags/pilot.md>), [private](<https://devfeed.tech/tags/private.md>), [reports](<https://devfeed.tech/tags/reports.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

In the Codename MDASH pilot, GitHub and Microsoft turned thousands of potential vulnerability findings across six open source projects into 99 private reports with suggested fixes. Microsoft's MAI Cyber model scanned projects; a GitHub Security Lab AI triage agent filtered duplicates and invalid or lower-impact findings, then seven Microsoft FORGE Lab researchers reviewed the results by hand. Maintainers had fixed 55 reports by November 15, with 14 fixes already released. The process aimed to reduce maintainer workload while leaving decisions about fixes and timing to maintainers. The evidence is early: six projects, and researcher review took about two days per project. The post says effective delivery also requires private vulnerability reporting, CI/CD testing on private forks, and access to cyber-capable models for checking proofs of concept.

### Source excerpt

In the Codename MDASH pilot, GitHub and Microsoft turned thousands of raw AI findings into 99 checked, private reports with suggested fixes for six widely used open source projects. Maintainers have already fixed more than half. The post Maintainers don't need more AI bug reports. They need fixes. appeared first on The GitHub Blog.

## How British Airways is accelerating the modernization of its Java services

DevFeed: [How British Airways is accelerating the modernization of its Java services](<https://devfeed.tech/articles/how-british-airways-is-accelerating-the-modernization-of-its-java-services-137163.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/how-british-airways-is-accelerating-the-modernization-of-its-java-services/>)

Author: Shane Routley

Published: 2026-11-16T20:16:41Z

Content type: news

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [Legacy Modernization](<https://devfeed.tech/topics/legacy-modernization.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>)

Tags: [accelerate](<https://devfeed.tech/tags/accelerate.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [auto-scaling](<https://devfeed.tech/tags/auto-scaling.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [aws-graviton](<https://devfeed.tech/tags/aws-graviton.md>), [aws-transform](<https://devfeed.tech/tags/aws-transform.md>), [business](<https://devfeed.tech/tags/business.md>), [containerized](<https://devfeed.tech/tags/containerized.md>), [custom](<https://devfeed.tech/tags/custom.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [java](<https://devfeed.tech/tags/java.md>), [modernization](<https://devfeed.tech/tags/modernization.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

British Airways is modernizing more than 250 Java services across roughly 750 repositories, moving from Amazon EC2 to containerized services on Amazon ECS with AWS Fargate and Graviton. Its 20-step workflow uses automation for repository and production-log analysis, dependency cataloging, infrastructure setup, and baseline tests; AWS Transform custom applies agentic AI to upgrade services to Java 21, change deployment patterns, and replace legacy dependencies. The transformed services are tested against the original regression and performance baselines, then undergo human code review, security and quality scans, operational review, and cybersecurity approval before go-live. BA reports that its first transformed service entered production and says the approach reduces manual modernization effort, freeing engineers for other work. The excerpt gives no quantified time or cost savings.

### Source excerpt

Learn how British Airways is using AWS Transform custom, agentic AI, and automation to accelerate the modernization of its Java services, migrating more than 250 business services from Amazon EC2 to a containerized, auto scaling architecture on Amazon ECS with AWS Fargate and AWS Graviton.

## Architectural Degradation: Definition, Motivations, Measurement and Remediation Approaches

DevFeed: [Architectural Degradation: Definition, Motivations, Measurement and Remediation Approaches](<https://devfeed.tech/articles/architectural-degradation-definition-motivations-measurement-and-remediation-approaches-131659.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2507.14547>)

Author: Noman Ahmad, Ruoyu Su, Matteo Esposito, Andrea Janes, Valentina Lenarduzzi, Davide Taibi

Published: 2026-11-13T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Maintainability](<https://devfeed.tech/topics/maintainability.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [academic](<https://devfeed.tech/tags/academic.md>), [aging](<https://devfeed.tech/tags/aging.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [code](<https://devfeed.tech/tags/code.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [coupling](<https://devfeed.tech/tags/coupling.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [definition](<https://devfeed.tech/tags/definition.md>), [design](<https://devfeed.tech/tags/design.md>), [detection](<https://devfeed.tech/tags/detection.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [integration](<https://devfeed.tech/tags/integration.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [literature](<https://devfeed.tech/tags/literature.md>), [maintainability](<https://devfeed.tech/tags/maintainability.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [organizational](<https://devfeed.tech/tags/organizational.md>), [remediation](<https://devfeed.tech/tags/remediation.md>)

### AI overview

A review of 108 academic and gray-literature studies finds that architectural degradation is a socio-technical problem shaped by architectural, code, and process debt. Definitions cover code violations, design drift, and structural decay; causes include poor documentation, hasty fixes, and knowledge loss. The review identifies 54 metrics and 31 measurement techniques, largely focused on smells, cohesion and coupling, and system evolution. Detection is well studied, but most tools offer little support for ongoing or preventive remediation, and metrics, tools, and repair logic are poorly integrated. The authors identify continuous remediation as a key gap and call for holistic, proactive strategies.

### Source excerpt

arXiv:2507.14547v2 Announce Type: replace Abstract: Architectural degradation, also known as erosion, decay, or aging, impacts system quality, maintainability, and adaptability. Although widely acknowledged, current literature shows fragmented definitions, metrics, and remediation strategies. Our study aims to unify understanding of architectural degradation by identifying its definitions, causes, metrics, tools, and remediation approaches across academic and gray literature. We conducted a multivocal literature review of 108 studies extracting definitions, causes, metrics, measurement approaches, tools, and remediation strategies. We developed a taxonomy encompassing architectural, code, and process debt to explore definition evolution, methodological trends, and research gaps. Architectural degradation has shifted from a low-level issue to a socio-technical concern. Definitions now address code violations, design drift, and structural decay. Causes fall under architectural (e.g., poor documentation), code (e.g., hasty fixes), and process debt (e.g., knowledge loss). We identified 54 metrics and 31 measurement techniques, focused on smells, cohesion/coupling, and evolution. Yet, most tools detect issues but rarely support ongoing or preventive remediation. Degradation is both technical and organizational. While detection is well-studied, continuous remediation remains lacking. Our study reveals missed integration between metrics, tools, and repair logic, urging holistic, proactive strategies for sustainable architecture.

## TorchCurves: Differentiable Parametric Curves

DevFeed: [TorchCurves: Differentiable Parametric Curves](<https://devfeed.tech/articles/torchcurves-differentiable-parametric-curves-128854.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.14516>)

Author: Alex Shtoff

Published: 2026-11-11T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [PyTorch](<https://devfeed.tech/topics/pytorch.md>), [procedural curves](<https://devfeed.tech/topics/procedural-curves.md>), [Library](<https://devfeed.tech/topics/library.md>), [Neural Network](<https://devfeed.tech/topics/neural-network.md>), [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [vectorization techniques](<https://devfeed.tech/topics/vectorization-techniques.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [SciPy](<https://devfeed.tech/topics/scipy.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [applications](<https://devfeed.tech/tags/applications.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [batches](<https://devfeed.tech/tags/batches.md>), [can](<https://devfeed.tech/tags/can.md>), [central](<https://devfeed.tech/tags/central.md>), [combines](<https://devfeed.tech/tags/combines.md>), [compare](<https://devfeed.tech/tags/compare.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [custom](<https://devfeed.tech/tags/custom.md>), [embeddings](<https://devfeed.tech/tags/embeddings.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [experiments](<https://devfeed.tech/tags/experiments.md>), [feature](<https://devfeed.tech/tags/feature.md>), [functional](<https://devfeed.tech/tags/functional.md>), [github](<https://devfeed.tech/tags/github.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [https](<https://devfeed.tech/tags/https.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [stat-ml](<https://devfeed.tech/tags/stat-ml.md>)

### AI overview

TorchCurves makes vector-valued parametric curves learnable in PyTorch: it maps batches of scalar inputs to curve points using B-spline or Legendre bases and differentiates through both inputs and coefficients. Coefficients can be optimized with a model or generated by another network. The library offers trainable and reusable basis modules plus a functional interface, with applications including continuous feature embeddings, Kolmogorov-Arnold networks, and functional regression. Its vectorized implementation uses classical evaluation algorithms without custom hardware kernels. Timing experiments compare evaluation with NumPy and SciPy, and KAN training with EfficientKAN; the abstract says these show both practical cases and substantial overhead, but gives no specific results.

### Source excerpt

arXiv:2611.14516v1 Announce Type: new Abstract: We present TorchCurves, a PyTorch library that treats vector-valued parametric curves as learnable primitives. Its central operation maps batches of scalar inputs to points on curves represented in B-spline or Legendre polynomial bases, with differentiation through both inputs and coefficients. Curve coefficients can be optimized jointly with the surrounding model or produced by another network. The library provides trainable modules, reusable basis modules, and a functional interface, supporting applications ranging from continuous feature embeddings to Kolmogorov-Arnold networks and functional regression. Its implementation combines classical evaluation algorithms with vectorized PyTorch operations, emphasizing readability and maintainability without custom hardware kernels. Timing experiments compare curve evaluation against NumPy and SciPy and KAN training against EfficientKAN across a range of problem sizes. The results illustrate where this generality remains computationally practical and where overhead is substantial. Library is available on GitHub at https://github.com/alexshtf/torchcurves.

## Software Project Rescue: When to Stabilize, Refactor, or Rebuild

DevFeed: [Software Project Rescue: When to Stabilize, Refactor, or Rebuild](<https://devfeed.tech/articles/software-project-rescue-when-to-stabilize-refactor-or-rebuild-127132.md>)

Original publisher: [Read original article](<https://hackernoon.com/software-project-rescue-when-to-stabilize-refactor-or-rebuild?source=rss>)

Author: Mariia Popovych

Published: 2026-11-10T16:23:59Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Software](<https://devfeed.tech/topics/software.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Software Process](<https://devfeed.tech/topics/software-process.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-avatar](<https://devfeed.tech/tags/ai-avatar.md>), [ai-code](<https://devfeed.tech/tags/ai-code.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [ai-content](<https://devfeed.tech/tags/ai-content.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [booking](<https://devfeed.tech/tags/booking.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [build](<https://devfeed.tech/tags/build.md>), [business](<https://devfeed.tech/tags/business.md>), [failure-in-software](<https://devfeed.tech/tags/failure-in-software.md>), [legacy-codebase-stabilization](<https://devfeed.tech/tags/legacy-codebase-stabilization.md>), [product](<https://devfeed.tech/tags/product.md>), [project](<https://devfeed.tech/tags/project.md>), [rebuild](<https://devfeed.tech/tags/rebuild.md>), [refactor](<https://devfeed.tech/tags/refactor.md>), [software](<https://devfeed.tech/tags/software.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [software-product-recovery](<https://devfeed.tech/tags/software-product-recovery.md>), [software-project-rescue](<https://devfeed.tech/tags/software-project-rescue.md>), [software-refactor-vs-rebuild](<https://devfeed.tech/tags/software-refactor-vs-rebuild.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>), [technical-debt-management](<https://devfeed.tech/tags/technical-debt-management.md>)

### AI overview

Software rescue begins with an audit to identify what is stable, fragile, and blocking development, then prioritizes problems affecting users and revenue. Stabilization addresses specific fragile areas when the core architecture is sound; refactoring restructures code when coupling or misplaced logic makes changes risky; a rebuild is warranted when the technology or architecture cannot support requirements or maintenance costs exceed replacement. The article describes focused interventions for integrations, production booking flows, AI generated code, handovers, and releases. Improvements proceed incrementally, with a handover that explains changes and remaining risks. Its case example attributes unreliable video production across three AI services to missing orchestration between providers, which the team mapped and rebuilt.

### Source excerpt

Software rescue isn't a last resort for failed products. Here's what it actually covers - and how to tell if your product needs it before something breaks.

## Set your intended architecture with your coding agent, skip the diagram

DevFeed: [Set your intended architecture with your coding agent, skip the diagram](<https://devfeed.tech/articles/set-your-intended-architecture-with-your-coding-agent-skip-the-diagram-127367.md>)

Original publisher: [Read original article](<https://www.sonarsource.com/blog/set-your-intended-architecture-with-your-coding-agent/>)

Author: Robert Curlee

Published: 2026-11-10T14:00:00Z

Content type: article

Language: en

Sources: [Sonar Blog](<https://devfeed.tech/sources/sonar-blog.md>)

Topics: [clean-architecture](<https://devfeed.tech/topics/clean-architecture.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [architectural-drift](<https://devfeed.tech/tags/architectural-drift.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [maintainability](<https://devfeed.tech/tags/maintainability.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [rules](<https://devfeed.tech/tags/rules.md>), [sonarqube-cloud](<https://devfeed.tech/tags/sonarqube-cloud.md>), [web-apis](<https://devfeed.tech/tags/web-apis.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

SonarQube Cloud lets developers define component boundaries through conversational coding agents, which can analyze dependencies and propose structural rules to limit architectural drift. Violations are flagged as maintainability issues in existing pull request and triage workflows. Teams can scale standards across repositories using public Web APIs. The excerpt mentions setup via CLI or MCP Server but gives no setup steps.

### Source excerpt

Define your intended architecture with your coding agent in SonarQube Cloud and catch architectural drift early. Set it up with the CLI or MCP Server.

## The AI Discount Trap: Why Cheaper Software Development Can Cost You More

DevFeed: [The AI Discount Trap: Why Cheaper Software Development Can Cost You More](<https://devfeed.tech/articles/the-ai-discount-trap-why-cheaper-software-development-can-cost-you-more-121023.md>)

Original publisher: [Read original article](<https://hackernoon.com/the-ai-discount-trap-why-cheaper-software-development-can-cost-you-more?source=rss>)

Author: Alexander Lipanov

Published: 2026-11-06T08:02:12Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [agencies](<https://devfeed.tech/tags/agencies.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [ai-development-risks](<https://devfeed.tech/tags/ai-development-risks.md>), [ai-engineering](<https://devfeed.tech/tags/ai-engineering.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-in-software-development](<https://devfeed.tech/tags/ai-in-software-development.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [ai-native-engineering](<https://devfeed.tech/tags/ai-native-engineering.md>), [ai-software-development](<https://devfeed.tech/tags/ai-software-development.md>), [code](<https://devfeed.tech/tags/code.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [development](<https://devfeed.tech/tags/development.md>), [discount](<https://devfeed.tech/tags/discount.md>), [generation](<https://devfeed.tech/tags/generation.md>), [software](<https://devfeed.tech/tags/software.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [software-delivery-speed](<https://devfeed.tech/tags/software-delivery-speed.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [speed](<https://devfeed.tech/tags/speed.md>), [tech](<https://devfeed.tech/tags/tech.md>), [tech-debt](<https://devfeed.tech/tags/tech-debt.md>), [verification](<https://devfeed.tech/tags/verification.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>)

### AI overview

AI reduces the example team's coding time from 14 to 10 hours per feature, but testing and code review remain six hours, so monthly output rises from 50 to 62 features within the same 1,000-hour budget. The article argues that the added verification load makes discounts risky if they are achieved by cutting review: unverified features may accumulate and later require costly re-engineering. It recommends asking vendors how they verify generated code before production, scale review, explain architectural decisions, and maintain the codebase over time. It favors judging engineering by outcomes and accountable quality rather than hours alone.

### Source excerpt

Why high-speed code generation increases tech debt. An architectural perspective on software delivery without proper verification by Alexander Lipanov, PhD.

## Cognitive Tours: Making Understanding a Deliverable in AI-Assisted Development

DevFeed: [Cognitive Tours: Making Understanding a Deliverable in AI-Assisted Development](<https://devfeed.tech/articles/cognitive-tours-making-understanding-a-deliverable-in-ai-assisted-development-120838.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.08456>)

Author: Margaret-Anne Storey

Published: 2026-11-06T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Developer Enablement](<https://devfeed.tech/topics/developer-enablement.md>), [human computer interaction](<https://devfeed.tech/topics/human-computer-interaction.md>), [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-coding](<https://devfeed.tech/tags/agentic-coding.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [audit](<https://devfeed.tech/tags/audit.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [cognitive-debt](<https://devfeed.tech/tags/cognitive-debt.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [design](<https://devfeed.tech/tags/design.md>), [development](<https://devfeed.tech/tags/development.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [open-questions](<https://devfeed.tech/tags/open-questions.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [skills](<https://devfeed.tech/tags/skills.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>), [tests](<https://devfeed.tech/tags/tests.md>), [web-based](<https://devfeed.tech/tags/web-based.md>)

### AI overview

Cognitive Tours is a web-based prototype intended to address cognitive debt--the loss of shared understanding of a system--and intent debt--the lack of documented goals, constraints, and rationale. It lets teams create and follow curated paths linking user needs, design decisions, code, tests, and open questions. AI-assisted skills audit existing waypoints and tours for possible problems or staleness and suggest new candidates; people decide what matters, verify connections, and shape the narrative. The authors intend this human sensemaking to help build and share understanding. The paper demonstrates the tool through a tour of itself and proposes an evaluation agenda; the supplied abstract does not report evaluation results.

### Source excerpt

arXiv:2611.08456v1 Announce Type: new Abstract: Generative AI and agentic coding are accelerating software development, leading to concerns about technical debt. But two less visible forms of debt, cognitive debt and intent debt, are emerging as key risks to software health. Cognitive debt is the absence or erosion of a team's shared understanding where no one can confidently explain how a system works or predict the impact of a change. Intent debt is the lack of clearly articulated goals, constraints, and rationale that explain what the system is for and guide how it should evolve. This paper presents Cognitive Tours, a tool designed to mitigate and repair cognitive and intent debt. Cognitive Tours is a web-based prototype for creating and following curated paths connecting user needs, design decisions, code, tests, and open questions. AI-assisted skills help audit existing waypoints and tours for possible problems or staleness and suggest candidates for new ones; humans decide what matters, verify relationships, and construct the narrative. This division of work deliberately preserves productive friction: the sensemaking involved in selecting, explaining, and revising a tour, which is intended to foster and share understanding. Our demonstration uses a tour of Cognitive Tours itself to introduce the tool and illustrate its design decisions and interaction mechanisms. A proposed evaluation agenda concludes the paper. A demo is available at https://cognitive-tours-demo.vercel.app/

## The Strange Future of AI-Written Software: Do Companies Really Own Their Code?

DevFeed: [The Strange Future of AI-Written Software: Do Companies Really Own Their Code?](<https://devfeed.tech/articles/the-strange-future-of-ai-written-software-do-companies-really-own-their-code-118807.md>)

Original publisher: [Read original article](<https://hackernoon.com/the-strange-future-of-ai-written-software-do-companies-really-own-their-code?source=rss>)

Author: Sasha Apartsin

Published: 2026-11-05T06:30:06Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [Code quality](<https://devfeed.tech/topics/code-quality.md>), [Code Health](<https://devfeed.tech/topics/code-health.md>), [code analysis](<https://devfeed.tech/topics/code-analysis.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [acceleration](<https://devfeed.tech/tags/acceleration.md>), [acquisitions](<https://devfeed.tech/tags/acquisitions.md>), [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistance](<https://devfeed.tech/tags/ai-assistance.md>), [ai-engineering-management](<https://devfeed.tech/tags/ai-engineering-management.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-generated-software](<https://devfeed.tech/tags/ai-generated-software.md>), [ai-stack](<https://devfeed.tech/tags/ai-stack.md>), [all](<https://devfeed.tech/tags/all.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [also](<https://devfeed.tech/tags/also.md>), [alter](<https://devfeed.tech/tags/alter.md>), [api](<https://devfeed.tech/tags/api.md>), [applications](<https://devfeed.tech/tags/applications.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [code](<https://devfeed.tech/tags/code.md>), [future](<https://devfeed.tech/tags/future.md>), [future-of-ai](<https://devfeed.tech/tags/future-of-ai.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [software-maintainability](<https://devfeed.tech/tags/software-maintainability.md>), [software-maintenance](<https://devfeed.tech/tags/software-maintenance.md>), [system](<https://devfeed.tech/tags/system.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>)

### AI overview

AI-written software may remain operational while becoming harder for companies to understand and maintain without the models and tools that helped create it. The text calls this cognitive lock-in: repository ownership may not ensure that a company can safely evolve its systems if its AI layer changes, becomes costly, or disappears. It argues that firms should plan for AI continuity by preserving human understanding, validation, traceability, and fallback workflows. It also proposes distinguishing systems that must remain human-recoverable--such as regulated or safety-sensitive systems--from lower-risk applications that can be more AI-dependent. The same concern could affect technical debt, engineering management, acquisitions, and software valuation, as maintainability may depend on the portability of the system's interpretive tooling as well as code quality.

### Source excerpt

Companies may soon discover that owning the code is no longer equivalent to owning the system.

## The Dangers of Non-Self-Fixed Architecture Technical Debt and Its Impact on Time-to-Fix

DevFeed: [The Dangers of Non-Self-Fixed Architecture Technical Debt and Its Impact on Time-to-Fix](<https://devfeed.tech/articles/the-dangers-of-non-self-fixed-architecture-technical-debt-and-its-impact-on-time-to-fix-118034.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2605.16133>)

Author: Edi Sutoyo, Paris Avgeriou, Andrea Capiluppi

Published: 2026-11-05T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [developer-roles](<https://devfeed.tech/tags/developer-roles.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [survival-analysis](<https://devfeed.tech/tags/survival-analysis.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

The study finds that architectural technical debt (ATD) repaid by someone other than its introducer can remain unresolved longer when changes to affected files are spread across many developers. In large Apache open-source projects, the authors traced Jira artifacts to version-control history to identify ATD introduction, repayment, and developer roles, then compared repayment dynamics using descriptive statistics, non-parametric tests, and survival analysis. They report distinct repayment dynamics and differences in how changes are shared between self-fixed and non-self-fixed ATD. The abstract recommends identifying potentially high-risk items, involving the introducer in repayment when feasible, and documenting design rationale to support knowledge transfer.

### Source excerpt

arXiv:2605.16133v2 Announce Type: replace Abstract: Technical Debt (TD) refers to the long-term costs incurred when developers prioritize short-term delivery over quality-improving work. Architectural Technical Debt (ATD) arises when architectural decisions (e.g., technology choices, patterns, or decomposition) prioritize near-term progress over future maintainability and evolvability. Because ATD affects a system's core structure and propagates through architectural dependencies, it is often more expensive and disruptive to remediate than localized code-level debt. Although ATD has been widely studied, an important but underexplored aspect of repayment is who performs it. Prior work provides limited empirical evidence on repayment responsibility in ATD and its relationship to time-to-fix. We empirically study self-fixed ATD, where the introducer also repays the debt, and contrast it with non--self-fixed ATD in large Apache open-source projects. We reconstruct ATD lifecycles by tracing Jira artifacts to version-control history to identify introduction and repayment points and attribute developer roles. We address three research questions on the prevalence of self-fixed ATD, time-to-fix differences between self-fixed and non--self-fixed items, and how factors related to code change and collaboration metrics relate to repayment speed. Using descriptive statistics, non-parametric tests, and survival analysis, we show that self-fixed and non--self-fixed ATD exhibit distinct repayment dynamics and differences in how changes are shared on ATD-affected files. In particular, non--self-fixed ATD is more likely to remain unresolved longer when changes are spread across many developers. These results provide actionable guidance for maintainers to identify potentially high-risk ATD items and support knowledge transfer by maintaining introducer involvement when feasible and documenting the design rationale during repayment.

## The harness is a product

DevFeed: [The harness is a product](<https://devfeed.tech/articles/the-harness-is-a-product-116274.md>)

Original publisher: [Read original article](<https://www.thoughtworks.com/insights/blog/generative-ai/harness-is-a-product>)

Author: Cecilia Geraldo

Published: 2026-11-04T00:00:00Z

Content type: opinion

Language: en

Sources: [Thoughtworks Insights](<https://devfeed.tech/sources/thoughtworks-insights.md>)

Topics: [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>), [product mindset](<https://devfeed.tech/topics/product-mindset.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [acceptance](<https://devfeed.tech/tags/acceptance.md>), [acceptance-rate](<https://devfeed.tech/tags/acceptance-rate.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-harness](<https://devfeed.tech/tags/agent-harness.md>), [agent-sandboxing](<https://devfeed.tech/tags/agent-sandboxing.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-engineering](<https://devfeed.tech/tags/agentic-engineering.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [all](<https://devfeed.tech/tags/all.md>), [harness](<https://devfeed.tech/tags/harness.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

An agent harness is the layer between a model and its work: instructions, tools, permissions, context, state, orchestration, evaluation and telemetry. The article argues that as these parts become reusable and depend on versioned plugins, teams should manage the harness as a product, with a named owner, roadmap, dependencies and quality gates. It recommends task-based evaluations drawn from real work, versioned alongside the harness and run on meaningful changes; track cost and latency and use human review where automated scoring falls short. For self-improvement, require evaluation, provenance and rollback, automating proposals while retaining human approval. At enterprise scale, platform teams need to provide auditable access controls, sandboxing, plugin allow-lists, routing and spend policies, version-specific telemetry, deprecation support and clear agent identity and permissions. If the supported harness is slower or less capable than ad hoc alternatives, teams may route around it, creating shadow IT and security risks.

### Source excerpt

The harness is a product

## What an AI-Native Product Team Actually Looks Like at Salesforce

DevFeed: [What an AI-Native Product Team Actually Looks Like at Salesforce](<https://devfeed.tech/articles/what-an-ai-native-product-team-actually-looks-like-at-salesforce-117676.md>)

Original publisher: [Read original article](<https://www.news.aakashg.com/p/salesforce-ai-native-product-team>)

Author: Aakash Gupta

Published: 2026-11-03T23:44:37Z

Content type: article

Language: en

Sources: [Product Growth](<https://devfeed.tech/sources/product-growth.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [AI-enhanced product development](<https://devfeed.tech/topics/ai-enhanced-product-development.md>), [product mindset](<https://devfeed.tech/topics/product-mindset.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [roadmaps](<https://devfeed.tech/topics/roadmaps.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [adlc](<https://devfeed.tech/tags/adlc.md>), [advice](<https://devfeed.tech/tags/advice.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-tasks](<https://devfeed.tech/tags/agentic-tasks.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-engineering](<https://devfeed.tech/tags/ai-engineering.md>), [ai-evals](<https://devfeed.tech/tags/ai-evals.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [hiring](<https://devfeed.tech/tags/hiring.md>), [like](<https://devfeed.tech/tags/like.md>), [native](<https://devfeed.tech/tags/native.md>), [org](<https://devfeed.tech/tags/org.md>), [product](<https://devfeed.tech/tags/product.md>), [salesforce](<https://devfeed.tech/tags/salesforce.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Salesforce AI leader Jayesh Govindarajan describes an Agent Development Lifecycle (ADLC) built around continual observation, building, testing, evaluation, and deployment. Agents need repeated adjustment as models and source context change; the excerpt's refund-policy example shows how an outdated agent can produce incorrect refunds. Because AI features require ongoing maintenance, teams should plan for evaluation and observability, and define domain-specific evals before trusting an agent.

For Salesforce's AI-native product teams, the described practices include letting teams choose among tools such as Codex, Claude Code, and Cursor; using Slack to route customer and field feedback into the roadmap; and using Agent Script to make selected outputs deterministic where inconsistent answers would be unacceptable. The account recommends proving value in a pilot before expanding the approach. For PM hiring, it emphasizes agency, an agent-native mindset, skepticism, craftsmanship, and the ability to define quality; AI prototyping and evaluation skills are also described as important.

### Source excerpt

Salesforce AI's Jayesh Govindarajan, who runs the Agentforce org, on the ADLC behind an AI-native product team and what Salesforce looks for when hiring PMs.

## Cognitive Debt in the GenAI Era - Listening to Practitioners' Voices on the Loss of Understanding

DevFeed: [Cognitive Debt in the GenAI Era - Listening to Practitioners' Voices on the Loss of Understanding](<https://devfeed.tech/articles/cognitive-debt-in-the-genai-era-listening-to-practitioners-voices-on-the-loss-of-understanding-107365.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.37888>)

Author: Theocharis Tavantzis, Bianca Trinkenreich, Michaela Greiler, J\\'ulia Cond\\'e Ara\\'ujo, Marina Cond\\'e Ara\\'ujo, Italo Santos, Alexander Serebrenik, Margaret-Anne Storey, Maria Teresa Baldassarre

Published: 2026-10-30T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [knowledge-management](<https://devfeed.tech/topics/knowledge-management.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [cognitive-debt](<https://devfeed.tech/tags/cognitive-debt.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [genai](<https://devfeed.tech/tags/genai.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [knowledge-sharing](<https://devfeed.tech/tags/knowledge-sharing.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [practices](<https://devfeed.tech/tags/practices.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [research](<https://devfeed.tech/tags/research.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [team](<https://devfeed.tech/tags/team.md>), [tests](<https://devfeed.tech/tags/tests.md>), [understand](<https://devfeed.tech/tags/understand.md>)

### AI overview

A grey literature review of 76 sources finds that cognitive debt--the gap between how a software system works and what its developers understand--can build up unnoticed even when code works and tests pass. Practitioners associate it especially with accepting AI-generated solutions without developing understanding, and report harder maintenance and debugging, fragmented team knowledge, and lower productivity. Suggested responses include recording design rationale, keeping changes small enough to review, adding comprehension gates, and holding knowledge-sharing rituals; reliability metrics are cited as a possible detection signal. The review emphasizes preserving human understanding alongside faster code production.

### Source excerpt

arXiv:2610.37888v1 Announce Type: new Abstract: Fast-paced AI-assisted software development risks reducing developers' understanding of the systems they build. This growing gap between what the system does and what developers understand about it, described as ``cognitive debt'', is not new, but AI has exacerbated it. This has led to a recent surge in blog posts and online discussions, in which practitioners recognize and write about cognitive debt, and share their experiences well before academic studies can capture them. To understand their concerns and inform future research and practice, we conduct a grey literature review of 76 sources, focusing on how cognitive debt is conceptualized and manifests, its contributing factors, its consequences, and the practices to prevent, detect, and mitigate it. We find that cognitive debt can accumulate unnoticed behind working code and passing tests, particularly when developers accept AI-generated solutions without building understanding. Practitioners report consequences such as harder maintenance and debugging, fragmented knowledge in the team, and reduced productivity. They propose practices such as documenting design rationale, review-sized changes, comprehension gates, and knowledge-sharing rituals, along with signals like reliability metrics to detect it. Our findings give software teams a structured view of emerging practical approaches in AI-assisted development and stress the need to preserve human understanding alongside faster code production.

## Overgrowth in your product garden? Send in the goats

DevFeed: [Overgrowth in your product garden? Send in the goats](<https://devfeed.tech/articles/overgrowth-in-your-product-garden-send-in-the-goats-104612.md>)

Original publisher: [Read original article](<https://hackernoon.com/overgrowth-in-your-product-garden-send-in-the-goats?source=rss>)

Author: Learnosity

Published: 2026-10-28T12:10:25Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Product Management](<https://devfeed.tech/topics/product-management.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [product mindset](<https://devfeed.tech/topics/product-mindset.md>), [roadmaps](<https://devfeed.tech/topics/roadmaps.md>), [API as a Product](<https://devfeed.tech/topics/api-as-a-product.md>)

Tags: [2-2](<https://devfeed.tech/tags/2-2.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [admin](<https://devfeed.tech/tags/admin.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [browser](<https://devfeed.tech/tags/browser.md>), [build](<https://devfeed.tech/tags/build.md>), [build-vs-buy](<https://devfeed.tech/tags/build-vs-buy.md>), [building](<https://devfeed.tech/tags/building.md>), [code](<https://devfeed.tech/tags/code.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [core](<https://devfeed.tech/tags/core.md>), [costs](<https://devfeed.tech/tags/costs.md>), [edtech](<https://devfeed.tech/tags/edtech.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [overgrowth-in-product](<https://devfeed.tech/tags/overgrowth-in-product.md>), [product](<https://devfeed.tech/tags/product.md>), [scale](<https://devfeed.tech/tags/scale.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

### AI overview

The author argues that in-house builds of non-core products often take far longer than planned and divert engineering effort into maintenance. Her team spent three months building authentication before adopting a specialist vendor. In edtech assessment, changing accessibility requirements--such as offering drag, click, and keyboard interaction for every drag-and-drop question--can turn a short task into months of work; scaling also demands reliability across exam loads, weak Wi-Fi, devices, and browsers. AI can speed code production but does not remove the need for skilled review, QA, and production maintenance. She suggests weighing realistic build and at-scale maintenance costs, considering bespoke needs, and building differentiation on a proven base where possible.

### Source excerpt

Building non-core software in-house? A VP of Product on the hidden costs of build vs buy, from accessibility to scale and AI.

## RIPE 93 Daily Meeting Blog

DevFeed: [RIPE 93 Daily Meeting Blog](<https://devfeed.tech/articles/ripe-93-daily-meeting-blog-101174.md>)

Original publisher: [Read original article](<https://labs.ripe.net/author/ripe-ncc-commsies/ripe-93-daily-meeting-blog/>)

Author: RIPE NCC Communications

Published: 2026-10-26T20:51:23Z

Content type: news

Language: en

Sources: [RIPE Labs](<https://devfeed.tech/sources/ripe-labs.md>)

Topics: [Internet Trends](<https://devfeed.tech/topics/internet-trends.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent-applications](<https://devfeed.tech/tags/ai-agent-applications.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [asics](<https://devfeed.tech/tags/asics.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [cern](<https://devfeed.tech/tags/cern.md>), [collectors](<https://devfeed.tech/tags/collectors.md>), [community](<https://devfeed.tech/tags/community.md>), [daily](<https://devfeed.tech/tags/daily.md>), [demo](<https://devfeed.tech/tags/demo.md>), [dns](<https://devfeed.tech/tags/dns.md>), [docker](<https://devfeed.tech/tags/docker.md>), [events](<https://devfeed.tech/tags/events.md>), [recordings](<https://devfeed.tech/tags/recordings.md>), [ripe](<https://devfeed.tech/tags/ripe.md>), [slides](<https://devfeed.tech/tags/slides.md>)

### AI overview

RIPE 93's first day in Sofia covered practical IPv6 testing, routing measurements, and operational questions. NIC.br demonstrated v6bench, an open-source Docker-based tool for testing application behavior in IPv4-only, dual-stack, and IPv6-only environments, including NAT64. Research on CERN data paths found high packet loss on UK corridors and called for NOCs and NRENs to share incident records. The RIPE NCC's RISwhois gained its first test suite and can now update data hourly rather than every eight hours; its collectors aim to show BGP topology while keeping archive size manageable. Researchers also reported unexpected TTL rewrites that can obscure traceroute paths, with causes still uncertain. Discussions of Layer 3 Internet exchanges were cautious, raising concerns that they could shift operational complexity and control away from participants. The excerpt also summarizes IETF topics including AI, post-quantum cryptography, IPv6, DNS, and space networking.

### Source excerpt

RIPE 93 has kicked off in wonderful ancient Sofia. As always, you can view the slides, you can watch the recordings, but if you want to get to the bottom of what's really going on, read this daily meeting blog!

## The Influence of Code Smells in Efferent Neighbors on Class Stability

DevFeed: [The Influence of Code Smells in Efferent Neighbors on Class Stability](<https://devfeed.tech/articles/the-influence-of-code-smells-in-efferent-neighbors-on-class-stability-100332.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2602.12950>)

Author: Zushuai Zhang, Elliott Wen, Ewan Tempero

Published: 2026-10-26T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Code Health](<https://devfeed.tech/topics/code-health.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>)

Tags: [class](<https://devfeed.tech/tags/class.md>), [code-smells](<https://devfeed.tech/tags/code-smells.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [java](<https://devfeed.tech/tags/java.md>), [maintainability](<https://devfeed.tech/tags/maintainability.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [ripple](<https://devfeed.tech/tags/ripple.md>), [risk](<https://devfeed.tech/tags/risk.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [study](<https://devfeed.tech/tags/study.md>)

### AI overview

The study finds that class stability risk can be missed when code smells are assessed only within the class being maintained. Using one year of commit history from 152 highly starred GitHub Java projects, the researchers detected smells and static dependencies and modeled their associations with class stability. Smells in a class's efferent neighbors--classes it depends on--revealed risks not seen from the class's own smells, while analyzing smells at both locations together and their dependency relationships revealed additional risks. The findings suggest extending smell analysis to a class's dependencies; the abstract reports associations and does not establish causation.

### Source excerpt

arXiv:2602.12950v3 Announce Type: replace Abstract: Understanding what drives code instability is essential for effective software maintenance, as unstable classes require larger or more frequent edits and increase the risk of unintended side effects. Although code smells are widely believed to harm maintainability, most prior stability studies examine only the smells within the class being modified. In practice, however, a class can change because its efferent neighbors (i.e., the classes it depends on) are modified due to ripple effects that propagate along static dependencies, even if the class itself is clean. Such ripple effects may be more severe when efferent neighbors exhibit code smells. Therefore, this study investigates whether code smells in a class's efferent neighbors affect its stability. We mined one year of commit history from 152 top-starred GitHub Java projects, detected code smells and static dependencies, and modeled their associations with class stability. Our results challenge the practice of examining code smells only within the class being maintained by showing that this provides an incomplete view of stability risk. Specifically, considering code smells in efferent neighbors reveals stability risks that are not observed when examining code smells in the class itself. Moreover, considering smells in both the class and its efferent neighbors, as well as their relationships across dependencies, reveals further stability risks that are not observed when smells at these two locations are analyzed separately. Consequently, these findings suggest that code smell analysis for class maintenance should extend beyond the class being maintained to the classes on which it depends.

## Introducing the Temporal Product Edition -- October 2026

DevFeed: [Introducing the Temporal Product Edition -- October 2026](<https://devfeed.tech/articles/introducing-the-temporal-product-edition-october-2026-100724.md>)

Original publisher: [Read original article](<https://temporal.io/blog/october-2026-temporal-product-edition>)

Author: Hien Phan

Published: 2026-10-26T00:00:00Z

Content type: release

Language: en

Sources: [Temporal](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [Resilience](<https://devfeed.tech/topics/resilience.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agents](<https://devfeed.tech/tags/agents.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [applications](<https://devfeed.tech/tags/applications.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [build](<https://devfeed.tech/tags/build.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cloud-run](<https://devfeed.tech/tags/cloud-run.md>), [labs](<https://devfeed.tech/tags/labs.md>), [launches](<https://devfeed.tech/tags/launches.md>), [nexus](<https://devfeed.tech/tags/nexus.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [product](<https://devfeed.tech/tags/product.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [temporal](<https://devfeed.tech/tags/temporal.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

Temporal's first Product Edition previews five launches aimed at making mission-critical applications and agents easier to build and operate. Standalone Nexus Operations lets apps and agents call reusable Nexus services through the Temporal SDK, with durable handling of failures and waits. Temporal Proxy centralizes encryption using customers' keys in their own environment, keeping protected values unreadable to Temporal Cloud. Serverless Workers run code on AWS Lambda or Google Cloud Run with demand-following capacity while Temporal tracks progress and retries; Amazon Bedrock AgentCore Runtime is listed as pre-release. Production controls help teams inspect work, investigate repeated failures, pause executions, and adjust retries and timeouts for pending steps; the post also covers moving workloads to Temporal Cloud. Temporal Labs offers early open source experiments and direct feedback opportunities, but projects may change or lose investment and are not supported product commitments.

### Source excerpt

Temporal's first Product Edition delivers five launches in five days, from Nexus and Proxy to Serverless Workers and Labs, for durable apps and agents.

## PHP's security scramble is just a preview: AI is digging up flaws faster than maintainers can fix them

DevFeed: [PHP's security scramble is just a preview: AI is digging up flaws faster than maintainers can fix them](<https://devfeed.tech/articles/php-s-security-scramble-is-just-a-preview-ai-is-digging-up-flaws-faster-than-maintainers-can-fix-them-95868.md>)

Original publisher: [Read original article](<https://thenewstack.io/php2shell-ai-vulnerabilities-maintainers/>)

Author: Paul Sawers

Published: 2026-10-22T14:35:13Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [Security research](<https://devfeed.tech/topics/security-research.md>), [Security](<https://devfeed.tech/topics/security.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [PHP](<https://devfeed.tech/topics/php.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [can](<https://devfeed.tech/tags/can.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [faster](<https://devfeed.tech/tags/faster.md>), [first](<https://devfeed.tech/tags/first.md>), [government](<https://devfeed.tech/tags/government.md>), [hit](<https://devfeed.tech/tags/hit.md>), [hospitals](<https://devfeed.tech/tags/hospitals.md>), [just](<https://devfeed.tech/tags/just.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [php](<https://devfeed.tech/tags/php.md>), [post](<https://devfeed.tech/tags/post.md>), [preview](<https://devfeed.tech/tags/preview.md>), [prompting](<https://devfeed.tech/tags/prompting.md>), [security](<https://devfeed.tech/tags/security.md>), [stack](<https://devfeed.tech/tags/stack.md>), [the-web](<https://devfeed.tech/tags/the-web.md>), [up](<https://devfeed.tech/tags/up.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

PHP2Shell exposed two critical PHP vulnerabilities that could let unauthenticated attackers execute code on affected servers. PHP issued emergency fixes for versions 8.2-8.5, with limited legacy patches for 7.4-8.1; Cloudflare added firewall protections, Automattic secured hosted sites, and Wikimedia took some services offline pending patches. The coordinated disclosure was disrupted when Chainguard released patched container images hours early, prompting disagreement over whether the release helped defenders or exposed systems before vendors were ready. The article describes a broader strain: AI is producing more vulnerability findings and reports, while triage and reliable fixes still require experienced maintainers. Smaller projects often lack the resources for emergency coalitions, and fixes can involve compatibility and performance trade-offs. Responses discussed include vulnerability planning, shared engineering support, improved report triage, easier backports and releases, and shorter embargoes at Valkey.

### Source excerpt

One of the biggest security scares to hit the web is causing widespread disruption, prompting businesses, hospitals, schools, and government The post PHP's security scramble is just a preview: AI is digging up flaws faster than maintainers can fix them appeared first on The New Stack.

## Your RAG System Can Be Healthy and Still Be Wrong

DevFeed: [Your RAG System Can Be Healthy and Still Be Wrong](<https://devfeed.tech/articles/your-rag-system-can-be-healthy-and-still-be-wrong-86506.md>)

Original publisher: [Read original article](<https://hackernoon.com/your-rag-system-can-be-healthy-and-still-be-wrong?source=rss>)

Author: Atul Kumar

Published: 2026-10-13T16:47:09Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [mutation-testing](<https://devfeed.tech/topics/mutation-testing.md>)

Tags: [ai-application-testing](<https://devfeed.tech/tags/ai-application-testing.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [mlops](<https://devfeed.tech/tags/mlops.md>), [production-ai-reliability](<https://devfeed.tech/tags/production-ai-reliability.md>), [rag](<https://devfeed.tech/tags/rag.md>), [rag-architecture](<https://devfeed.tech/tags/rag-architecture.md>), [rag-observability](<https://devfeed.tech/tags/rag-observability.md>), [rag-pipeline-reliability](<https://devfeed.tech/tags/rag-pipeline-reliability.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [stale-context-detection](<https://devfeed.tech/tags/stale-context-detection.md>), [tests](<https://devfeed.tech/tags/tests.md>), [validation](<https://devfeed.tech/tags/validation.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

This tutorial demonstrates how stale documents in a retrieval-augmented generation (RAG) pipeline can produce incorrect AI answers even when requests succeed. It presents a version freshness check that rejects documents that do not match the authoritative source, explains failure handling and consistency tradeoffs, and recommends tests and observability to validate the approach. It does not report measured production results.

### Source excerpt

Learn how stale RAG context causes incorrect AI answers and how document version checks, automated tests, and freshness validation improve reliability.

## The AI control gap: Who gets to say 'It's safe'?

DevFeed: [The AI control gap: Who gets to say 'It's safe'?](<https://devfeed.tech/articles/the-ai-control-gap-who-gets-to-say-it-s-safe-84510.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/10/10/the-ai-control-gap-who-gets-to-say-its-safe/>)

Author: Dave Vellante

Published: 2026-10-10T16:54:10Z

Content type: opinion

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-in-production](<https://devfeed.tech/tags/agents-in-production.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-sprawl](<https://devfeed.tech/tags/ai-agent-sprawl.md>), [ai-alignment](<https://devfeed.tech/tags/ai-alignment.md>), [ai-auditing](<https://devfeed.tech/tags/ai-auditing.md>), [ai-control-gap](<https://devfeed.tech/tags/ai-control-gap.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-regulation](<https://devfeed.tech/tags/ai-regulation.md>), [ai-safety](<https://devfeed.tech/tags/ai-safety.md>), [ai-trust](<https://devfeed.tech/tags/ai-trust.md>), [appian](<https://devfeed.tech/tags/appian.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [bounded-autonomy](<https://devfeed.tech/tags/bounded-autonomy.md>), [breaking-analysis](<https://devfeed.tech/tags/breaking-analysis.md>), [china-ai-competition](<https://devfeed.tech/tags/china-ai-competition.md>), [david-vellante](<https://devfeed.tech/tags/david-vellante.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [homepage-wikibon](<https://devfeed.tech/tags/homepage-wikibon.md>), [human-in-the-loop](<https://devfeed.tech/tags/human-in-the-loop.md>), [independent-oversight](<https://devfeed.tech/tags/independent-oversight.md>), [matt-calkins](<https://devfeed.tech/tags/matt-calkins.md>), [news](<https://devfeed.tech/tags/news.md>), [privileged-access-management-pam](<https://devfeed.tech/tags/privileged-access-management-pam.md>), [public-policy](<https://devfeed.tech/tags/public-policy.md>), [qualitate](<https://devfeed.tech/tags/qualitate.md>), [stealth-ai](<https://devfeed.tech/tags/stealth-ai.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [thecube-research](<https://devfeed.tech/tags/thecube-research.md>), [top-story-1](<https://devfeed.tech/tags/top-story-1.md>), [wikibon](<https://devfeed.tech/tags/wikibon.md>)

### AI overview

The article argues that AI systems should earn greater authority through evidence that their controls work in real deployment settings. It calls for independent experts to assess safety evidence and an accountable public authority to enforce standards, including corrective action for high-risk systems. For enterprises, it recommends human approval of high-risk agent actions, bounded permissions, monitoring, and clear ownership. A survey of 25 customers found that all 19 respondents with agents in production required human approval for high-risk actions.

### Source excerpt

We see a control gap between what artificial intelligence can do and what the evidence supports trusting it to do. A great demo doesn't prove that a system will stay within the limits of an intended deployment's goals. The question is: Who gets to decide when the evidence is sufficient to declare AI is safe? [...] The post The AI control gap: Who gets to say 'It's safe'? appeared first on SiliconANGLE.

## OpenAI GPT-6 Sol: An evaluation

DevFeed: [OpenAI GPT-6 Sol: An evaluation](<https://devfeed.tech/articles/openai-gpt-6-sol-an-evaluation-59613.md>)

Original publisher: [Read original article](<https://www.sonarsource.com/blog/open-ai-gpt-6-sol-evaluation/>)

Author: Prasenjit Sarkar

Published: 2026-09-24T13:00:00Z

Content type: article

Language: en

Sources: [Sonar Blog](<https://devfeed.tech/sources/sonar-blog.md>)

Topics: [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Code](<https://devfeed.tech/topics/code.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>), [Security](<https://devfeed.tech/topics/security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [gpt-6-astra](<https://devfeed.tech/topics/gpt-6-astra.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [gpt](<https://devfeed.tech/tags/gpt.md>), [gpt-6](<https://devfeed.tech/tags/gpt-6.md>), [gpt-6-sol](<https://devfeed.tech/tags/gpt-6-sol.md>), [humaneval](<https://devfeed.tech/tags/humaneval.md>), [maintainability](<https://devfeed.tech/tags/maintainability.md>), [mbpp](<https://devfeed.tech/tags/mbpp.md>), [openai](<https://devfeed.tech/tags/openai.md>), [openai-gpt-6-sol](<https://devfeed.tech/tags/openai-gpt-6-sol.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability-density](<https://devfeed.tech/tags/vulnerability-density.md>)

### AI overview

An evaluation compares GPT-6 Sol with GPT-6 Astra on HumanEval and MBPP tasks, code volume, correctness, maintainability findings, and security. Sol passed 83.09% of the 544 tasks, generated 26.9% less code, and produced 21.8% fewer total findings, but vulnerabilities increased in count and density.

### Source excerpt

GPT-6 Sol writes 27% less code than GPT-6 Astra and produces 22% fewer findings in total. See the full evaluation of correctness, security and maintainability.

## Code Quality Q&A With the JetBrains Qodana Team

DevFeed: [Code Quality Q&A With the JetBrains Qodana Team](<https://devfeed.tech/articles/code-quality-q-a-with-the-jetbrains-qodana-team-58128.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/qodana/2026/09/code-quality-q-a/>)

Author: Kerry Beetge

Published: 2026-09-22T13:16:19Z

Content type: article

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>)

Topics: [Code quality](<https://devfeed.tech/topics/code-quality.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>), [mutation-testing](<https://devfeed.tech/topics/mutation-testing.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [jetbrains](<https://devfeed.tech/topics/jetbrains.md>)

Tags: [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [code-quality](<https://devfeed.tech/tags/code-quality.md>), [cognitive-complexity](<https://devfeed.tech/tags/cognitive-complexity.md>), [coupling](<https://devfeed.tech/tags/coupling.md>), [mutation-testing](<https://devfeed.tech/tags/mutation-testing.md>), [quality](<https://devfeed.tech/tags/quality.md>), [serve](<https://devfeed.tech/tags/serve.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>), [testing](<https://devfeed.tech/tags/testing.md>), [unit-testing](<https://devfeed.tech/tags/unit-testing.md>)

### AI overview

A Q&A with the JetBrains Qodana team explains distinctions between technical debt and poor code quality, ways to reduce cognitive complexity, the relationship between code coverage and mutation testing, and the role of unit tests in maintaining code quality.

### Source excerpt

Code quality is shaped by countless decisions, from how developers manage complexity to how quickly they detect regressions. But common concepts such as technical debt, cognitive complexity and unit testing are not always clearly understood. In a new code quality Q&A session, we asked members of the Qodana team to answer some frequently searched questions [...]

## Claude Opus 5.5: An evaluation review and metrics benchmarks

DevFeed: [Claude Opus 5.5: An evaluation review and metrics benchmarks](<https://devfeed.tech/articles/claude-opus-5-5-an-evaluation-review-and-metrics-benchmarks-58304.md>)

Original publisher: [Read original article](<https://www.sonarsource.com/blog/claude-opus-5-5-an-evaluation/>)

Author: Prasenjit Sarkar

Published: 2026-09-22T13:00:00Z

Content type: article

Language: en

Sources: [Sonar Blog](<https://devfeed.tech/sources/sonar-blog.md>)

Topics: [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Code](<https://devfeed.tech/topics/code.md>), [bug](<https://devfeed.tech/topics/bug.md>), [Maintainability](<https://devfeed.tech/topics/maintainability.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-opus-5](<https://devfeed.tech/tags/claude-opus-5.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [maintainability](<https://devfeed.tech/tags/maintainability.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [review](<https://devfeed.tech/tags/review.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability-density](<https://devfeed.tech/tags/vulnerability-density.md>)

### AI overview

This evaluation compares Claude Opus 5.5 with Opus 5 on coding benchmarks and software quality metrics. Opus 5.5 achieved an 87.7% pass rate, produced less code with fewer tokens, and reduced total, code-smell, vulnerability, reliability, security, and maintainability findings. Bug and concurrency finding densities increased.

### Source excerpt

Explore Claude Opus 5.5 benchmarks covering coding accuracy, complexity, bugs, security vulnerabilities, maintainability and output efficiency.

[Next page](<https://devfeed.tech/topics/maintainability.md?cursor=WyIyMDI2LTA5LTIyVDEzOjAwOjAwKzAwOjAwIiwgIjliODRjODg4LTk1NTktNGU0Yi05OTE3LWZiOTM5YjIyMjFhMyJd>)