dry

Is there a way to simplify this sort of repetition in a Makefile? duo = ./node_modules/.bin/duo build: lib/background/build lib/page/build lib/popup/build lib/background/build: lib/background/build/build.js lib/background/build/build.css lib/page/build: lib/page/build/build.js lib/page/build/build.css lib/popup/build: lib/popup/build/build.js lib/popup/build/build.css lib/background/build/build.js: lib/background/index.js node_modules component.json @mkdir -p lib/background/build @$(duo) lib/background/index.js > lib/background/build/build.js lib/page/build/build.js: lib/page/index.js node

I use a template that generates a Bootstrap tab layout. Like below: <div class="a"> <ul class="nav nav-bar nav-stacked" role="tabs"> <li><a href="#home"></a></li> ... </ul> <div class="tab-content"> <div id="home">abc</div> ... </div> </div> Now this is pretty simple and straightforward tab navigation that can be hardcoded and achieved. I have a dynamic ng-repeat on the ul's li and the tab-content's div s. The JSON that I get from the REST service is something that contains the data for the tabs and the content to be displayed inside the tab-content within a single object. For eg: { "0": "a":

In one of my rails controller, I must respond to several types of formats, so I use the typical respond_to chain: respond_to do |format| format.html { ... } format.mobile { ... } format.jpg { ... } format.xml { ... } format.js { ... } end Usually that the { ... } part is repeated on several formats. What is the best way to stay DRY on this case? On an scenario in which html , mobile and xml have a "repeated" action, I'd like to do something like this: respond_to do |format| format[:html, :mobile, :xml] { ... } format.jpg { ... } format.js { ... } end Thanks a lot. Eric Hu Have you tried format

I have the following Model... class Room < ActiveRecord::Base belongs_to :hotel belongs_to :layout has_many :visits validates :number, presence: true validates :rate, presence: true validates :smoking, presence: true def self.rooms_with_smoking(smoking) self.where('smoking = ?', smoking) end def self.occupied_rooms(from_date, to_date) #24-26 self.joins(:visits).where('date >= ? and date <= ?', from_date, to_date).uniq end def self.vacant_rooms(from_date, to_date) self.where.not(id: Room.occupied_rooms(from_date, to_date)) end def self.blahblah(occupancy_count, smoking, from_date, to_date)

I see this scattered throughout code base: @RequestMapping(value = "myValue") I would prefer to use something like this: @RequestMapping(value = Constants.myValue) It seems to break DRY using the actual String value within @RequestMapping instead of constant. But is this good code practice? Should I use an enum instead? I may need to use Constants.myValue elsewhere in the code base. Should I use an enum instead? You can't. Annotation variables must be compile-time constants. Enums and String literals both are, but you can't create an enum that is a String and @RequestMapping needs a String