Even though I don't really ever write it anymore, I still have a HUGE softspot for Ruby. It's a great language though definitely one you have to understand and

Even though I don't really ever write it anymore, I still have a HUGE softspot for Ruby. It's a great language though definitely one you have to understand and follow its idioms to not be annoyed by it. Unfortunately, all your coworkers will need to do the same, which is where it can start to fall apart. One thing I don't miss that a significant part of this short article, is RSpec. I was into it at first but it just becomes a burden. When you're writing test descriptions in English, there is very little value gain to gain from the ceremony RSpec has. As for assertions, it turns out that if you're a programmer, `assert a == b` is just as readable as `expect(a).to eq(b)`. Yes, the latter does make it easier to get the arguments in the right order for the output, but that's about it. Otherwise, it's just "neat." You end up thinking a bit too much if you are doing things "the rspec way" which is not something I want in my brain when writing tests. It's also more to learn for onboarding people. Stuff like `expect(a).to be_present` really means `assert a.present?` are head scratchers that I just don't see any value in other than being neat. RSpec is definitely a cool idea and a very well-designed project, but un-necessary by me. It's been 3 years since I've used it daily and haven't found the tests I'm writing these days to be any less readable.