Zulkar Bedelbaev zismailov

Hanami Arch

Slides: https://speakerdeck.com/davydovanton/hanami-architecture

Telegram channel (russian): https://t.me/pepegramming

Ссылки на конкретные посты: http://telegra.ph/Pepegramming-Contents-07-16

https://github.com/davydovanton/hanami-architecture

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

-E: will describe the underlaying queries of the \ commands (cool for learning!)
-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

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.

Friendly URLs

By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:

/people/6

But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.

	#!/usr/bin/env ruby

	require 'socket'
	require 'whois'

	zones = %w(com ru)

	words = %w(
	word1
	word2

	HTTP status code symbols for Rails

	Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings.

	Status Code Symbol
	1xx Informational
	100 :continue
	101 :switching_protocols
	102 :processing

	#!/bin/bash

	#Precommit hook to prevent "debugger" and "console.log"

	#Note: to enamble precommit on Windows machine don't forget add path to Git\bin and Git\cmd to PATH environment variable
	count=0
	for FILE in `git diff-index --name-status HEAD -- \| cut -c3-` ; do
	# Check if the file contains 'debugger' or 'console.log'
	contains=`grep -e "debugger" -e "console\.log" -e "binding\.pry" $FILE`
	if [ `grep -e "debugger" -e "console\.log" -e "binding\.pry" $FILE\|wc -l` -ne 0 ]

	#!/usr/bin/env ruby

	require 'english'
	require 'rubocop'

	ADDED_OR_MODIFIED = /A\|AM\|^M/.freeze

	changed_files = `git status --porcelain`.split(/\n/).
	select { \|file_name_with_status\|
	file_name_with_status =~ ADDED_OR_MODIFIED

	#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)

	# A few examples about how to use Ruby for parsing files as we could do
	# with Awk or Grep. This is based on what I learn fro this post:
	# http://code.joejag.com/2009/using-ruby-as-an-awk-replacement/

	# Split each line with ':' and print the first $F[0] field
	awk -F: '{ print $1 }' /etc/passwd
	ruby -F: -nae 'puts $F[0]' /etc/passwd

	# Parse the 'ps aux' output
	# It'll print the ID process for the 'jojeda' user