Combining the method object pattern with DRY initialization

There are tons of books yelling about how you shouldn't repeat yourself, how you should keep it DRY(Don't Repeat Yourself). Well, we tried hard to keep the code clean, but when it comes to blog we wrote, we seems quite ignorante to the DRY principle. During the whole developement process, there will always be some interesting points you want to record, so git gurus told us to write proper git commit messages for further reference or so. And yes, I followed, and I spent quite a time writing about the problem I encountered, how I found the solution, and what should might be useful in the future. That's nice, right? But I've also got a blog to write! Wait, I don't want to REPEAT MYSELF. And that leads to a barely touched blog site. And git-blog is here to help.

collection of often used cucumber steps to avoid the violation of DRY principle

Where Conditioner allows you to write conditional `where` expressions in a DRY manner.

Keep your code DRY by inferring column validations from table properties! Automagically validate presence, length, numericality, inclusion and uniqueness of ActiveRecord backed columns.

DRY your controllers and make your API more predictable by defining responders for different formats. E.g. Posting an invalid resource in HTML should render a form with errors, while in JSON you expect serialized errors.

Include more records in your relations/associations, just to DRY your code.

Dry-matcher free implementation of trailblazer endpoint, with ability to redefine matchers and handlers behavior for separate controllers or actions.

An intuitive and very DRY CSS framework that lets you dictate styling with classes that behave as they are named.

Know how you can't just use 'form_for' in rails with a newly initialized ActiveResource object? Ever get annoyed at having to add default attributes to your newly initialized ActiveResource objects? Fortify gives you the power to DRY'ly define default attributes for your ActiveResource derived classes.

Simplifies dry-data usage with Rails.

Outsource several config files to a gem.

Simplifies dry-types usage with Rails.

A collection of convenient assertions to enable faster DRY'er testing of Sequel database apps/gems.

DRY your RubyMotion project

DRY (Don't Repeat Yourself) of require 'spec_helper'.

My SAKURA gem with various utilities. This is my swiss-army knife for Linux and Mac. See README.md for amazing examples, like: richelp ubuntu # shows a richelp of my 'ubuntu' cheatsheet richelp sakura synopsis # shows a richelp of my 'sakura' cheatsheet, grepping for 'synopsis' ls | act # randomly scrambles the lines! Taken from cat/atc ;) ps | rainbow # colors all lines differently twice itunes - # lowers volume of iTunes... twice :) 10 echo Bart Simpson likes it DRY # tells you this 10 times. Very sarcastic script! seq 100 | 1suN 7 # prints every 7th element of the list zombies # prints processes that show zombies (plus funny options to kill them) find . -size +300M | xargs mvto /tmp/bigfiles/ # moves big files to that directory alias gp='never_as_root git pull' # only if u r not root it runs! tellme-time # Tells you the time with Riccardo voice in Italian. Brilliant! find-duplicates . # Tells you files with same size/MD5 in this directory facter is_google_vm # Tells if it's a GCE Virtual Machine

DRYer rendering method for Padrino, mainly used for templates for controllers

With this gem, a template is searched in the current controller's view folder (as usual). If it is not found there, the template with the same name in the view folder of the superclass controller is used. Finally, also views and partials remain DRY!

Keep a DRY multilingual translation of your ActiveRecord models' textual attributes