cis-venkat

My issues with Modules

In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.

A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.

You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.

class Article &lt; ActiveRecord::Base

@Pramati (02/07/2015)

Difference between module include and extending?
Difference between rails concerns and modules?
Difference between Proc and lambda?
Ruby Singleton patten? What are other patterns you know?
Explain SRP principle
Presentors - Drapper
Access modifiers - Difference between protected and private
Can use private methods of one class in its sub class? (Yes)
How 'super' works in ruby?

What are the differences between procs and lambdas?

Before getting into the differences, they are very similar and both are Proc objects.

proc = Proc.new { puts "Hello world" }
lam = lambda { puts "Hello World" }

proc.class # returns 'Proc'
lam.class  # returns 'Proc'

Originally published in June 2008

When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.

To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.

What to expect

Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.

Originally published in June 2008

When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.

To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.

What to expect

Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.

	# This is a skeleton for testing models including examples of validations, callbacks,
	# scopes, instance & class methods, associations, and more.
	# Pick and choose what you want, as all models don't NEED to be tested at this depth.
	#
	# I'm always eager to hear new tips & suggestions as I'm still new to testing,
	# so if you have any, please share!
	#
	# @kyletcarlson
	#
	# This skeleton also assumes you're using the following gems:

	1. https://gist.github.com/webficient/979005
	2. false.blank?
	3. Alias name for associations?