Here is my order for the 7 habits and how I apply them.
"Be proactive" by reading sites like Hacker News, listening to podcasts, and attending Meet UpsHere is my order for the 7 habits and how I apply them.
"Be proactive" by reading sites like Hacker News, listening to podcasts, and attending Meet Ups. "Begin with an end in mind" with your direction. Ask the 5 whys before starting. "Put first things first" by making priorities and talking to stakeholders. "Seek first to understand, then to be understood" is essential for building trust with others. "Think win-win" when you are negotiating. You don't want to burn bridges with those that help you. "Synergize" with your team through mentoring and coaching. "Sharpen the saw" by learning and automating in order to increase your efficiency....more
After 10 years of programming, I have developed some bad habits. The best way to get rid of a bad habit is replacing it with a good one. This book isAfter 10 years of programming, I have developed some bad habits. The best way to get rid of a bad habit is replacing it with a good one. This book is filled with good programming habits that you can use to replace those bad ones. Shorter methods, better names, and understandable code are just some of the things that I learned reading this book....more
The book covers great how-to programming tips. This was not the first book I read on programming habits so I had heard of many of these concepts beforThe book covers great how-to programming tips. This was not the first book I read on programming habits so I had heard of many of these concepts before. It was chapter 33 Personal Character that got my attention. No matter how much I study about programming, I will not get better at it until I work on myself. My thoughts are turned into software. I need to fight complexity not in the program, but in my mind. I have to break down the problems into simpler pieces. I have to express my ideas in simple terms. This book opened my eyes to the fact that programming is personal....more
This book taught me that basic functionality should be simple, standardized, and visible. I was able to apply these concepts to website design and datThis book taught me that basic functionality should be simple, standardized, and visible. I was able to apply these concepts to website design and data entry....more
My undergrad was Human Resource Management. As a programmer, I was missing some of the nuts and bolts of computer science. This book filled in some gaMy undergrad was Human Resource Management. As a programmer, I was missing some of the nuts and bolts of computer science. This book filled in some gaps. The most exciting part for me was chapter 24. The author takes you through machine code, assembly, and finally ALGOL....more
While reading the book I enjoyed the conversational tone and the examples it gave. I was able to identify 16 potential strengths.
When I took the exam,While reading the book I enjoyed the conversational tone and the examples it gave. I was able to identify 16 potential strengths.
When I took the exam, I was surprised that I had a strength that I did not identify. This made me read the book again and ask others how they felt. My friends agreed with the test and showed me how I use that strength without thinking about it....more
This book makes learning design patterns fun. I have read code that mentions Factory, Repository, and Proxy, but I didn't understand what these concepThis book makes learning design patterns fun. I have read code that mentions Factory, Repository, and Proxy, but I didn't understand what these concepts meant. Starting out with the official Gang of Four book sounded intimidating. This book offered a perfect way to learn the basics of these patterns. The examples were easy to understand. I really enjoyed reading this book....more
I read this book because it came highly recommended by many other testers in the industry. I thought it would not be relevant for Web and mobile testiI read this book because it came highly recommended by many other testers in the industry. I thought it would not be relevant for Web and mobile testing, but the principles are timeless. I really liked the humor and the matter-of-fact tone in the book. It kept me engaged....more
This book was a great read. It had humor. The examples were fun and easy to follow. The book talked about all the popular frameworks such as jQuery, bThis book was a great read. It had humor. The examples were fun and easy to follow. The book talked about all the popular frameworks such as jQuery, but it asked the reader to download their custom Core.js library. I did not download this library. Instead I used jQuery and was still able to complete the exercises....more
As a Quality Engineer I need to ask good questions to make sure the team has built the right product. This book taught me different kinds of questionsAs a Quality Engineer I need to ask good questions to make sure the team has built the right product. This book taught me different kinds of questions I can ask. It taught me what makes a good question. Asking a question is only the start. The book went on to teach me note taking and active listening skills....more
Read a little, code a little. That was my experience. I caught myself saying, "Wow, I want to try that" on almost every page. This was a great book toRead a little, code a little. That was my experience. I caught myself saying, "Wow, I want to try that" on almost every page. This was a great book to learn jQuery. Even though while I'm writing this review, jQuery has come out with a new version, the book's content is still relevant....more
I really enjoyed this book. This is the first programming book that I want to read more than once. The principles transcend the language. I learned toI really enjoyed this book. This is the first programming book that I want to read more than once. The principles transcend the language. I learned to leave code better than I found it. Use names that are human readable. Comments are an opportunity to make the code more expressive. No matter what language you code in, this book will help you be a cleaner coder....more
This was a great book on how testing can be accomplished in an Agile team. This book taught me that the testers can be involved at the planning, throuThis was a great book on how testing can be accomplished in an Agile team. This book taught me that the testers can be involved at the planning, through programming, and into a release. It also taught me the importance of test automation to meet deadlines. It was easy to read and very practical....more
This book inspired me to write book reviews as a way of maintaining a "Reading List". It challenged me to start a website so that I can "Share What YoThis book inspired me to write book reviews as a way of maintaining a "Reading List". It challenged me to start a website so that I can "Share What You Learn". Almost every chapter of the book has inspired or challenged me to do something. Some books you read and nod your head, this book you read and put into action....more
As a programmer I find it hard to pay attention to interruptions. My mind wanders during meetings. When my wife calls me at work, I can't remember a tAs a programmer I find it hard to pay attention to interruptions. My mind wanders during meetings. When my wife calls me at work, I can't remember a thing she said after I hang up. This book has given me practical advice on how to focus. This advice is based on ancient wisdom taken from the martial arts and modern scientific research....more
In 1969, John Adair wrote the book, Training for Decisions, which had a problem involving connecting a box made up of nine dots with just four lines.In 1969, John Adair wrote the book, Training for Decisions, which had a problem involving connecting a box made up of nine dots with just four lines. The solution to this problem coined the phrase, "Thinking outside the box."
I love to solve problems. That's one reason I got into computer programming. This book helped shine light on a bad habit I have with problem solving. I try to solve the problem before I understand it. The book gave practical steps towards understanding a problem, but it warns about Information Overload. There's a fine line between "He who hesitates is lost," and "Look before you leap."
This book confirmed my belief in Hammock Driven Development. It's the idea that we need to sleep on complex problems. Doing this gives our "Depth Mind" or subconscious a chance to solve it. When you get stuck, let it go. "A problem is a solution in disguise."...more
I was really impressed by the responsibility that Google places on its software engineers for quality. Testing and quality belong to the entire team aI was really impressed by the responsibility that Google places on its software engineers for quality. Testing and quality belong to the entire team and not just a few people with the word Quality in their job title.
The end of the book was a surprise. It made me envision a future where quality was just built into the framework for developing applications and not something bolted on at the end. The tools are getting better and the practices are improving to the level that testers can focus on the user experience and not basic correctness....more
I had a Zen moment while reading this book. The best way to make a decision is to not have a decision to make. The author tells a story about firefighI had a Zen moment while reading this book. The best way to make a decision is to not have a decision to make. The author tells a story about firefighters. When faced with a fire that is shooting straight up, they pour water on it from the top. When the fire is spreading out, they evacuate the area. They are experts. They realize the problem right away and know exactly how to deal with it. After years of experience, there is no decision. The solution is clear.
Other than becoming an expert, you can make checklists, explain the decision to other people, and above all don't panic!
This book opened my eyes to the importance of going outside my comfort zone. Researchers took a group of chess grandmasters and showed them a chess board. They asked them to find the checkmate in as few moves as possible. On the board there was a well-known five move checkmate and a three move checkmate. The masters found the five moves right away, but could not see the three moves that were also on the board. Even after removing the five moves, many of the masters still couldn't see the three moves. Their eyes kept drifting back to the place where the five move checkmate used to be. Their minds became locked on only one solution. It's called the Einstellung effect. The book discusses two ways to combat it. The one that spoke to me was, never get comfortable....more
Loading...
