bansalakhil

# I have seen people writing something like:

users.collect{|u| u.tasks.size}.sum

# This can also be written as

users.sum{|u| u.tasks.size}

bansalakhil

Only show commit history earlier than 5 days ago:

git log --since=5.day.ago


Only show commit history older than 5 days ago:

git log --until=5.day.ago

bansalakhil

# Rails Edge: Custom Flash Types
#
#Rails just got some syntactic sugar for dealing with flash messages in
#your controllers and views.
#
#You can now declare the following in your controllers:
#

class ApplicationController
  add_flash_types :error, :warning

bansalakhil

Allow scaffold/model/migration generators to accept a polymorphic modifier for references/belongs_to, for instance

rails g model Product supplier:references{polymorphic}

will generate the model with belongs_to :supplier, polymorphic: true association and appropriate migration.

bansalakhil

# Edge rails you can do: 

create_join_table :products, :categories


# Earlier:

 create_table :categories_products, :id => false do |td|
   td.integer :product_id, :null => false
   td.integer :category_id, :null => false

bansalakhil

# cattr_accessor

class Base
  cattr_accessor :settings

  # def self.settings
  #   @@settings
  # end

  # def self.settings=(value)

bansalakhil

Beginner’s Guide to Responsive Web Design
http://blog.teamtreehouse.com/beginners-guide-to-responsive-web-design

Responsive Web Design, by- ETHAN MARCOTTE
http://www.alistapart.com/articles/responsive-web-design/

E-Book on Responsive web design, by - ETHAN MARCOTTE
http://www.abookapart.com/products/responsive-web-design

A Presentation on Responsive Design:

bansalakhil

# In rails 3.2, it's creating custom error pages is much more easier:
#
# Add this to config/application.rb:

  config.exceptions_app = self.routes

# That causes errors to be routed via the router. Then you just add to config/routes.rb:

  match "/404", :to => "errors#not_found"

bansalakhil

Hey there! And welcome to my little mailing list about writing faster Rails tests.
 
My goal is to send you only focused, actionable info that will help you speed up your test suites right away. Let's get started!
 
The first thing we'll cover is the leading cause of test slowness in Rails apps: bloated fixtures.
 
Here's an example of a test that will run far slower than it needs to (using factory_girl (a great tool, despite its involvement in this test's slowness)):
 
describe "#full_name" do

bansalakhil

defmodule Power do
  defmacro raise_n(x) do 
    method_name = :"raise_#{x}"
    quote do
      def unquote(method_name)(val) do
        :math.pow(val, unquote(x) )
      end
    end
  end
end