Good Code, Bad Code: Think like a software engineer

I have found this to be a good edition to the software and programming section of my technical library. There are a lot of good tips, examples, and reminders. While none of the chapters came as a complete surprise, the clarity with which each topic is presented helped me to remember important ideas that I put into use almost immediately in my code development tasks.I think that this book will be of greatest use to programmers with at least a few years of professional experience behind them, but I can also see it being useful for CS students and newly hired coders.

Although some parts of this book were review, I greatly appreciated the presentation, writing, and topics covered. I have already started using ideas from this book (e.g. more null checks and better type construction) on the job. I highly recommend this book for advanced beginners, early intermediate coders, or anyone wanting to brush up on principles of software engineering.

if you're an experienced developer, there's not a lot of meat here. Lots of vague examples of "problems" that really boil down to using OO - creating problems and then solving those problems by creating other problems.I imagine this is a useful book if you're just getting started but for me it was largely a miss and I skimmed the latter half.

As someone who's always coaching newer engineers, this book is one of my new go-tos. I think it's relevant for engineers in their first couple years, and what I like about it is that it helps build a shared vocabulary for talking about not just how to write good code, but what good code is. The writing quality is good, and the author includes examples throughout that are detailed enough to be relevant, but compact enough to remain easily digestible.

I originally started to read this book thinking I would likely have heard most of what it contained from other software books, but I found a surprising number of useful things I didn't know/hadn't thought of.

As a technical coach, I love what this book either teaches or reviews. It falls in line with a number of books that started with "Code Complete" (Steve McConnell, 1993!). I love the way that this breaks down specific characteristics about what "good code" looks like, and invites you to understand why we should think a certain way, not just what and how.

I'm QA, not a developer (unless sometimes writing test automation counts). The material presented matches very well, and extends, material to which I've been exposed in both practice as a technically involved QAer as well as too many graduate Computer Science courses. Well worth reading for either reminders of lessons maybe a little faded from memory or new insights.

Would recommend for anyone looking to improve the way they structure / write their code.

A great resource for anyone new to software engineering