One of the best ways to get better at Rails (and Ruby) is to read more code
Today I read some code that had some impressive chaining and some Ruby I've never seen in the wild -- the "then" method.
Whenver I'm learning a new language, or brushing up on a language I haven't used in a while, the first thing I do is write a small testing library.
Then I learn it by writing basic tests.
You know what's cool? 👀
@russolsen just announced that he and @baweaver will do a second edition of 📕 Eloquent Ruby at @pragprog.
It's nice to see that the
@ruby community gained so much traction again recently. 😊
#rubylang #books #PragmaticProgrammer #ruby #rails #rubyonrails #RubyProgramming
I'm thrilled to announce that Brandon Weaver and I have just kicked off work on a second edition of Eloquent Ruby, to be published by our friends at The Pragmatic Programmers. The idea is to keep the basic structure of the book the same while updating it to Ruby as it is used today. While we are all excited, let me repeat something that Brandon and I tell each other every day: This is a big project and we want to do it right. So while the second edition is on its way, it is going to take time, time measured in months. But Eloquent Ruby, Second Edition is on its way. | 14 comments on LinkedIn
Calling all Rubyists! We are looking for help verifying third-party libraries on JRuby 10! I've opened an issue to track that process, and provided links to snapshot JRuby builds you can use to verify your own code. Please help us verify JRuby 10!
I wrote something about Ruby’s documentation. If you’re at #RubyConf this week and want to improve it together, come talk to me 🙂
https://st0012.dev/a-rdoc-maintainer-s-view-on-ruby-s-documentation
As someone who genuinely cares about Ruby's developer experience, I've been thinking about Ruby's documentation for a while, especially after I became a maintainer of RDoc. And I'd like to share my thoughts on the current state of Ruby's documentatio...
My kid is finally old enough so we just bought a mess of PC parts to build a nice desktop PC. I told him no screen restrictions but that we're going to install Linux so he has to install and maintain everything. Oh, the agony and ecstasy to come...
Anyone know of a blog/writeup on how to create an install which is somewhat resilient to breakage (guest VMs/containers, emergency partition, dual boot, etc)?
I think I'll name the PC "bikeshed".