# reusable code Published articles for reusable code. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## When Duplicated Code Is the Better Tradeoff DevFeed: [When Duplicated Code Is the Better Tradeoff]() Original publisher: [Read original article]() Author: Franco Fernando Published: 2026-07-04T06:05:31Z Content type: opinion Language: en Sources: [The Polymathic Engineer]() Topics: [Software Engineering](), [Code](), [distributed-systems](), [Microservice](), [Library]() Tags: [abstraction](), [bugs](), [code](), [components](), [distributed](), [distributed-systems](), [reusable-code](), [services](), [software](), [software-engineering](), [teams]() ### AI overview This article examines when following the DRY principle creates more cost than value. It argues that duplicated code can be reasonable when abstraction adds coordination overhead, tight coupling, or inflexibility, especially across distributed services and teams whose code may evolve differently. ### Source excerpt When duplicated code is the better tradeoff. ## Managing State in Vue Applications: The Composable Provider Pattern DevFeed: [Managing State in Vue Applications: The Composable Provider Pattern]() Original publisher: [Read original article]() Author: Doximity Published: 2023-07-21T07:23:00Z Content type: article Language: en Sources: [Doximity]() Topics: [Vue.js](), [Front end](), [Scalability](), [Nuxt.js]() Tags: [code-modularity](), [components](), [maintainability](), [modularity](), [reusable-code](), [reuse](), [scalability](), [state-management](), [vue]() ### AI overview This article explains the Composable Provider pattern for state management in Vue applications. The approach combines the Vue Composition API with the Provide/Inject APIs to manage complex, feature-driven state, with benefits including scalability, maintainability, reusability, and reduced code duplication. ### Source excerpt State management is a fundamental concept of front-end application design, and a critical aspect in building robust Vue applications. As Vue applications grow in complexity, managing state becomes an increasingly challenging task, especially when working with a large organization of engineers spread across various product teams. Fortunately, the Vue and Nuxt ecosystem provides a variety of state management solutions, each with its own trade-offs. In this blog post we will explore the Composable Provider pattern, which handles state management by combining the Vue Composition and Provide/Inject APIs, and why its clean and simple implementation is a powerful approach to handling complex, feature-driven state in modern Vue applications. Note: This article was originally intended as a reference for our internal engineering team, but given its potential general use among Vue application developers we are publishing it here. We hope you'll find this pattern helpful when designing your Vue application's state as we have here at Doximity! Why Efficient State Management Matters Efficient state management plays a crucial role in the development of Vue applications. As applications grow in complexity, the ways in which we manage and handle changes to state become increasingly important. Here are a few key reasons why managing state efficiently matters: Scalability: As Vue applications and the teams building them grow in size, the complexity and size of their state grow also. Efficient state management allows for better scalability by providing a structured and organized approach to handling state. It becomes easier to add new features, maintain existing functionality, and reason about the flow of data within the application. Code Maintainability: Well-managed state reduces code complexity and promotes code maintainability. When state is not encapsulated properly, it becomes challenging to understand and modify the application's behavior. By implementing sound state management ## Making Twig Macros Work Like Functions DevFeed: [Making Twig Macros Work Like Functions]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2023-07-14T18:38:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Programming](), [Development](), [reusable code](), [Code]() Tags: [functions](), [insights](), [just](), [languages](), [learn](), [like](), [macros](), [make](), [manipulate](), [programming](), [programming-languages](), [return](), [returning](), [reusable-code](), [twig](), [value](), [values]() ### AI overview A tutorial on making Twig macros return values that can be manipulated like function results. It demonstrates a sales-calculation macro, whitespace control, and returning a value for further computations such as sales tax. ### Source excerpt Learn how to make Twig macros return values you can manipulate, just like functions in other programming languages ## Generics vs. Interfaces DevFeed: [Generics vs. Interfaces]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Binance](), [backends](), [Code]() Tags: [adapter-pattern](), [api](), [api-server](), [business-logic](), [decoding](), [decoupling](), [encoding](), [function](), [generics](), [go](), [go-api-server](), [gorm](), [http](), [interfaces](), [reusable-code](), [solid](), [solid-principles](), [transactions](), [video]() ### AI overview A video explains how generic functions and adapter functions can reduce code duplication and decouple business logic from API server handlers in Go. It demonstrates HTTP handlers, GORM database transactions, performance evaluation with PPROF, and generic data encoding and decoding. ### Source excerpt Introduction In this video, Paulo shows the benefit of leveraging generic functions to write less code that does more. He starts by walking you through an API server he initially wrote that makes use of Go's default HTTP handlers with a sprinkle of GORM to manage database transactions. He then refactors that code by introducing the concept of adapter functions. Paulo's approach consists of decoupling his business logic with his API code. To achieve this, he defines an adapter function that will establish a bridge between his business logic and API server handlers. This proves to be an effective way to abstract request processing and handling. This approach also promotes code reusability because the business logic is loosely coupled with the API service invoking it. ## Why Are There Functions? DevFeed: [Why Are There Functions?]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2022-09-29T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Programming](), [function](), [Assembly](), [Polymorphism](), [C](), [reusable code]() Tags: [assembly](), [c](), [code](), [polymorphism](), [programming](), [reusable-code]() ### AI overview The article examines why programmers write functions, drawing on the author's experience with assembly language for embedded systems. It argues that functions reduce repeated code, memory use, duplicate debugging effort, and reliability risks, while enabling reusable code; C automates much of the calling work required in assembly language. ### Source excerpt Returning from giving my Polymorphism Unbound presentation at StrangeLoop (not yet available on YouTube, but all the examples and presentation slides are on Github), I found myself dissatisfied. Part of this was certainly my failure to cram a 2-hour presentation into 40 minutes (after cutting it down from a day-long, workshop-length size). The bigger issue was my inability to answer the essential question at the end of the presentation: why are we writing polymorphic functions? ## Learning From npm's Rough Few Months DevFeed: [Learning From npm's Rough Few Months]() Original publisher: [Read original article]() Author: Adam Published: 2017-08-15T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [npm](), [Package manager](), [JavaScript](), [Critical Infrastructure](), [Security](), [reusable code]() Tags: [critical-infrastructure](), [javascript](), [npm](), [reusable-code](), [security]() ### AI overview This commentary examines npm's difficult recent period, what npm and other package managers could do, and what policy lessons may follow from treating package infrastructure as critical infrastructure. ### Source excerpt [no description provided] ## MVVM-C A simple way to navigate DevFeed: [MVVM-C A simple way to navigate]() Original publisher: [Read original article]() Author: Susann Proszak Follow Published: 2016-08-26T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [iOS development](), [mvc](), [Mobile](), [navigation](), [reusable code]() Tags: [architectures](), [business-logic](), [design-patterns](), [ios-development](), [mobile](), [mvc](), [mvvm](), [navigation](), [reusable-code](), [testing]() ### AI overview An introduction to the MVVM-C design pattern for iOS development. The article explains how coordinators handle application navigation and flow while view models contain business logic, using a small demo app to illustrate the approach. ### Source excerpt When thinking about design patterns and architectures in iOS development, MVC might be the first thing that comes to mind for most of you. But throughout the last years, MVC got a really bad reputation. Probably a lot of you heard about MVC as the massive view controller.