| I love Ruby and have been working with it full-time since 2014. Additionally, I would say that my taste in humor and art tends towards the wacky and whimsical, and even twee sometimes I suppose. But, like you.... maaaaaaaaaan, to say that book/guide didn't connect with me would be an understatement. Among other issues I had, is that it begins (I'm paraphrasing) by describing Ruby as a seamless and intuitive extension of one's brain. Now, I love Ruby, and think it's admirably friendly, but you still need a solid handle on basic computer science concepts to be good at it, and maaaaan there's a lot of unintuitive Ruby stuff out there and you hit it extremely quickly as soon as you venture outside of the standard library... and sometimes even before. Even conventions like affixing ? and ! to methods is just a convention and ! is barely even a convention: it can mean "mutate in place" or "this method is going to try and do a thing, but might throw an exception instead so be ready to catch it" (ala ActiveRecord's #save!) But... I am glad others like _why's work and get value from it. |