david.doolin
Very short (22 page) thesis summarizing material also covered in Before The Quagmire. Provides a handy timeline for the events of the Fall of 1960, and a good reference list of original sources much of which is drawn from JCS archives.
I'm not a fan of points-based estimation, but if that's whats on the table, here's how to handle it.
A note for my future self. At the time of writing, I am using this edition for quotes and as reference material for a different physics hobby project. As the man himself recommends, always start from first things, and in physics, the first thing is Physics.
I have not read enough to rate it.
First read 12+ years ago, just finished 2d read. The general principles of selling haven't changed very much and the book is very convenient for me.
However, I do not recommend this to general readers.
Dated, but useful principles, notable obsessing over preparation and quality. I've used this to land clients.
Much to my surprise and delight, I'm working on a greenfield Rails application at the moment, one which doesn't warrant a full-blown SPA system such as React. Hence, review the Views! I've had this book since (probably 2012) but had not read it thoroughly then. On this read, I was pleasantly surprised to find several useful techniques I either missed or had forgotten. I did skip the chapters on CSS and Javascript, I'm working in Rails 8 right now, and those are too out of date. I can recommend this book for 1. when working with legacy system dating from Ruby 2.x and Rails 3/4, 2. when you find it super inexpensively (or acquire as a gift) and need some Rails View referesher, and 3. if you're the sort of person with the space inclination to have an extensive, historically relevant Rails library.
Ten years post publication, Braithwaite's material is still generally relevant and very much worth spending some time with. The Ruby Programming Language has advanced considerably since publication, and it would be an interesting exercise to bring the examples up to Ruby 3.3 syntax.
This was a reread. It's a nicely short book, covers some very basic things, and was a good review. I learned (or relearned) a couple of tricks. Would be a good book for a Rails beginner to read along with an LLM for discussion.
This is a really handy book to have for reference. I have the paperback version. I use it cross-check GPT results and as a guide for going deeper into specific topics.
I skimmed some of it, read some of it in detail, did not work through the examples. However, I picked up enough to know where to look for more when necessary. In particular, at 10 years post publication, threads seem to be as popular as ever. This will be the first reference I reach for the next time I need to work with threads.
The book almost surely warrants an updated edition. A big job to be sure.
I am very pleasantly surprised at how much I liked this book. The authors succinctly present at least the 80% of what matters in software engineering management. Despite that, it is not a long book. What works for the book is coverage. Each chapter closes with an outstanding list of references, most of which I have, and have read. What works against it is an almost telegraphic approach. People unfamiliar with the material may not realize how much breadth is covered in the book, and how much depth is summarized in any particular section.
Short read and pretty good high level overview. Something to read after having a higher level view of the whole conflict.
I have the 4th edition, which apparently is not listed here on Goodreads, which is fine.
This was a 3 semester sequence in college. I've legit done around half the exercises in that book, and I believe we covered nearly every chapter over the three semesters. For me it's a decent bridge between the classic “solve all the integrals” exemplified by, say, Goursat, and more modern texts attempting to build deeper intuition.
I'm listing it as a reference now as I've actually been back into it several times over the last year to sanity check GPT output, and I expect to continue using it on a regular basis in the future.
I do not understand why Higgins' reporting on Vietnam has been completely bypassed. None of her observations or perspectives are reflected in the current narrative of that war. Perhaps had she not tragically passed away in early 1966, she might have had an influence on the conduct and direction of the proceeding years.
A very small book with excellent illustrations of very narrow interest. While the ambush deterrent factor may or may not have been large, I'm sure if I was a convoy driver I would want one or more of these trucks along for the ride. Regardless of combat efficacy, a gun truck had to be good for morale.
Read maybe 30%, skimmed most of the remaining, was not able to finish it in detail.
I suspect people who like this book will really, really like it, and people who don't, really won't.
My rating of 3 reflects my point of view coming from the engineering side. That is, I did not feel this book was overly helpful when I was working mostly as an individual contributor. I might well find a reread more useful being more on the management side.
I've read a vast amount of literature over the decades, nearly none of which is listed on my page here on Goodreads. But this was my first read of Heart of Darkness. Fully intend on rereading.
This collection of writings provides a basic understanding of systems thinking, starting from first principles. It's referenced in a number of management and engineering books I've read, and references in blog posts are starting to appear more frequently.
One thing to understand about systems thinking is that it's really, really hard to get right in complex systems, and especially when people form an integral component of the system.
