7 ms·
99 Bottles of OOP
- RankingMember 10y agoI'd like to see the first few pages just to see what the style is like, ala Amazon's "Look inside" function.
- latortuga 10y agoSandi Metz has another book on what I would guess is a similar topic, Practical Object-Oriented Design in Ruby (colloquially, POODR). I found that book to be highly practical to daily development and I expect this to be no different. You might try googling for info about that book or perhaps try the mailing list if you want to find out more before buying.
- acchan 10y agoI'm curious about how the two relate to each other. Is 99B supposed to supplant or complement POODR? Edit: looks like the later. The Products page has a description of both: http://www.sandimetz.com/products/ http://www.sandimetz.com/products/
- noahc 10y agoThis is designed for people who just pull out their credit cards and buy the book. I would expect she and Katrina have a significant number of those folks. No preview needed.
- RankingMember 10y agoI doubt the lack of preview is intentionally some sort of loyalty/"in-crowd" test.
- svec 10y agoI love Sandi's writing - and how they're giving it away for people who can't afford it: "Of course we want you to buy it. It's been years of our lives in the making, and we have bills too. However, if you absolutely cannot afford it, we'll make you a deal. Snail-mail us a postcard, and we'll email you a free copy. A proper postcard, mind you, with a vacation-like scene, and an actual postcard stamp. Hand-drawn postcards are both acceptable and encouraged. The more effort you expend, the better we'll feel about our end of this bargain."
- thecosas 10y agoI love the idea of asking people to show effort (rather than .edu mail address, etc) to get a free copy.
- dopamean 10y agoLike another commenter I think $49 is a bit high for a digital book. However, now that I know that they are giving it away for people who can't afford it I don't mind as much. I can afford $49 for this book even if I think it's a little high. I guess this begs the question: if they dropped the price to $25 would more people be able to afford it and then they wouldn't have to give any away? I wonder what the "correct" balance is there.
- aantix 10y ago$49 for a lifetime software engineering wisdom? You refactor a single class that you never have to revisit again and you've easily paid for this. I will never understand programmer's cost/benefit analysis..
- why-el 10y agoI have to say it largely depends on the location. I have moved progressively to more and more affluent countries (now in my fourth, the US), and it had radically changed how I view "value", especially money. A good book (and I like Sandy's work) will easily pay for itself now that I can actually afford to buy it and 50 dollars is not such an immediate hit on my bank. Before, 50 dollars is a blood rush. :D
- superswordfish 10y agoThat's assuming that what's in this book is exceptional (which you can't tell without a preview). I didn't think that Practical Object-Oriented Ruby was incredible, though it is a well-written tutorial of basic OO techniques. You could spend less than $49 on a couple good used copies of OO classics, or many more if you visit the right used bookstore. And it's not even a hard copy so it is competing with the wealth of good free information online about OOP. I might pay $99 for a hard copy of this, but no way I'd pay $49 for a PDF.
- hacksonx 10y agoThe intro sold the book to me but I'm a bit reluctant to buy it because of the fact that it uses Ruby. I've just started working with Java (straight from University last year) and I've come to realise that in comparison to other OO languages which have evolved their syntax (C# & Python) Java hasn't. I doubt it'll help me with Java. I've already invested in a few books and test engines, mainly for my Oracle certifications.
- diggan 10y agoAfter touching most mainstream languages, I conclude that many of the languages have different syntax and stuff, but the principles are mostly the same. So without having read this book, if it teaches you OOP via ruby, you should be able to apply it in Java as well, but maybe with different syntax but the outcome would be the same
- phillmv 10y agoIunno, what's unique to ruby? I can only think of module mixins. Everything else (blocks, anonymous functions, syntax sugar) can be roughly approximated (i.e. generics), since I strongly doubt the book would use any of the metaprogramming features.
- superswordfish 10y agoOne objection I can think of is that Ruby is dynamically typed. Something that is elegant in Ruby might be a horror in Java.
- tln 10y agoRuby uses messages for methods, allowing cheap delegation; classes can be extended (monkey patched) after definition. I doubt Ruby OOP code would avoid using all metaprogramming, at the very least attr_accessor!
- titanomachy 10y agoTo me, metaprogramming means writing new macros/templates, not just using the "standard" ones.
- hiou 10y agoDoes anyone know how ruby specific this gets? Is it more about general software development while simply using ruby as the vehicle or is it something only ruby specialists would get something from?
- JustinAiken 10y agoSandi came and did the training this book is based on with our company, and the iOS/Android devs got a lot out of besides the Ruby peoples... it uses Ruby, but it's not about Ruby.
- eliah 10y agoUnclear -- is this a physical book, an ebook, or both?
- mattangriffel 10y agoDigital – every button on the page says "Buy Digital Book Now"
- svec 10y agoEbook, provided as an epub download immediately after paying for it. (no pdf or mobi/Kindle files)
- rollover 10y agoDammit, the epub format is such a disgrace for books, especially for those containing code snippets. I've yet to encounter a book that doesn't suffer from being published as epub. I prefer a well formatted pdf that just looks like the printed book, any time.
- glennericksen 10y agoEbook
- kentt 10y agoI would have bought a physical copy, but I don't prefer digital copies of books like this.
- rjeli 10y agoThe book seemed rather short for the price. Definitely had useful information that helped me to understand issues I have with code design. It wasn't worth $50 to me, but may be for other people.
- nerdy 10y agoIt seemed expensive but I bought it anyhow because any small insight into programming or process could easily be worth $50 over time. It's worth noting that the book is incomplete, chapters 5 & 6 are still being written. If I'm able to complete the book in the next day or so I'll post a follow-up.
- bdcravens 10y agoSandi really distills knowledge well. I haven't bought this book yet, but after reading POODR, I'd take 20 pages from her over 100 from another author. I think it's easily worth $50, but I realize we're in an age where we're used to $19 ebooks. Again, I'd pay $100 for her material over somebody else's $19 book. (Not compensated or anything, just a fan of not wasting my time and of awesome materials that help me accomplish that goal)
- nerdy 10y agoThis is a very accurate based on my impression of the 99 bottles book. The information is plainly stated in a way which is so simple it's novel.
- paultannenbaum 10y agoIs it just me, or does $49 seem high for a digital copy? I went to buy it expecting it be somewhere around $20, and then had a bit of sticker shock when I was in the checkout path. I know it took a lot of time and effort and on the author's part, so not saying it isn't worth it, but for a non-physical copy it seems like a pretty steep price. I ended up passing, wonder how many others did the same as me.
- jabagonuts 10y agoThe value of a book is not in its format (digital vs. print), but in the quality of the content and the reputation and relationships the authors have earned due to their previous efforts. And you can always try negotiating a discount via postcard ;-) http://www.sandimetz.com/99bottles/postcard http://www.sandimetz.com/99bottles/postcard
- paultannenbaum 10y agoFor me as a consumer, the format is very much correlated with price. I am always willing to spend more money for a physical copy of a book than the digital version. For them as publishers, it also costs less to come to market with a digital versions, and so should be reflected in the price. I do hear what your saying about value being derived from content, but without a free preview of a couple chapters and a price that I deemed to high, I ended up passing.
- khedoros 10y agoIf I don't think about it, yes, a physical version seems to be worth more, because I feel like I'm actually buying a "thing", rather than just paying for access to information. It feels nicer to know that printing it cost the publisher more to produce; there's a sense of fairness. It's an interesting psychological effect.
- doomtop 10y agoA physical book can also be interacted with and utilized, physically, in ways a digital copy cannot.
- SCdF 10y agoI think it would be helpful to have a sample chapter. I haven't read an OOP book in awhile, but when I did they often had a lot of examples that while reasonably easy to follow didn't actually translate into real world usage (`Car extends Vehicle implements Drivable` or whatever).
- qwertyuiop924 10y agoI might be picking this up. Most OOP design books I avoid, as I have little money and I dislike code with Java Syndrome (heavy focus on inheritence and hierarchy, extreme verbosity, IDE focus, boilerplate with no end in sight, patterns to replace your favorite features from Lisp, java.net.org.lang.lang.really.long.reallylong.import.paths.path, IteratorStrategyProviderFactoryFactoryFactory, etc. yes, I'm exaggerating quite a bit, but there's a reason I avoid Java like the plague), but Ruby tends to play home to practicality, and smalltalk refugees. This is good, and means that this book is a far safer bet than, say, flashy OO design book of the week. Although, I should probably get around to reading Refactoring, and Design Patterns. I've heard those are good...
- stcredzero 10y agoheavy focus on inheritence and hierarchy, extreme verbosity, IDE focus, boilerplate with no end in sight, patterns to replace your favorite features from Lisp, java.net.org.lang.lang.really.long.reallylong.import.paths.path, IteratorStrategyProviderFactoryFactoryFactory, etc. What people need to get their heads around is that everything is about cost/benefit in particular languages in particular contexts/environments. What is the "density of reward" in the edit/test/debug cycle? What is the density of punishments? What comprises the cognitive load and where does it come from? Just because something is good for one thing, doesn't mean it's good for another.
- qwertyuiop924 10y agoWell, yeah, but lighening up on the boilerplate and shortening your import path a bit never hurt anybody. 50 copy-pasted lines don't make your app more flexable. Some of the other stuff I mentioned CAN work and be useful, though.
- stcredzero 10y agoWell, yeah, but lighening up on the boilerplate and shortening your import path a bit never hurt anybody. My point is that often adopting patterns/tools/conventions from other languages results in cruft like that.
- percept 10y agoThe author has good presentations on YouTube, too.
- _zachs 10y ago$49 seems pricy for a digital book, but like said before, it's a small price to pay in the grand scheme of things if you're making a decent salary and if you write much better code after reading it. That said, the broke college student in me is writing a postcard.
- zwilliamson 10y agoCongrats on the release Sandi and Katrina! I am looking forward to reading it! Just purchased and downloaded.
- sambe 10y agoI bought this and regretted it. The writing is nice and friendly, giving clear explanations. They are particularly good at pinpointing and naming problems with design. However, contrary to the expectations I had from the web page, here, and the introduction, it offers little to anyone with experience. I learned almost nothing I didn't know from a few articles about TDD (I don't practice it) and exposition is slow (no different from most programming books). The chapters currently available also have little to do with the OO part of OOP: several "OOP terms" are mentioned and used, but they apply and are applied without the context of multiple classes. I also agree with others about the high price. This seems a lot to me for an ebook, and having got through it very quickly the feeling is only confirmed. Two more chapters are due, as it's a beta, but I doubt this will change my view. I feel it would be a good book for someone new to programming and potentially someone new to TDD. I would still feel obliged to mention value for money to such a person.
- rahilsondhi 10y agoI agree. This book is for beginners - very disappointed.