# Maintainability Published articles for Maintainability. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Human judgment doesn't leave the software factory. It relocates. DevFeed: [Human judgment doesn't leave the software factory. It relocates.]() Original publisher: [Read original article]() Author: Addy Osmani Published: 2026-08-21T00:00:00Z Content type: article Language: en Sources: [Addy Osmani]() Topics: [Software](), [coding](), [event driven](), [implementation](), [GitHub](), [Claude Code](), [codex]() Tags: [agent](), [architecture](), [automated](), [batch](), [build](), [claude-code](), [codex](), [event-driven](), [github](), [linear](), [maintainability](), [mutation-testing](), [pull-requests](), [quality](), [scanners](), [slack](), [software](), [testing](), [verification]() ### AI overview A field guide to building a repeatable software factory while keeping humans responsible for product intent, system design, quality standards, code review, and final merge decisions. It recommends early and continuous quality checks, deliberate constraints, and event-driven automation when ordinary coding workflows are no longer sufficient. ### Source excerpt A field guide to building a software factory that still has an owner. ## OpenTelemetry Demo 3.0 introduces breaking changes to attributes, dashboards, and local deployment DevFeed: [OpenTelemetry Demo 3.0 introduces breaking changes to attributes, dashboards, and local deployment]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-28T10:15:19Z Content type: opinion Language: en Sources: [Blog on OpenTelemetry]() Topics: [Demo](), [OpenTelemetry](), [Maintainability](), [dashboards](), [Kafka]() Tags: [changes](), [dashboards](), [demo](), [maintainability](), [opentelemetry](), [services]() ### AI overview This article explains intentional breaking changes in OpenTelemetry Demo 3.0, including renamed custom telemetry attributes, broken dashboards and queries, and a revised local-run configuration split across multiple files. The changes aim to improve maintainability and make forks easier to manage. ### Source excerpt If you've been running the Demo for some time, you may have seen a couple of structural changes lately, and you may even have gotten mad about things not working as expected. We feel your pain and we totally understand it. Unfortunately there was no better way to change things without breaking the existing flow. Some of what you knew is gone. New services were added. Attribute names have changed. If you had dashboards with custom metrics, everything is broken now. ## RPG Metrics: A Free-Beta Code Quality Scanner for IBM i RPG DevFeed: [RPG Metrics: A Free-Beta Code Quality Scanner for IBM i RPG]() Original publisher: [Read original article]() Author: Federico Tomassetti Published: 2026-07-15T09:22:39Z Content type: opinion Language: en Sources: [Federico Tomassetti]() Topics: [Code quality](), [Software](), [ibm]() Tags: [code-processing](), [code-quality](), [free](), [maintainability](), [platform](), [rpg]() ### AI overview This commentary reviews RPG Metrics, a code quality scanner from KDP Software for IBM i RPG source. The tool measures metrics including cyclomatic complexity and maintainability, identifies problematic files and refactoring points, and is free while in beta. The article compares it with enterprise-oriented static-analysis products. ### Source excerpt KDP Software has worked the IBM midrange platform since 1985. Their new RPG Metrics tool measures cyclomatic complexity, maintainability, and RPG Free convertibility across your RPG source. It is free during beta, it took me minutes to get a number out of it, and when I had questions the founder answered them himself. The post RPG Metrics -- The IBM i Tool the Big Vendors Wouldn't Sell You appeared first on Federico Tomassetti. ## Why Decision-Makers Adopt Kotlin Multiplatform DevFeed: [Why Decision-Makers Adopt Kotlin Multiplatform]() Original publisher: [Read original article]() Published: 2026-04-29T18:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [Maintainability](), [Developer experience](), [jetbrains]() Tags: [adoption](), [business-value](), [developer](), [jetbrains](), [kmp](), [kotlin](), [kotlin-multiplatform](), [maintainability]() ### AI overview The article explains that Kotlin Multiplatform adoption depends on decision-makers seeing measurable business value, not only on developer enthusiasm. It highlights reduced duplicated work across iOS and Android, native UI and workflows, potentially less code, faster release cycles, and improved maintainability. ### Source excerpt KMP adoption is not driven by developer enthusiasm alone. It moves forward when leaders see a clear case for measurable business value. ## Object Oriented Programming - The Key Terms DevFeed: [Object Oriented Programming - The Key Terms]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-24T08:38:43Z Content type: article Language: en Sources: [System Design Codex]() Topics: [Object-oriented programming (OOP)](), [Programming](), [Polymorphism](), [Inheritance](), [implementation](), [interface]() Tags: [abstraction](), [concepts](), [inheritance](), [maintainability](), [object-oriented](), [polymorphism](), [programming](), [security]() ### AI overview This tutorial introduces object-oriented programming through four principles: abstraction, encapsulation, inheritance, and polymorphism. It explains how abstraction hides implementation details, encapsulation controls access to data and methods, and inheritance supports reuse and hierarchical relationships. The supplied text begins its discussion of polymorphism but is truncated. ### Source excerpt The essential concepts ## Heroku March 2026 Update DevFeed: [Heroku March 2026 Update]() Original publisher: [Read original article]() Author: Keshav Pokkuluri Published: 2026-03-19T22:31:10Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [Machine learning]() Tags: [ai-ml](), [apps](), [changelog](), [cli](), [data](), [engineering](), [features](), [libraries](), [maintainability](), [news](), [platform](), [platform-updates](), [update]() ### AI overview Heroku describes a shift to a Sustaining Engineering model and announces three enhancements: a default compressed slug limit increased to 1GB, longer build timeouts, and Heroku CLI v11's move to ESM and oclif v4. ### Source excerpt We've transitioned to a Sustaining Engineering model to better serve the customers who rely on us every day. Our mission is simple: to provide the most stable, secure, and reliable environment for your apps and data. We will continue releasing features and functionality that align with our Sustaining Engineering goals and provide a more robust and efficient platform to our customers. Today we are excited to share three recent enhancements: The post Heroku March 2026 Update appeared first on Heroku. ## Modernizing the Command Line: Heroku CLI v11 DevFeed: [Modernizing the Command Line: Heroku CLI v11]() Original publisher: [Read original article]() Author: Eric Black Published: 2026-03-19T22:29:49Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [ECMAScript](), [modules](), [migration](), [maintenance](), [Usability]() Tags: [cli](), [command-line](), [heroku](), [javascript](), [legacy](), [maintainability](), [migration](), [modules](), [monorepo](), [news](), [node-js](), [npm](), [performance](), [release](), [upgrade](), [usability]() ### AI overview Heroku CLI v11 is available with a migration to ECMAScript Modules and oclif v4. The release also changes the build system from Yarn to npm, removes the monorepo structure, improves command execution and manifest caching, and adds semantic colors and theme support. ### Source excerpt Heroku CLI v11 is now available. This release represents the most significant architectural overhaul in years, completing our migration to ECMAScript Modules (ESM) and oclif v4. This modernization brings faster performance, a new semantic color system, and aligns the CLI with modern JavaScript standards. While v11 introduces breaking changes to legacy namespaces, the benefits are [...] The post Modernizing the Command Line: Heroku CLI v11 appeared first on Heroku. ## System Design: Principles for Maintainability, Scalability, and Reliability DevFeed: [System Design: Principles for Maintainability, Scalability, and Reliability]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Maintainability](), [reliability](), [Scalability](), [Architecture & Design](), [data](), [Testing](), [observability](), [CRUD](), [Latency]() Tags: [architecture](), [crud](), [data-systems](), [debug](), [latency](), [maintainability](), [observability](), [reliability](), [scalability](), [system-design]() ### AI overview This article presents production system design around reliability, scalability, and maintainability. It discusses data building blocks beyond CRUD, fault containment, isolation, testing, recovery, observability, latency versus response time, and vertical versus horizontal scaling. ### Source excerpt Reliability, scalability, and maintainability rest on one distinction: a fault is a component-level anomaly, a failure is the system no longer delivering its service. Design to contain faults so they never become failures, and stay precise that latency is waiting time while response time is the full client-visible number. ## AI Coding Best Practices for Today DevFeed: [AI Coding Best Practices for Today]() Original publisher: [Read original article]() Published: 2026-02-25T21:59:05Z Content type: tutorial Language: en Sources: [Colin The Shots]() Topics: [ai-coding](), [Artificial Intelligence](), [coding](), [GitHub Copilot](), [Claude](), [cursor](), [Development](), [Vulnerabilities](), [Code](), [Security](), [pair\_programming](), [Maintainability]() Tags: [ai](), [ai-coding](), [ai-coding-assistants](), [best-practices](), [claude](), [code](), [coding](), [copilot](), [cursor](), [developers](), [github-copilot](), [llms](), [maintainability](), [pair-programming](), [research](), [uncategorized]() ### AI overview A practical guide to using AI coding assistants such as GitHub Copilot, Claude, and Cursor while managing risks in code quality, deprecated APIs, security, performance, and maintainability. It emphasizes human responsibility, reviewing all generated code, and verifying it with tests, linters, and personal judgment. ### Source excerpt Why This Document Exists AI coding assistants like GitHub Copilot, Claude, Cursor, and others can significantly accelerate development. However, research shows they also introduce systematic risks: ## How Service Level Objectives Align Developers and Product Managers DevFeed: [How Service Level Objectives Align Developers and Product Managers]() Original publisher: [Read original article]() Author: Anis Khan Site Reliability Engineering is my role Cost optimization is my goal GitHub profile Linkedin profile Published: 2026-02-02T00:00:00Z Content type: opinion Language: en Sources: [Trivago]() Topics: [Availability](), [User Experience](), [data]() Tags: [availability](), [developer](), [engineering-culture](), [maintainability](), [opinions](), [outages](), [performance](), [site-reliability-engineering](), [technical](), [uptime]() ### AI overview This article argues that Service Level Objectives (SLOs) can reduce conflict between developers and product managers by creating a shared, data-driven agreement about reliability and user experience. It explains how a 99.9% availability target creates a 43.2-minute monthly downtime budget and shows how that budget can guide decisions about releasing features versus restoring stability. ### Source excerpt It's a scenario developers relate to a little too well. The product manager always comes with more and more feature requests. They also want to release fast by giving a tight deadline. While you... ## Blog: Introducing Falco 0.43.0 DevFeed: [Blog: Introducing Falco 0.43.0]() Original publisher: [Read original article]() Published: 2026-01-26T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [eBPF](), [Kernel](), [Maintainability]() Tags: [ebpf](), [falco](), [improvements](), [kernel](), [legacy](), [maintainability](), [race-condition](), [release](), [version]() ### AI overview Falco 0.43.0 is a stabilization release that consolidates changes from 0.42.0, adds deprecations, and fixes issues across Falcoctl, plugins, and libraries. It includes updates to Falco libraries and drivers, signature verification fixes, plugin fixes, and the reintroduction of the evt.arg.filename field. The release deprecates the legacy eBPF probe and gVisor engine while directing users toward modern alternatives. ### Source excerpt Dear Falco Community, we are happy to announce the release of Falco 0.43.0 today! This is a stabilization release that consolidates the changes introduced in 0.42.0, including the drop-enter initiative and the capture recording feature. It also introduces several deprecations to improve maintainability and fixes minor issues across falcoctl, plugins, and libs. During this release cycle, we merged: 31 PRs on Falco, including 11 release note-worthy changes 48 PRs on Falco libs, including 17 release note-worthy changes 8 PRs on Falco drivers, including 3 release note-worthy changes We upgraded libs to version 0.23.1 and drivers to 9.1.0+driver. Thank you to our maintainers and contributors. This would not have been possible without your support and dedication! To learn everything about the changes, read on! What's new? TL;DR Deprecations GPG key rotation Container plugin improvements Falcoctl tweaks and improvements Key fixes: evt.arg.filename field reintroduction Falcoctl signature verification fixes overflow and NULL pointer dereferences fixes for the container plugin, shipped with plugins/container/0.6.1 race condition fix for the k8smeta plugin, shipped with plugins/k8smeta/0.4.1 This release also comes with breaking changes that you should be aware of before upgrading. Latest updates Deprecations In Falco 0.43.0, we are announcing the deprecation of three significant components to streamline the project, reduce maintenance burden, and focus on modern, more efficient alternatives. All these components are stable, and considering that the deprecation is first enforced in this version, they could be removed at any future version starting from 0.44.0. Legacy eBPF probe deprecation The "legacy" eBPF probe (configured via engine.kind=ebpf) was the original eBPF implementation in Falco. It required compiling a specific probe for each kernel version, often necessitating the dynamic usage of the falco-driver-loader or pre-built drivers. The Modern eBPF probe (engine.kind=m ## Out with the Old, In with the New: A Guide to Application Upkeep DevFeed: [Out with the Old, In with the New: A Guide to Application Upkeep]() Original publisher: [Read original article]() Author: Andres Sacco Published: 2025-12-20T03:08:59Z Content type: tutorial Language: en Sources: [Java Advent Calendar]() Topics: [Java](), [migration](), [Spring Boot](), [Microservice](), [Vulnerabilities](), [Security]() Tags: [2025](), [automatic](), [guide](), [java](), [legacy-application](), [legacy-code](), [maintainability](), [microservices](), [migration](), [rewrite](), [security](), [spring](), [spring-boot]() ### AI overview This guide explains why upgrading Java or Spring Boot applications involves more than changing a version number. It discusses migration challenges, legacy code, differing versions across microservices, and risks from outdated software, including security, compatibility, stability, and maintainability concerns. ### Source excerpt Migrating an existing application to a new version of Java or a framework such as Spring Boot involves much more than simply updating a version number in a file. Each new release of a library or language brings new features, deprecations, behavioral changes, and sometimes complete API redesigns. When legacy code is involved, these upgrades [...] The post Out with the Old, In with the New: A Guide to Application Upkeep appeared first on JVM Advent. ## Creating an Arduino Library for ESP32 DevFeed: [Creating an Arduino Library for ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2025-12-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Arduino](), [ESP32](), [Library](), [Development](), [Code](), [C++](), [ide](), [Programming](), [API]() Tags: [arduino](), [arduino-ide](), [beginner](), [blog](), [c-plus-plus](), [class](), [classes](), [code](), [development](), [esp32](), [getting-started](), [guide](), [how-to](), [ide](), [libraries](), [library](), [maintainability](), [modular](), [modularity](), [modules](), [programming](), [structure](), [tutorial]() ### AI overview A step-by-step guide to creating, structuring, and publishing custom Arduino libraries for ESP32. It explains library benefits and structure, prerequisites, and implementation through a minimal "Hello World" example. ### Source excerpt Learn how to create, structure, and publish Arduino libraries for ESP32. This step-by-step guide covers everything from understanding a library structure to submitting your library to the Arduino Library Manager. ## Case Study: Modernizing a High-Traffic Streaming Platform with the AHA Stack (HTMX & Alpine.js) DevFeed: [Case Study: Modernizing a High-Traffic Streaming Platform with the AHA Stack (HTMX & Alpine.js)]() Original publisher: [Read original article]() Author: Daniel Bencz Published: 2025-08-29T17:02:07Z Content type: article Language: en Sources: [RisingStack]() Topics: [htmx](), [Web Development](), [Streaming](), [JavaScript](), [Back end](), [Flask]() Tags: [case-study](), [flask](), [htmx](), [js](), [maintainability](), [state-management](), [streaming](), [ux](), [web]() ### AI overview This case study describes modernizing a high-traffic streaming website for responsiveness, maintainability, business continuity, and easier developer onboarding. The existing Python Flask and Jinja site used jQuery; the team retained server-rendered architecture and adopted HTMX with Alpine.js instead of introducing a single-page application. ### Source excerpt Our client, a leading company in the streaming industry, acquired a highly successful indie website with over 50 million unique visitors per month. The site had been built by a single developer who prioritized functionality over maintainability. While the features were mostly bug-free, the design was outdated, and the code relied on aging technologies. The [...] The post Case Study: Modernizing a High-Traffic Streaming Platform with the AHA Stack (HTMX & Alpine.js) appeared first on RisingStack Engineering. ## Practical Considerations for Advancing AI Collaboration in Software Development DevFeed: [Practical Considerations for Advancing AI Collaboration in Software Development]() Original publisher: [Read original article]() Author: Peter Lawrey (noreply@blogger.com) Published: 2025-05-15T19:35:00Z Content type: opinion Language: en Sources: [Vanilla Java]() Topics: [Artificial Intelligence](), [AI Development](), [Development](), [Prompt Engineering](), [Software Engineering]() Tags: [ai](), [challenges](), [collaboration](), [development](), [evaluation](), [info](), [maintainability](), [mentoring](), [opinion](), [practical]() ### AI overview This article examines practical considerations for collaborating with AI in software development. It argues for human oversight, stronger documentation and context, critical evaluation of probabilistic outputs, diverse model use, and awareness of deskilling, ethical, intellectual-property, and software-economics risks. ### Source excerpt TL;DR Human-in-the-loop is essential; AI offers probability, not certainty. AI excels at word-smithing, so spend more time on documentation and context. Leverage diverse AI models for varied research, improvements, and analysis. Be wary of deskilling: if AI makes a task trivial, agents may soon replace it. You should feel like you are testing the boundaries of what AI is capable of for at least some tasks. The Problem AI's proficiency in handling routine coding allows human engineers to dedicate more time to strategic activities such as system design, architectural planning, intricate requirement elicitation, and the rigorous evaluation of application performance across multifaceted metrics. Tools often amplify underlying behaviours and failures -- Rob Lambert Value is increasingly found not in rote knowledge, which AI can often provide, but in the capacity to frame complex problems effectively for AI, critically evaluate its probabilistic outputs, and innovatively integrate AI's capabilities into novel solutions. Developing with AI is not merely about adopting a new tool but about learning to collaborate with intelligence that operates on different principles, sometimes without profound contextual understanding, yet capable of processing and synthesising information at a scale and speed that surpasses human capability. However, this power comes with new challenges: ensuring the reliability of probabilistically generated outputs, managing the 'black box' nature of some AI reasoning, and navigating the ethical and IP landscapes of AI-generated content. Effective collaboration requires developers to master prompt engineering, the art of providing precise context, critically verifying outputs, and understanding the AI's inherent limitations to guide it effectively. This is akin to mentoring an exceptionally capable but occasionally erratic junior partner. Moreover, "disposable" or "ephemeral" AI-generated software carries profound and often unexamined implications for s ## Make regular expressions easier to read DevFeed: [Make regular expressions easier to read]() Original publisher: [Read original article]() Author: Stanko Published: 2025-03-31T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Code](), [formatting](), [Maintainability]() Tags: [example](), [extra](), [join](), [maintainability](), [readability](), [regular-expressions](), [value]() ### AI overview The article presents a formatting technique for making complex regular expressions easier to read: split the expression into multiple string components, join them, and construct the final regex. The approach adds code and requires escaping backslashes, but enables scanning and comments that can improve readability and maintainability. ### Source excerpt This is a simple formatting trick I use to make regular expressions more readable. The secret? Break them into multiple lines. To achieve this, format the regex as an array of strings and then concatenate the array into a single regex string. Example # Compare this example, written in a single line: const FILTER_REGEXP = /(?blur|brightness|contrast|grayscale|hue-rotate|invert|opacity|saturate|sepia)\((?-?\d*(?:\.\d*)?)(?\w*?)\)/g; with the multi-line version: const SUPPORTED_FILTERS = [ 'blur', 'brightness', 'contrast', 'grayscale', 'hue-rotate', 'invert', 'opacity', 'saturate', 'sepia', ].join('|'); const FILTER_REGEXP = new RegExp( [ `(?${SUPPORTED_FILTERS})`, // filter name `\\(`, `(?\-?\\d*(?:\\.\\d*)?)`, // value `(?\\w*?)`, // unit if any `\\)`, ].join(''), 'g' ); The multi-line version has a bit more code, but it's easier to scan and read. It also allows us to write comments for each section, clarifying the purpose of each part of the regex. I've found that complex expressions are much easier to write this way. I believe it greatly reduces the cognitive load for both the writer and the reader. Caveats # You'll need to escape the backslashes in regex strings. While this is a minor inconvenience, the readability benefits easily outweigh it. Conclusion # It boils down to personal preference, but I believe the extra code is worth it, as it improves readability and maintainability. This is especially true when dealing with notoriously difficult-to-parse complex regular expressions. ## Ekapkgs, a poly-repo fork of Nixpkgs DevFeed: [Ekapkgs, a poly-repo fork of Nixpkgs]() Original publisher: [Read original article]() Author: Jon Ringer Published: 2025-03-31T00:00:00Z Content type: opinion Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [repo](), [Development](), [Maintainability](), [cloud-infrastructure]() Tags: [development](), [fork](), [glibc](), [infrastructure](), [maintainability](), [openssl](), [repo]() ### AI overview The article presents Ekapkgs as a poly-repository fork of Nixpkgs. It argues that Nixpkgs' monolithic scale, lengthy RFC process, and staging workflow make maintenance, convention changes, and package updates difficult, while separate repositories could enable faster iteration and more focused curation. ### Source excerpt Ekapkgs forks Nixpkgs, splitting it into repos for faster updates & easier curation. Ditch monolithic development flows & slow RFCs. Innovate freely! ## 2025 Priorities: Reliability, Audio, Cameras and More DevFeed: [2025 Priorities: Reliability, Audio, Cameras and More]() Original publisher: [Read original article]() Published: 2025-03-30T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [reliability](), [Linux](), [systemd](), [GitLab](), [Operating system](), [ci](), [Maintainability](), [Logging](), [test]() Tags: [ci](), [fosdem](), [gitlab](), [linux](), [logging](), [maintainability](), [postmarketos](), [reliability](), [systemd](), [test]() ### AI overview The postmarketOS community outlines its 2025 priorities, with reliability as the central goal. Planned work includes hardware for remotely testing phones, integrating real devices with GitLab CI, completing systemd integration, and upstreaming systemd support for musl. ### Source excerpt As our community grows, we are increasing the focus we put on planning and organizing the work we do. Therefore we have been thinking hard about priorities for this year. And as we mentioned after our FOSDEM hackathon, the greatest goal for this year is reliability. Reliability So far, the postmarketOS community has mostly been focused on functionality: Hackers bring up devices and get them to a point where various device features such as audio, calls and Wi-Fi are usable once or most of the time. We want to get it to always. Ongoing focus by the team Currently the postmarketOS team is focusing on the following projects: Getting a PCB ready to be able to place phones in a rack for testing. This is necessary so we have remote control of the devices for booting or flashing, and we avoid the risk of batteries in racks. There has been an amazing progress on the design in the last weeks, and a test run might be possible before v25.06. Thanks Federico, Anjan, Casey, and Nicola! Software work on CI-tron to be able to talk to devices and seamlessly connect them to our GitLab instance is underway upstream and in our repos. This allows treating real devices as any other runner in GitLab! We will share more information about this project, its architecture and reasons in a follow-up blog post. Thanks Martin R., Samuel, and Pablo! Finishing the integration of systemd, to bring its stability on-par with OpenRC (#3476). systemd brings considerable reliability improvements in the form of better management of services, logging, and more general predictability in the behavior of the lower-layers of the operating system. Though a lot of work is still needed, we are well on track to have systemd in v25.06! systemd musl upstreaming efforts are slowly underway. musl is the C standard library used in Alpine Linux and postmarketOS. It provides us with a great set of benefits, but has some limitations and is not supported in systemd. For maintainability reasons, it's critical we have suppor ## Angular Architecture Guide To Building Maintainable Applications at Scale DevFeed: [Angular Architecture Guide To Building Maintainable Applications at Scale]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2025-03-18T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Architecture & Design](), [Domain-driven design (DDD)](), [Scalability](), [Tooling]() Tags: [angular](), [architecture](), [collaboration](), [design](), [development](), [domain](), [domain-driven-design](), [guide](), [how-to](), [key-angular](), [key-architecture](), [maintainability](), [modular](), [nx](), [scalable-architecture](), [scale](), [software-architecture](), [structure](), [tooling]() ### AI overview A guide to architecting maintainable Angular applications at scale. It explains modular design, clear boundaries, dependency decoupling, layered and vertical architectures, and organizing code around business domains. ### Source excerpt Learn how to build scalable Angular applications using domain-driven design, clear boundaries, and Nx tooling for better maintainability and team collaboration. ## Programming Priorities DevFeed: [Programming Priorities]() Original publisher: [Read original article]() Author: Dan Lew Published: 2025-03-11T14:00:44Z Content type: opinion Language: en Sources: [Dan Lew Blog]() Topics: [Maintainability](), [Programming](), [Development](), [Software Engineering](), [Refactoring](), [Optimization]() Tags: [automated](), [code](), [code-design](), [coupling](), [decoupling](), [development](), [maintainability](), [programming](), [readability](), [software](), [software-development](), [tests]() ### AI overview This article presents a priority order for code design: functionality first, maintainability second, and other concerns afterward. It argues that maintainable code reduces the time and risk involved in future changes, allowing later refactoring and optimization. Suggested practices include automated tests, good architecture, decoupling, encapsulation, readable code, and useful comments. ### Source excerpt Software development (or, you know, life in general) is all about juggling priorities. For this post, I'm thinking specifically about code design priorities. You only have a limited amount of time to implement a feature, so you have to pick and choose which aspects of it to spend ## Keycloak JS 26.2.0 released DevFeed: [Keycloak JS 26.2.0 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-02-20T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [JavaScript](), [releases](), [version](), [Maintainability](), [npm]() Tags: [idm](), [javascript](), [kerberos](), [keycloak](), [keycloak-js-release](), [ldap](), [maintainability](), [npm](), [openid-connect](), [release](), [releases](), [saml](), [sso](), [version]() ### AI overview Keycloak JS 26.2.0 was released with no functional adapter changes. The JavaScript adapter now follows an independent release cycle, remains backward compatible with actively supported Keycloak server releases, and has moved to a dedicated repository to improve maintainability and community contribution workflows. ### Source excerpt Highlights Today marks a significant milestone in the evolution of Keycloak JS with the release of version 26.2.0. This new version represents a shift in how the JavaScript adapter develops and evolves alongside the Keycloak ecosystem. Although this new version introduces no functional changes to the adapter, it does include several organizational changes. The most notable change is that Keycloak JS now breaks free from the main Keycloak project's release cycle. As announced earlier this year, the JavaScript adapter will follow its own independent development path. The separation from the main project allows for more frequent releases of features, bug fixes, and improved responsiveness to community feedback. The JavaScript adapter will continue to be backwards compatible with all actively supported releases of the Keycloak server, and deviation from this will be considered a breaking change. The choice to use a higher version than the main project itself was made intentionally in order to signal to users the departure from Keycloak's release cycle. We will however continue to commit to using Semantic Versioning, only bumping major versions if backwards incompatible changes are made, as is customary in the NPM ecosystem. Maintenance updates will continue to land in the 26.1.x series, as it is tied to the current stable release of the Keycloak server, but we encourage users to upgrade to new versions as needed. Another significant change is the relocation of the codebase to its own dedicated repository. This structural adjustment is not just administrative--it represents a strategic move toward better maintainability. By separating the JavaScript adapter from the main Keycloak repository, the development team gains greater flexibility in managing the codebase and processing community contributions. If you are looking to provide contributions, or are reporting issues, please redirect your efforts here. Looking ahead, we will be focussing on what is next for Keycloak JS. ## KMMBridge 1.1.0 Released - Kevin Galligan DevFeed: [KMMBridge 1.1.0 Released - Kevin Galligan]() Original publisher: [Read original article]() Published: 2024-12-05T00:00:00Z Content type: release Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Refactoring](), [gradle-plugin](), [Maintainability](), [swift-package-manager](), [cocoapods](), [iOS](), [.NET 11]() Tags: [cocoapods](), [gradle](), [gradle-plugin](), [ios](), [kmmbridge](), [kotlin](), [kotlin-multiplatform](), [maintainability](), [refactoring](), [releases](), [spm](), [swift-package](), [swift-package-manager](), [xcode]() ### AI overview KMMBridge 1.1.0 is a significant internal refactoring of the Gradle plugin used to publish Kotlin Multiplatform Xcode Framework binaries through Swift Package Manager and CocoaPods. The release improves maintainability and adds Gradle configuration cache support where possible, while introducing separate modules for GitHub features and potentially requiring plugin ID changes for GitHub publishing. ### Source excerpt KMMBridge is a Gradle plugin that publishes Kotlin Multiplatform Xcode Framework dependencies for Swift Package Manager and CocoaPods. The 1.1.0 release is a significant internal refactoring to support ongoing improvements and maintainability. ## .NET Support on Heroku DevFeed: [.NET Support on Heroku]() Original publisher: [Read original article]() Author: Rune Soerensen Published: 2024-12-03T00:00:00Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [.NET](), [ASP.NET Core](), [Blazor](), [C#](), [F#](), [Visual Basic](), [cross-platform](), [Open Source](), [Databases]() Tags: [announce](), [apis](), [app](), [asp-net](), [asp-net-core](), [blazor](), [buildpacks](), [c-sharp](), [can](), [community](), [core](), [cross-platform](), [deploy](), [developers](), [f-sharp](), [heroku](), [high-performance](), [languages](), [maintainability](), [net](), [news](), [nextgen](), [platform]() ### AI overview Heroku announces that official .NET support is entering public beta. Developers can build and deploy C#, F#, and Visual Basic applications using frameworks including ASP.NET Core and Blazor. The support includes a buildpack, documentation, testing, and guidance for deploying applications, including Blazor apps with Heroku Postgres. ### Source excerpt We're excited to announce that official support for .NET on Heroku is entering public beta starting today. Developers can now build and deploy applications in C#, F#, and Visual Basic, using frameworks like ASP.NET Core and Blazor, all with the simplicity and flexibility of the Heroku platform. .NET has long been one of the most [...] The post .NET Support on Heroku appeared first on Heroku. ## SMURF: Beyond the Test Pyramid DevFeed: [SMURF: Beyond the Test Pyramid]() Original publisher: [Read original article]() Author: Google Testing Bloggers (noreply@blogger.com) Published: 2024-10-15T12:22:00Z Content type: tutorial Language: en Sources: [Google Testing Blog]() Topics: [Testing](), [Mocking]() Tags: [adam-bender](), [article](), [dependency](), [flaky](), [google](), [integration](), [maintainability](), [memory](), [production](), [resources](), [speed](), [testing](), [tests](), [tott](), [unit-tests]() ### AI overview This Google Testing on the Toilet article explains why the conventional test pyramid is insufficient for growing test suites. It introduces the SMURF mnemonic--Speed, Maintainability, Utilization, Reliability, and Fidelity--as a framework for balancing testing trade-offs. ### Source excerpt This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office. By Adam Bender The test pyramid is the canonical heuristic for guiding test suite evolution. It conveys a simple message - prefer more unit tests than integration tests, and prefer more integration tests than end-to-end tests. While useful, the test pyramid lacks the details you need as your test suite grows and you face challenging trade-offs. To scale your test suite, go beyond the test pyramid. The SMURF mnemonic is an easy way to remember the tradeoffs to consider when balancing your test suite: Speed: Unit tests are faster than other test types and can be run more often--you'll catch problems sooner. Maintainability: The aggregated cost of debugging and maintaining tests (of all types) adds up quickly. A larger system under test has more code, and thus greater exposure to dependency churn and requirement drift which, in turn, creates more maintenance work. Utilization: Tests that use fewer resources (memory, disk, CPU) cost less to run. A good test suite optimizes resource utilization so that it does not grow super-linearly with the number of tests. Unit tests usually have better utilization characteristics, often because they use test doubles or only involve limited parts of a system. Reliability: Reliable tests only fail when an actual problem has been discovered. Sorting through flaky tests for problems wastes developer time and costs resources in rerunning the tests. As the size of a system and its corresponding tests grow, non-determinism (and thus, flakiness) creeps in, and your test suite is more likely to become unreliable. Fidelity: High-fidelity tests come closer to approximating real operating conditions (e.g., real databases or traffic loads) and better predict the behavior of our production systems. Integration and end-to-end tests can better reflect realistic conditions, while unit [Next page]()