인간을 위한 코드

공백

- white-spaces are code too


leave a blank line between method definitions
a blank line when there is a changes in context within method body 

들여 쓰기

- indent code well
follow consistent indent length, 2 spaces or 4 spaces
be consistent with use of tabs or spaces, choose one and stick to it across the team(s)

변수 및 메서드 이름 지정

- use concise and meaningful names
variable names should reflect the value they refer
method names should reflect the process / business logic contained

선적 서류 비치

- unless it is a framework, module, class, method, variable names should be self documenting without need of additional documentation
comments should not be a tool to justify messy code segments

코드를 디자인하다

- every code is a piece of art uniquely conceived by it's developer
visualise the interactions between objects before beginning to code
visualise message exchanges needed before beginning to code

오른쪽 추상화

- abstraction does not mean hiding the complexity detail
know the behavioural traits to model
have a api spec to refer to
know before hand methods, variables, constants to expose
do not make decisions based on speculations
requirements are the corner stone

언어 관용구

- make use of language idioms
Ruby Example: [1, 2, 3, 4].sum  v/s  [1, 2, 3, 4].each {|ele| sum = sum + ele}

인간을 위한 코드