brunohenrique

0 = Success
1 = Operation not permitted
2 = No such file or directory
3 = No such process
4 = Interrupted system call
5 = Input/output error
6 = No such device or address
7 = Argument list too long
8 = Exec format error

brunohenrique

• Jim Weirich: The Building Blocks of Modularity – http://goo.gl/g4Nk
• Jim Weirich: SOLID Ruby – http://goo.gl/z3jd
• Sandi Metz: SOLID Object-Oriented Design – http://goo.gl/PDn6T
• Sandi Metz: Less – The Path to Better Design – http://goo.gl/VuTl4
• Demeter is for Encapsulation – http://is.gd/eeyLx
• Opinionated Modular Code – http://is.gd/eeyXm
• Scaling to Hundreds of Millions of Requests – http://vimeo.com/12814529
• Confident Code – http://goo.gl/VFLX
• Destroy All Software Screencasts – https://www.destroyallsoftware.com/screencasts
• Corey Haines: Fast Rails Tests – http://goo.gl/Va2gb

brunohenrique

The Elements of Programming Style

The following rules of programming style are excerpted from the book "The Elements of Programming Style" by Kernighan and Plauger, published by McGraw Hill. Here is quote from the book: "To paraphrase an observation in The Elements of Style by Strunk and White, the rules of programming style, like those of English, are sometimes broken, even by the best writers. When a rule is broken, however, you will usually find in the program some compensating merit, attained at the cost of the violation. Unless you are certain of doing as well, you will probably do best to follow the rules."