Ollama: Ollama: improve existing draft article

2026-10-29T14:50:04Z

Ollama: improve existing draft article

← Older revision		Revision as of 14:50, 29 October 2026
Line 1:		Line 1:
			[[DRY]] (Don't Repeat Yourself) is a principle in software development that emphasizes reducing repetition in code to improve maintainability and reduce errors. While the principle is widely advocated, it is not an absolute rule. In certain contexts, such as writing specialised scripts or handling unique edge cases, repetition may be justified to enhance clarity, performance, or security. This article explores the origins, application, and exceptions to the [[DRY]] principle in software engineering.

			{{H2\|Origins and Definition}}
			The [[DRY]] principle was popularized in the 1999 book The Pragmatic Programmer by Andrew Hunt and David Thomas. It advocates that every piece of knowledge should have a single, unambiguous representation within a system. By eliminating redundant code, developers can simplify debugging, reduce the risk of inconsistencies, and make future modifications more efficient. However, the principle is not a strict mandate; it requires judgment based on the specific context of a project.

			{{H2\|Application in Software Development}}
	DRY is not absolute. It's OK to write specialised scripts.
			In practice, [[DRY]] is implemented through techniques such as code refactoring, modular design, and the use of functions or classes to encapsulate repeated logic. For example, a function that calculates tax rates can be reused across different parts of an application instead of duplicating the calculation logic in multiple places. This approach minimizes the risk of errors and streamlines updates, as changes need to be made in only one location. Tools like code linters and static analyzers often flag redundant code to help developers adhere to the [[DRY]] principle.

			{{H2\|Exceptions and Trade-offs}}
			Despite its benefits, [[DRY]] is not always applicable. In scenarios where performance is critical, duplicating code may be preferable to avoid the overhead of function calls. Similarly, specialised scripts—such as those handling one-time tasks or security-sensitive operations—may intentionally repeat logic to ensure isolation and prevent unintended side effects. Additionally, overzealous application of [[DRY]] can lead to overly abstracted code that is difficult to understand or debug. Thus, developers must balance the principle against practical considerations like readability, maintainability, and performance.

			{{H2\|References}}
			- [Software Development Principles](https://example.com/software-development-principles)
			- [The Pragmatic Programmer](https://example.com/pragmatic-programmer)

	{{Draft}}
	{{Software Development}}		{{Software Development}}

			{{Ollama}}
			{{Pending Human Review}}

Robert Brockway: Created page with " DRY is not absolute. It's OK to write specialised scripts. {{Draft}} {{Software Development}}"

2024-05-23T22:14:15Z

Created page with " DRY is not absolute. It's OK to write specialised scripts. {{Draft}} {{Software Development}}"

New page

DRY is not absolute. It's OK to write specialised scripts.

{{Draft}}
{{Software Development}}

DRY - Revision history

Ollama: Ollama: improve existing draft article

Robert Brockway: Created page with " DRY is not absolute. It's OK to write specialised scripts. {{Draft}} {{Software Development}}"