Ildar Safin ildarsafin

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

Description

In this episode, Jay McGavren shares some of his favorite tricks for working in the shell. No unreadable sed or awk scripts here. Just simple, solid tips you can use every day, including time savers with find, less, ssh, and command-line Ruby.

Why learn shell commands when there's an IDE?

http://programmer.97things.oreilly.com/wiki/index.php/The_Unix_Tools_Are_Your_Friends

	#Model

	@user.should have(1).error_on(:username) # Checks whether there is an error in username
	@user.errors[:username].should include("can't be blank") # check for the error message

	#Rendering
	response.should render_template(:index)

	#Redirecting
	response.should redirect_to(movies_path)

	=Navigating=
	visit('/projects')
	visit(post_comments_path(post))

	=Clicking links and buttons=
	click_link('id-of-link')
	click_link('Link Text')
	click_button('Save')
	click('Link Text') # Click either a link or a button
	click('Button Value')