Thanks, yeah, it's interesting. We're not through the whole project, so it may still mess up ;) But so far so good.

I think the key point here is that I'm not trying to learn Ruby. We're trying to get a single project done in Ruby. I'm the best person to do the project, Ruby is the best language to do it in, but I don't know Ruby.

If I was trying to learn Ruby, this is not the way I'd do it, and I'd go up the learning curve as normal, writing all those shitty PRs and making all the mistakes as normal. As you say, there are no shortcuts to achieving understanding.

And the plot thickens... :-)

Now I can reply to your message (can't say why I couldn't before, so moving on).

Below is the added content in the event you were unaware of the previous message edit. In addition are three other resource links which may be beneficial to your project. The last one, nokogiri[3], is least likely to be applicable in general but is simply too cool to omit.

  Why’s (Poignant) Guide to Ruby[0]

0 - https://poignant.guide/book/chapter-1.html

1 - https://www.rubyguides.com/2018/07/rspec-tutorial/

2 - https://github.com/cucumber/cucumber-ruby

3 - https://nokogiri.org/