Practical techniques for writing code that is robust, reliable, and easy for team members to understand and adapt.. Summary in good code, bad code youll learn how to -     think about code like an effective software engineer     write functions that read like well-structured sentences     ensure code is reliable and bug free     effectively unit test code     identify code that can cause problems and improve it     write code that is reusable and adaptable to new requirements     improve your medium and long-term productivity     save yourself and your team time the difference between good code or bad code often comes down to how you apply the established practices of the software development community. In good code, bad code youll learn how to boost your productivity and effectiveness with code development insights normally only learned through careful mentorship and hundreds of code reviews. Purchase of the print book includes a free ebook in pdf, kindle, and epub formats from manning publications. About the technology software development is a team sport. For an application to succeed, your code needs to be robust and easy for others to understand, maintain, and adapt. Whether youre working on an enterprise team, contributing to an open source project, or bootstrapping a startup, it pays to know the difference between good code and bad code. About the book good code, bad code is a clear, practical introduction to writing code thats a snap to read, apply, and remember. With dozens of instantly-useful techniques, youll find coding insights that normally take years of experience to master. In this fast-paced guide, google software engineer tom long teaches you a host of rules to apply, along with advice on when to break them. Whats inside     write functions that read like sentences     ensure your code stays bug-free     how to sniff out bad code     save time for yourself and your team about the reader for coders early in their careers who are familiar with an object-oriented language, such as java or c . About the author tom long is a software engineer at google where he works as a tech lead. Among other tasks, he regularly mentors new software engineers in professional coding best practices. Table of contents part 1 in theory 1 code quality 2 layers of abstraction 3 other engineers and code contracts 4 errors part 2 in practice 5 make code readable 6 avoid surprises 7 make code hard to misuse 8 make code modular 9 make code reusable and generalizable part 3 unit testing 10 unit testing principles 11 unit testing practices