Practical techniques for writing code that is robust, reliable, and easy to understand and adapt to your team members.
In Good Code, Bad Code, you will learn how to:
- ✓ Think about code like an effective software engineer.
- ✓ Write functions that read like well-structured sentences.
- ✓ Ensure the code is reliable and error-free.
- ✓ Unit test code effectively.
- ✓ Identify code that may cause problems and improve it.
- ✓ Write code that is reusable and adaptable to new requirements.
- ✓ Improve your mid- and long-term productivity.
- ✓ Save time for you and your team.
The difference between good code and bad code often depends on how you apply the established practices of the software development community. In Good Code, Bad Code, you'll learn how to increase your productivity and efficiency with insights about code development that are typically only learned through careful mentoring and hundreds of code reviews.
About technology:
Software development is a team sport. For an application to be successful, your code needs to be robust and easy to understand, maintainable, and adaptable to others. Whether you're working on an enterprise team, contributing to an open source project, or starting a startup, knowing the difference between good code and bad code is valuable.
About the book:
Good Code, Bad Code is a clear, practical introduction to writing code that is easy to read, apply, and remember. With dozens of immediately useful techniques, you'll find coding insights that typically take years of experience to master. In this quick guide, the author, a Google software engineer, walks you through the many rules to apply, along with advice on when to break them!
Contents inside the book:
- ✓ Write functions that read like sentences.
- ✓ Make sure your code is error-free.
- ✓ How to detect bad code.
- ✓ Save time for yourself and your team.
About the reader:
For beginner programmers who are familiar with object-oriented languages, such as Java or C#.
Index:
- ✓ PART 1: IN THEORY:
- ✓ Chapter 01. Code quality.
- ✓ Chapter 02. Abstract Layers.
- ✓ Chapter 03. Other engineers and code contracts.
- ✓ Chapter 04. Error.
- PART 2: IN THE PRACTICE SECTION:
- ✓ Chapter 05. Making code readable.
- ✓ Chapter 06. Avoid surprises.
- ✓ Chapter 07. Making code difficult to misuse.
- ✓ Chapter 08. Making code modular.
- ✓ Chapter 09. Making code reusable and generalizable.
- PART 3: UNIT TESTING:
- ✓ Chapter 10. Unit testing principles.
- ✓ Chapter 11. Unit testing practices.