david.doolin
Dated, but useful principles, notable obsessing over preparation and quality. I've used this to land clients.
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.
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.
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.
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.
Short read and pretty good high level overview. Something to read after having a higher level view of the whole conflict.
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.
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.
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.
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.
This is a reference book, and I've referenced it several times, hence counting it “read.”
I found it instructive to examine the proportion of casualties with respect to branch of service. The USMC served well. Semper Fi.
Wikipedia reports an unnamed military analyst repudiates Abrams' claim of Clear and Hold strategy.
Lamar Plain was conducted during Abram's tenure, which I'm reading about in “A Better War.” I'm curious whether that book will mention this operation, and how Abram's envisioned this operation in his One War program.
It took me two tries to get through this one.
The best I can some up with is “thought provoking,” as it's making me think about a number of assumptions currently held as gospel in both corporate HR and the talent industry.
While the book seemed to start from a science-based point of view, by the end I'm having to classify it as a polemic (because the author has a PhD, otherwise I'd call it a bit of rant). I did not find much immediately actionable material which will help me tune my current hiring pipeline.
However, the author exposes so many absurdities in current thinking that I'm inclined to a future reread.
Good material, a little light for me on immediate demonstration, will be rereading to extract actionables.
Fast read, but very little exploration useful for applying Boyd's concepts. The big take home for me: “Do your homework.”
Not currently in the audience for this at the moment; style did not resonate with me. Material seems good, will consider rereading in the future.
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.
I've had this for ages, and find myself referring to it more and more often of late. It's really nice just getting the definition for a term without having to wade through 1. search results, then pointless discussion surrounded by advertising on typical web pages.
I read this several years ago, and, paging through it again just now, want to reread it. Absolutely fantastic.
