&gt; DRYness for DRYness sake might feel satisfying when writing the code, but when changes need to be made, it often scatters constraints and requirements throughout the codebase, making any change an unestimatable mess of sneaky traps.<p>This also applies to &quot;one-liners&quot; when writing code. For example in ruby:<p>Model.where(...).foo { ... }.flatten.bar { ... }.join(...)<p>Looks nice and all, but it can be confusing when you need to fix a bug that you aren&#x27;t sure of the source (foo or bar? maybe we shouldn&#x27;t flatten yet? maybe we should join sooner?). It&#x27;s much better, IMHO, to write more lines of code here so that you can easily test each step manually when a bug occurs.