Uses dry-validation

Providing dry standard test environment for Ruby on Rails plugins

Dry interactor initializer

DRY module for APIs to render HTTP errors in JSON

DRY up your associations with named_scope conditions!

Dry::Types for RSpec

Combining the method object pattern with DRY initialization

DRY your RubyMotion project

Generates a Dry::Struct object from Dry::Validation::Contract schemas to avoid repetition when passing DTO's to your services.

Why does a squirrel swim on its back? To keep its nuts dry

Service is based on Dry::Monads

Enables relative controller paths in Padrino (for DRYness)

Uses guard monitoring to run rake file tasks to keep you DRY. \ (A placeholder for the moment.)

Dry your hands from the terminal

You've DRYed up your controllers. Now DRY up your controller specs.

its terminal time babyyyyyyÿyyyyy......................

Dry your hands from the terminal. Optional.

A simple plugin to DRY models

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.

Dry your hands from the terminal.