description: software development principle with the goal of reducing repetitive software patterns, and replacing them with abstractions that use data normalization to avoid redundancy
51 results
by Marc Bodmer · 11 Feb 2013 · 48pp · 10,481 words
of structure makes it easy to make modifications or refactor changes to any part of your code. It will also allow you to adhere to Don't Repeat Yourself (DRY) principles. The model is responsible for notifying associated views and controllers when there has been a change in the state of the application. The
by Rolf Schröder
every aspect of the work flow and code presented throughout the book. You may be surprised how short the book is. This owes to the don’t-repeat-yourself principle consequently followed in this book: Nothing that can be seen with minimum effort in code is repeated in the book. You will always get
by Max Kanat-Alexander · 23 Mar 2012 · 108pp · 28,348 words
of violating this rule, but the way to follow it is simple: just get real evidence that a problem is valid before you address it. Don’t Repeat Yourself This is probably the most well known rule in software design. This book is not the first place it’s ever appeared. But it is
by John Calcote · 20 Jul 2010 · 555pp · 119,733 words
. I've heard it called by many names, but the one I tend to use the most is the DRY principle—the acronym stands for don't repeat yourself. C function prototypes are very useful because, when used correctly, they enforce the fact that the public's view of a function is identical to
by Michael Dory, Adam Parrish and Brendan Berg · 29 Sep 2011 · 136pp · 20,501 words
elsewhere. UI Modules As we’ve seen, the templating system is lightweight but powerful. In practice, we’d like to follow the software engineering adage, Don’t Repeat Yourself. In order to eliminate redundant code, we can make sections of our templates modular. For example, pages that display lists of items can define a
by L.G. Meredith · 214pp · 14,382 words
the Haskell community, provided operations that behaved remarkably like sequencing and assignment. Haskell offers syntactic sugar to 1 DRY is the pop culture term for "Don’t repeat yourself.” Cover · Overview · Contents · Discuss · Suggest · Glossary · Index 21 Download from Wow! eBook <www.wowebook.com> Section 1.1 Chapter 1 · Motivation and Background support the
by Fabio Alessandro Locati · 21 Nov 2016
helps you to reduce duplicity while writing tasks. This also allows us to have smaller playbooks by including reusable code in separate tasks using the Don't Repeat Yourself (DRY) principle. To trigger the inclusion of another file, you need to put the following under the tasks object: - include: FILENAME.yaml You can also
by Jesse Keating
topic specific file that can be included into other files one or more times within a project. This inclusion feature supports the concept of DRY (Don't Repeat Yourself). Including tasks Task files are YAML files that define one or more tasks. These tasks are not directly tied to any particular play or playbook
…
180 D data encrypting, at rest 33, 34 disruptions delaying 147-152 destructive tasks, running only once 152, 153 managing 147 dot notation 162 DRY (Don't Repeat Yourself) 96 dynamic inventory plugins about 199, 200 developing 199-205 hosts, listing 201 host variables, listing 201 [ 209 ] E HAProxy behavior 6 encrypted files ansible
by Andrew Johnson · 29 May 2018 · 303pp · 57,177 words
third most significant language feature following control flow and data structures. Parameterization addresses the copy-and-paste problem of early languages. This feature permits the don't repeat yourself principle of good program design. In this chapter, we will look at how parameterization can help us design robust programs that evolve with change rather
by Lorin Hochstein · 8 Dec 2014 · 761pp · 80,914 words
chapter. In the next one, we’ll discuss roles, a convenient mechanism for organizing your playbooks. 1 Thanks to John Jarvis for this tip. 2 Don’t Repeat Yourself, a term popularized by The Pragmatic Programmer: From Journeyman to Master, which is a fantastic book. 3 etcd is a distributed key-value store, and
by Jason Lengstorf and Phil Leggetter · 20 Feb 2013
by Venkat Subramaniam · 1 May 2009 · 226pp · 17,533 words
by Alan Berg · 15 Mar 2012 · 372pp · 67,140 words
by James Sugrue · 15 Dec 2013 · 290pp · 119,172 words
by Matt Copperwaite and Charles Leifer · 26 Nov 2015
by Vikram Chandra · 7 Nov 2013 · 239pp · 64,812 words
by Mark Bates · 2 Jun 2012 · 323pp · 65,306 words
by John Arundel · 25 Aug 2013 · 274pp · 58,675 words
by Addy Osmani · 21 Jul 2012 · 420pp · 79,867 words
by Eric Brechner · 25 Feb 2015
by Michael Snoyman · 22 Apr 2012 · 485pp · 74,211 words
by Dustin Boswell and Trevor Foucher · 14 Sep 2010
by VM (Vicky) Brasseur · 266pp · 79,297 words
by Dan Cederholm · 14 May 2013 · 62pp · 15,274 words
by Nilanjan Raychaudhuri · 27 Mar 2012
by Sam Newman · 25 Dec 2014 · 540pp · 103,101 words
by Diomidis Spinellis and Georgios Gousios · 30 Dec 2008 · 680pp · 157,865 words
by Andreas M. Antonopoulos and Gavin Wood Ph. D. · 23 Dec 2018 · 960pp · 125,049 words
by Boris Cherny · 16 Apr 2019 · 629pp · 83,362 words
by Peter Seibel · 22 Jun 2009 · 1,201pp · 233,519 words
by Ben Frain · 24 Apr 2013
by Matt Behrens · 24 Jan 2015
by Clive Thompson · 26 Mar 2019 · 499pp · 144,278 words
by Neal Ford · 8 Dec 2008 · 224pp · 48,804 words
by Harry J. W. Percival · 10 Jun 2014 · 779pp · 116,439 words
by Aurélien Géron · 13 Mar 2017 · 1,331pp · 163,200 words
by Jeff Forcier
by Eric S. Raymond · 22 Sep 2003 · 612pp · 187,431 words
by Sean Kane and Karl Matthias · 14 May 2023 · 433pp · 130,334 words
by Ben Grynhaus, Jordan Hudgens, Rayon Hunte, Matthew Thomas Morgan and Wekoslav Stefanovski · 28 Jul 2021 · 739pp · 174,990 words
by Sean P. Kane and Karl Matthias · 15 Mar 2018 · 350pp · 114,454 words
by David Beazley and Brian K. Jones · 9 May 2013 · 1,606pp · 168,061 words
by Robert C. Martin · 1 Jan 2007 · 462pp · 172,671 words
by Dan Bader · 14 Oct 2017 · 262pp · 60,248 words
by Drew Neil · 6 Oct 2012 · 722pp · 90,903 words
by Andrew Hunt and Dave Thomas · 19 Oct 1999 · 509pp · 92,141 words
by Chas Emerick, Brian Carper and Christophe Grand · 15 Aug 2011 · 999pp · 194,942 words
by Kevlin Henney · 5 Feb 2010 · 292pp · 62,575 words
by Drew Neil
by Drew Neil
by Steve McConnell · 8 Jun 2004 · 1,758pp · 342,766 words