Creating applications for clients - what does thoughtbot do?

In an article on BDD, you cite this article. I understand that writing Gherkin scenarios is a bit fluffy, and the application I’m contracted to develop for a client will pay me whether I have these scenarios written or not. However, I’ve worked with the client closely and we’ve written out the user stories to translate to Gherkin scenarios.

Is the article suggesting that thoughtbot doesn’t write human-readable Gherkin specs (and that they’re generally overkill)? Where can I find your BDD best practices for contract work?

I have not read it but you can look inside their book ‘The playbook’.

I can’t seem to find a blog post on the full reasons for the switch. In general we prefer to just use rspec request specs + capybara for our acceptance tests. You gain most of the benefits of Gherkin if you extract everything into properly named methods. This means less dependencies for new developers to learn, and less context switching when writing specs.