lo w vsvld

Inspired by dannyfritz/commit-message-emoji

Rails naming conventions

General Ruby conventions

Class names are CamelCase.

Methods and variables are snake_case.

Methods with a ? suffix will return a boolean.

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!

\

Chapter 1 - Object Oriented Design

The purpose of design is to allow you to do design later, and it's primary goal is to reduce the cost of change.

SOLID Design:

Single Responsibility Principle: a class should have only a single responsibility
Open-Closed Principle: Software entities should be open for extension, but closed for modification (inherit instead of modifying existing classes).
Liskov Substitution: Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
Interface Segregation: Many client-specific interfaces are better than one general-purpose interface.

Rails Rspec APIs Testing Notes

Folders Structure

  spec
  |--- apis #do not put into controllers folder. 
        |--- your_api_test_spec.rb  
  |--- controllers
  |--- models
  |--- factories
 |--- views

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.

	#!/bin/env ruby
	#
	# Collects info about the age of all gems in the project
	#
	require "json"
	require "date"

	bundle = `bundle list`

	yearly_stats = {}

	# File: app/controllers/api/api_controller.rb
	class Api::ApiController < ActionController::Base
	# Consider subclassing ActionController::API instead of Base, see
	# http://api.rubyonrails.org/classes/ActionController/API.html

	protect_from_forgery with: :null_session
	before_action :authenticate

	def self.disable_turbolinks_cookies
	skip_before_action :set_request_method_cookie

Commit type	Emoji
Initial commit	🎉 `:tada:`
Version tag	🔖 `:bookmark:`
New feature	✨ `:sparkles:`
Bugfix	🐛 `:bug:`