Reviews
I was selected for the third cohort of Jpub's IT book reviewers and received a copy of this book. The book itself is very easy to read, but there is a prerequisite: you should know some programming, have encountered plenty of errors, tried debugging, and gone through your share of trial and error. The main topics are organized like this: 0) identifying the components and types of errors; 1) how to read errors; 2) debugging methods for finding the cause of defects; 3) what to do when debugging
I've been working as a professional developer since 2017, and this book gave me a chance to reflect on whether I had relied too much on Stack Overflow and Google and not tried hard enough to solve problems on my own. Some of it may feel familiar to experienced developers, but I recommend it to students who are just starting out and people in their first development job. It's a book I'd like to give to a new employee joining as a developer.
Today’s book review is of The Book That Makes You Not Afraid of Errors, by Hiroyuki Sakuraba and Kotaro Mochizuki. You encounter all kinds of errors while developing software. I remember how helpless and overwhelmed I felt as a beginner when faced with so many error messages and problems I could not understand. After encountering errors often, I learned that most of them could be solved with a Google search, so they stopped feeling quite so frightening. These days, AI such as GPT is a big help
The Book That Makes You Not Afraid of Errors offers a comprehensive, practical guide to errors and debugging. It covers everything from reading and understanding errors to debugging efficiently and writing code that is easier to debug. It should be a great help to any developer who feels afraid of errors, especially junior developers and senior developers who have not learned debugging systematically. The book gives concrete methods that can be applied directly at work and helps improve
As I read each chapter, I felt it connect with my experience as a mobile development team lead of 15 years, wrestling with countless bugs. Looking back, implementing features in code takes less than half of the total time spent on software development; most of the time seems to go to communication and debugging. I think debugging is one of the things that has the greatest impact on software quality. This book offers practical ways to reduce the fear we feel when facing errors and turn them into
This book explains important ideas in a lighthearted, friendly way. Even people who love development can have heart-pounding moments while coding, and that moment comes when they encounter an error. The author explains errors as if introducing them as friends, and you can see the effort to put readers at ease. I'm grateful for that. I would recommend this book to junior developers and people just starting out. Although it focuses mainly on JavaScript, I was able to read it without difficulty as
It's important to understand the root cause of an error and be able to fix simple ones. The book explains why errors feel scary, how to find their causes, how to debug, and how to use test code. As a college junior, I had already used or knew most of the methods, but I learned about static code analysis tools from this book! I liked the illustrations throughout, and even though I don't usually like writing in books, I appreciated that the important parts were underlined. People who are just
This is a light, accessible development book with important content. Errors are unavoidable, and many developers find them difficult to deal with. The book explains why developers struggle with them and clearly presents ways to analyze errors and debug so they can overcome those challenges. It uses JavaScript for many of its examples among the various languages, making the material especially fun and easy to understand for front-end developers. I think this book can be a first step for
This book makes errors, especially front-end errors, less intimidating for junior developers. It reminded me of my early days as a new developer, when I would ask someone right away or paste an error into Google without even trying to read it. First, calmly read the error message. The answer is often right there. Read this book, too, and improve your coding and debugging skills. It's small, but packed with tips worth remembering. Be sure to read it!
Hiroyuki Sakuraba et al.: A book that makes errors less scary
Any programmer has probably had development grind to a halt because of an error at least once. You may have thought, "The code won’t work because there’s an error!", "I don’t know what caused it!", or "No matter what I do, I can’t fix it!" Even experienced programmers cannot completely prevent errors or defects in software. That makes the ability to quickly find the cause of errors and defects essential for programmers. This book clearly explains what to do when code does not work and how to handle errors and defects well. It is recommended for every developer who wrestles with broken code every day, from junior developers and senior developers who never properly learned debugging to beginners who cannot enjoy development because they are afraid of errors.
Korean title: 에러가 무섭지 않게 되는 책
Korean author: 사쿠라바 히로유키 외
Korean publisher: 제이펍
ISBN-13: 9791193926307
Reviews
I was selected for the third cohort of Jpub's IT book reviewers and received a copy of this book. The book itself is very easy to read, but there is a prerequisite: you should know some programming, have encountered plenty of errors, tried debugging, and gone through your share of trial and error. The main topics are organized like this: 0) identifying the components and types of errors; 1) how to read errors; 2) debugging methods for finding the cause of defects; 3) what to do when debugging
I've been working as a professional developer since 2017, and this book gave me a chance to reflect on whether I had relied too much on Stack Overflow and Google and not tried hard enough to solve problems on my own. Some of it may feel familiar to experienced developers, but I recommend it to students who are just starting out and people in their first development job. It's a book I'd like to give to a new employee joining as a developer.
Today’s book review is of The Book That Makes You Not Afraid of Errors, by Hiroyuki Sakuraba and Kotaro Mochizuki. You encounter all kinds of errors while developing software. I remember how helpless and overwhelmed I felt as a beginner when faced with so many error messages and problems I could not understand. After encountering errors often, I learned that most of them could be solved with a Google search, so they stopped feeling quite so frightening. These days, AI such as GPT is a big help
The Book That Makes You Not Afraid of Errors offers a comprehensive, practical guide to errors and debugging. It covers everything from reading and understanding errors to debugging efficiently and writing code that is easier to debug. It should be a great help to any developer who feels afraid of errors, especially junior developers and senior developers who have not learned debugging systematically. The book gives concrete methods that can be applied directly at work and helps improve
As I read each chapter, I felt it connect with my experience as a mobile development team lead of 15 years, wrestling with countless bugs. Looking back, implementing features in code takes less than half of the total time spent on software development; most of the time seems to go to communication and debugging. I think debugging is one of the things that has the greatest impact on software quality. This book offers practical ways to reduce the fear we feel when facing errors and turn them into
This book explains important ideas in a lighthearted, friendly way. Even people who love development can have heart-pounding moments while coding, and that moment comes when they encounter an error. The author explains errors as if introducing them as friends, and you can see the effort to put readers at ease. I'm grateful for that. I would recommend this book to junior developers and people just starting out. Although it focuses mainly on JavaScript, I was able to read it without difficulty as
It's important to understand the root cause of an error and be able to fix simple ones. The book explains why errors feel scary, how to find their causes, how to debug, and how to use test code. As a college junior, I had already used or knew most of the methods, but I learned about static code analysis tools from this book! I liked the illustrations throughout, and even though I don't usually like writing in books, I appreciated that the important parts were underlined. People who are just
This is a light, accessible development book with important content. Errors are unavoidable, and many developers find them difficult to deal with. The book explains why developers struggle with them and clearly presents ways to analyze errors and debug so they can overcome those challenges. It uses JavaScript for many of its examples among the various languages, making the material especially fun and easy to understand for front-end developers. I think this book can be a first step for
This book makes errors, especially front-end errors, less intimidating for junior developers. It reminded me of my early days as a new developer, when I would ask someone right away or paste an error into Google without even trying to read it. First, calmly read the error message. The answer is often right there. Read this book, too, and improve your coding and debugging skills. It's small, but packed with tips worth remembering. Be sure to read it!
