Showing posts with label Book Reading. Show all posts
Showing posts with label Book Reading. Show all posts

Sunday, February 18, 2024

Jim Paul | What I Learned Losing a Million Dollars

 #JimPaul, #StopLoss, #LoseMillionDollars #止损

What I Learned Losing a Million Dollars Hardcover – April 30 2013

Wednesday, July 29, 2020

System design: Computer networking - a top-down approach 7th edition

July 29, 2020


Introduction

It is my Facebook onsite interview prepration on August 13, 2020. How should I prepare for Facebook system design interview? Do I purchase Leetcode premium version? Do I pay to purchase system design video from tech lead on youtube.com, a senior level programmer from Amazon to get one hour service? I choose to stay hunger, stay to be frugal, learn by myself. I do believe that best learning will happen if I choose not to be a parrot in my own system design interview. 

A network book

I like to focus on basics. One is to review operating system basics, and then networking basics. Since I have limit time to prepare, I like to work on networking basics. 

I chose to spend at least 10 hours to rush to go over as many topics in the book "Networking - Top down approach". I like to focus on application layer, case study about Netflix, youtube.com. 

Thursday, February 13, 2020

Design large data intensive application - find 10 mentors

Feb. 13, 2020

Introduction


It is so important for me to learn advanced topic about storage design - LSM tree this week. I like to encourage myself to learn better from reading book: Design large data intensive application, so I have to find terms like LSM tree, and then find good talks first. I like to give my ranking from those presenters.

Best talks 


It is so important for me to find mentors through youtube.com, so that I can learn most important content about storage design like LSM tree. I spent over 10 hours to read a book chapter, but I found out that I could not learn by myself, I need to get some help from those mentors.


  1. Oana Balmau
  2. Niv Dayan
  3. Alex Petrov




Here is data structure research Niv Dayan's page.
  1. Scaling Write-Intensive Key-Value Stores
  2. SILK: Preventing Latency Spikes in Log-Structured Merge Key-Value Stores
  3. What Every Programmer has to know about Database Storage by Alex Petrov

Sunday, January 19, 2020

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


Tuesday, March 27, 2018

Book reading: Competitive Programmer's Handbook

March 27, 2018

Introduction


It is my 10:00 pm mock interview as an interviewer. I never expected that I will interview a senior who will prepare Google onsite in 3 weeks. So I did ask two algorithms I studied today, and then I was so surprised to learn how good the peer gave his analysis, and also I learned the algorithm from his analysis.

I was told to read the book called: Competitive programmer's handbook by Antti Laaksoen, Draft December 10, 2017.

Advice from the peer


1. read Competitive Programmer's Handbook
2. 200+ on leetcode  - top 100 question
2.1 strong at DP - don't have to solve every DP
2.2 graphs -> open that topic and solve medium and hards

3. 10 minutes to solve a question -> look up the best solution for this problem -> don't code it immediately -> wait 2-3 days at least

Thursday, September 14, 2017

Mathematics for computer science

Sept. 14, 2017


Introduction



I reviewed a lot of computer science books and then found an excellent book to read. I am very good at reading mathematics and also like to learn how to think about more using mathematics, help me to be a competitive programmer.

Actually the revised version is over 1000 pages. But it is still my favorite book. I have to find time to read the book. The book is available on mit.edu website, the link is https://courses.csail.mit.edu/6.042/spring17/mcs.pdf. I also save it on my github and here is the link.


Monday, May 22, 2017

The art of programming contest

May 22, 2017

Plan to read the book "The art of programming contest". Julia read the discussion of special substrings algorithm in the week code 32 contest, here is the discussion link. Read the discussion:

"I studied Programming Challenges 3, Programming Contests, Hitchhiker's Guide to Competitive Programming and the Art of Programming Contests. I know what the most frequent algorithms is."



Write down a note to finish 30 minutes reading each time here.

1. May 22, 2017  12:04 pm - 12:34 pm

Chapter 2 Game Plan for a contest

Friday, May 19, 2017

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.

Sunday, May 14, 2017

Testable JavaScript

May 14, 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.

It is always a good idea to read book written by google programmers, specially short books like 200 pages.


Testable JavaScript




It is a good idea to read the book called "Testable JavaScript" again in 2017.

Choose a good fight, instead of fighting against the hackerrank contest lead board, Julia likes to follow the author, Mark Ethan Trostler, a googler by reading the book again.

The ideal case is that Julia will design the algorithm using a new school technique, by working smart on testable idea. Really focus on a small unit test case, instead of focusing on recurrence formula, analysis of the algorithm. Will try to read the book again in 2017 and see if there are some valuable ideas in the book.


Show how hard Julia tries to study the book and gather all topics she should learn again.



Book reading 



May 14, 2017 3:20 pm - 4:29 pm
Read the book from page 1 - 13, page 35 / 273, chapter one.

Chapter 2. Complexity 


Code size


Notes:

comand query separation - commands are setters and queries are getters.

internal and external names of docRoot versus realRoot


A better solution is to use private properties with public getters and setters.

Try to read JavaScript code and understand the discussion - maybe I should put the code in html page next time.
Try to complete chapter 2 reading first.

JSLint



Cyclomatic Complexity 



independent paths

jsmeter - a command-line tool


Read the article about Complexity metrics - link is here.

multiple exits -


bad fix probability

Actionable Items



Elements of JavaScript style - article link is here. Chinese translated version is here.

12 books every JavaScript developer should read - article link is here.

Read the book "The art of readable code" again. First reading is in 2014, Oct. 31, 2014.
Chapter 8: Break down giant expression - favorite example:

 Two ranges does not overlap

Thursday, November 24, 2016

Sunday, November 13, 2016

Mobile first

Nov. 13, 2016

Julia has to focus on learning mobile first design again. She went back to work on the book:

Luke Wroblewski - Mobile first

Spent 1 hour to read the book on Nov. 10.

Spent 2 hour to go over twitter account content on Nov. 10: Julia's favorite!
https://twitter.com/lukew


And then, she watched latest videos:
Luke Wroblewski Part 1 - Conversions@Google 2016
https://www.youtube.com/watch?v=OkeJg92PA4E&t=1380s

Luke Wroblewski Part 2 - Conversions@Google 2016
https://www.youtube.com/watch?v=1jUaGin7YTM&spfreload=5




Friday, November 4, 2016

Book: Becoming a Better Programmer

Nov. 4, 2016

Going Beyond Code to Become a Better Programmer - Interview with Pete Goodliffe
https://www.youtube.com/watch?v=vGmCc7AhKVo

Slideshow: 130+ pages
https://goo.gl/2tmjII

The only way to go fast is to go well.
Bob martin, speed kills, 97 things Every programmer should know

Learn to communicate effectively in speech and writing. Bjarne Stroustrup

More reading:

1. Book:  Code Craft: The Practice of Writing Excellent Code

https://www.amazon.ca/Code-Craft-Practice-Writing-Excellent/dp/1593271190

2. Beautiful Architecture - Leading Thinkers Reveal the Hidden Beauty in Software Design
http://shop.oreilly.com/product/9780596517984.do

Sunday, October 30, 2016

Book reading: Programming Challenges - The programming Contest Training Manual

Oct. 30, 2016

Plan to read the book - Programming Challenges - The programming Contest Training Manual
By Steven S. Skiena
      Miguel A. Revilla

http://www.programming-challenges.com/pg.php?page=index

Read first 2 hours, write down some notes to encourage good behavior - Algorithm book reading is a great way to relax, help to write great code and speed up everything - coding/ design/ maintenance.

http://www3.cs.stonybrook.edu/~skiena/

Wednesday, April 27, 2016

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