Live data from Hacker News

Why's (Poignant) Guide to Ruby (2004)

poignant.guide

41–50 of 213 posts

Re: Why's (Poignant) Guide to Ruby (2004)

#41
post #38

this is legitimately the worst programming book i've ever read. i wanted to get started with ruby back in 2009, and everyone was praising this book. i got it, read the first few chapters, and got bored out of my mind. it meanders and takes forever to get to the point. in the end, i never really learned ruby, and the main cause was this book.

A book which stops you learning Ruby is in fact an excellent book.

Ruby is good :)

Re: Why's (Poignant) Guide to Ruby (2004)

#42
post #12

I've always felt this was a singular achievement, one which perfectly captured the spirit of its author, the community he inhabited, and a particular zeitgeist in programming and on the internet. The need for various other authors to attempt to replicate it for other languages by creating rambling, twee books with wacky titles and comic characters of their own, I've frankly found a bit sad and underwhelming. It's a b…

i don't think it was even funny the first time.

reading this stuff i always feel like the author is trying to keep my attention by jiggling some car keys in front of my face as if i am an infant. this applies to books like learn you a haskell too.

Re: Why's (Poignant) Guide to Ruby (2004)

#43
post #38

this is legitimately the worst programming book i've ever read. i wanted to get started with ruby back in 2009, and everyone was praising this book. i got it, read the first few chapters, and got bored out of my mind. it meanders and takes forever to get to the point. in the end, i never really learned ruby, and the main cause was this book.

A book which stops you learning Ruby is in fact an excellent book.

touche.

Re: Why's (Poignant) Guide to Ruby (2004)

#44

this is legitimately the worst programming book i've ever read. i wanted to get started with ruby back in 2009, and everyone was praising this book. i got it, read the first few chapters, and got bored out of my mind. it meanders and takes forever to get to the point. in the end, i never really learned ruby, and the main cause was this book.

[deleted]

Re: Why's (Poignant) Guide to Ruby (2004)

#45
post #7
post #2

I don’t think about _why every day the way I used to, but I still miss his presence.

his influence on a whole generation of developers was priceless

It is not an exaggeration to suggest that If I - liberal arts graduate focusing on technology in academia - had not found _why's guide, I would never have believed I had a mind capable of doing code professionally. I will be celebrating my 10th year in the industry soon.

Re: Why's (Poignant) Guide to Ruby (2004)

#46
post #22

Earlier quoted context omitted.

This about sums up most Monty Python and Rick & Morty references as well. A lot of nerd/hacker culture falls into this kind of recognition of unique humor and wit, then squeezing every little drop of joy out of it until it's as empty as a Garfield cartoon.

Au contraire: https://garfieldminusgarfield.net (Although I suppose a case could be made for it still being "empty.")

I prefer `lasagnacat` for my existential/surreal Garfield riffs.

https://www.youtube.com/channel/UC2AQkHXNVA-w9FA1m9VqO7A

My favorite may be this one, a one-hour single-take monologue about finding the meaning of life in a Garfield strip.

https://www.youtube.com/watch?v=NAh9oLs67Cw

Re: Why's (Poignant) Guide to Ruby (2004)

#48

this is legitimately the worst programming book i've ever read. i wanted to get started with ruby back in 2009, and everyone was praising this book. i got it, read the first few chapters, and got bored out of my mind. it meanders and takes forever to get to the point. in the end, i never really learned ruby, and the main cause was this book.

I saw it as more of an art piece than a practical learning experience; the latter being more exemplified by books such as K&R and the like.

Re: Why's (Poignant) Guide to Ruby (2004)

#49

this is legitimately the worst programming book i've ever read. i wanted to get started with ruby back in 2009, and everyone was praising this book. i got it, read the first few chapters, and got bored out of my mind. it meanders and takes forever to get to the point. in the end, i never really learned ruby, and the main cause was this book.

it has its place. If you already know how to code but are learning Ruby, it's not a good book (lot of fluff). But if you are learning to code for the first time it's good. This was my case in 2012.

I admit the comedy style is showing its age–a little cringe now.

Re: Why's (Poignant) Guide to Ruby (2004)

#50
post #12

I've always felt this was a singular achievement, one which perfectly captured the spirit of its author, the community he inhabited, and a particular zeitgeist in programming and on the internet. The need for various other authors to attempt to replicate it for other languages by creating rambling, twee books with wacky titles and comic characters of their own, I've frankly found a bit sad and underwhelming. It's a b…

Don't forget Ruby. Only Ruby (and Clojure) can liberate the mind enough to facilitate such flights of fancy :)
Post reply on HN