The art of readable code - book review

January 19, 2020

Introduction

It is so hard for me to find my writing back in 2014. I did not write so often and I am lucky to find my writing on my Linkedin.com.

The book recommendation

The following is written by me back in 2014.

Code review, rewrite

Jul 2014

Project description

Two month fan of the book - The art of readable code, from August - Oct. 2014; and then, started to practice code review, change the code to make it readable. Big fan of DRY (Do not repeat yourself) principle, do one thing a time, break giant expression, using explaining variable or summary variable, and abstract the thing to a function, extract a subproblem to a function. Training with great mind, like tennis sport, is a good practice. The book is coach's book with guidelines. Follow closely, in this 2014.
http://shop.oreilly.com/product/9780596802301.do

Book reading: The art of readable code

May 19, 2017

Introduction

As a hackerrank contest player, Julia likes to do some research on how to improve her performance. She was surprised that she could not figure out easy algorithm on Hackerrank last year, and then she posted questions on codereview.stackexchange.com, and then she quickly followed the advice. She felt more confident on easy algorithm on hackerrank contest. Here is one of questions she asked on a easy algorithm called Spiral Message.

For medium level algorithm, Julia stumbled badly on Rookie3 maximum score algorithm. She tried to look up the lead board and then tried to find out a good solution to work on her skills, and then she figured out that it is better to work on the basics. She remembered that she read a book to teach how to set up a good test case, and she likes to enhance her skills to use test case for the algorithm analysis.

The book is called "The art of readable code", chapter 14: testing and readability.

The art of readable code - book review second time

April 27, 2016

 Julia spent one month to go over the book, use it to do some code review in 2014. So, write down things learned from her favorite book:

 http://www.amazon.com/Art-Readable-Code-Theory-Practice/dp/0596802293

  chapter 5: Knowing what to comment
  chapter 6: Making comments precise and compact
  chapter 7: Make control flow easy to read <- 9 out of 10
  chapter 8:  Break Down giant expression  <- 10 out of 10
  chapter 10: Extracting unrelated subproblems <- Favorite (8/ 1-10)
  chapter 11: One task a time <- Should follow the idea more closely

 Later, compare to "Clean Code" book, write a few words to share.

A blog about naming variable: (10-15 minutes reading)
http://a-nickels-worth.blogspot.ca/2016/04/a-guide-to-naming-variables.html