{"product_id":"9781617298936","title":"Good Code, Bad Code: Think like a software engineer","description":"\u003cb\u003ePractical techniques for writing code that is robust, reliable, and easy for team members to understand and adapt.\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003eSummary\u003cbr\u003e In \u003ci\u003eGood Code, Bad Code\u003c\/i\u003e you’ll learn how to:\u003cbr\u003e \u003cbr\u003e    Think about code like an effective software engineer\u003cbr\u003e     Write functions that read like well-structured sentences\u003cbr\u003e     Ensure code is reliable and bug free\u003cbr\u003e     Effectively unit test code\u003cbr\u003e     Identify code that can cause problems and improve it\u003cbr\u003e     Write code that is reusable and adaptable to new requirements\u003cbr\u003e     Improve your medium and long-term productivity\u003cbr\u003e     Save yourself and your team time\u003cbr\u003e \u003cbr\u003eThe 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 you’ll learn how to boost your productivity and effectiveness with code development insights normally only learned through careful mentorship and hundreds of code reviews.\u003cbr\u003e \u003cbr\u003ePurchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.\u003cbr\u003e \u003cbr\u003eAbout the technology\u003cbr\u003e 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 you’re 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.\u003cbr\u003e \u003cbr\u003eAbout the book\u003cbr\u003e \u003ci\u003eGood Code, Bad Code\u003c\/i\u003e is a clear, practical introduction to writing code that’s a snap to read, apply, and remember. With dozens of instantly-useful techniques, you’ll 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!\u003cbr\u003e \u003cbr\u003eWhat's inside\u003cbr\u003e \u003cbr\u003e    Write functions that read like sentences\u003cbr\u003e     Ensure your code stays bug-free\u003cbr\u003e     How to sniff out bad code\u003cbr\u003e     Save time for yourself and your team\u003cbr\u003e \u003cbr\u003eAbout the reader\u003cbr\u003e For coders early in their careers who are familiar with an object-oriented language, such as Java or C#.\u003cbr\u003e \u003cbr\u003eAbout the author\u003cbr\u003e \u003cb\u003eTom Long\u003c\/b\u003e 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.\u003cbr\u003e \u003cbr\u003eTable of Contents\u003cbr\u003e \u003cbr\u003ePART 1 IN THEORY\u003cbr\u003e 1 Code quality\u003cbr\u003e 2 Layers of abstraction\u003cbr\u003e 3 Other engineers and code contracts\u003cbr\u003e 4 Errors\u003cbr\u003e PART 2 IN PRACTICE\u003cbr\u003e 5 Make code readable\u003cbr\u003e 6 Avoid surprises\u003cbr\u003e 7 Make code hard to misuse\u003cbr\u003e 8 Make code modular\u003cbr\u003e 9 Make code reusable and generalizable\u003cbr\u003e PART 3 UNIT TESTING\u003cbr\u003e 10 Unit testing principles\u003cbr\u003e 11 Unit testing practices","brand":"Manning","offers":[{"title":"Default Title","offer_id":46439140950257,"sku":"9781617298936","price":49.99,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0674\/5433\/7265\/files\/9781617298936_p0.jpg?v=1765883873","url":"https:\/\/shop.barnesandnoble.com\/products\/9781617298936","provider":"Barnes \u0026 Noble","version":"1.0","type":"link"}