Why Bother with Cucumber Testing?

I think you're mixing Cucumber (the framework) and Behavioural Driven Development up. When you do it right (look at Example Mapping) and focus on rich descriptive scenarios that absolutely never describe the implementation. E.g. "When user clicks submit". It makes writing bug free code a breeze. Thanks to the author for writing an article on what BDD is not though

I remember working at a job where Cucumber was introduced to make test writing easier for the testers (the testers were all non-technical and non-programmers). The reality was that programmers ended up writing the tests because the testers didn't know how to implement step definitions and the functionality was too complicated and varied to allow much reuse of existing step definitions.

Ugh, I'm literally getting my first dose of cucumber today. quite funny to come across this. You still have to "bother" with it if you're migrating tests to a new framework etc

Tldr but I am not sure I really understand the purpose of cucumber still.

Years ago I was on a project where the QA manager insisted on cucumber. But it seemed like just a fancy syntax for tests.

So instead of writing:

clickElement(Selectors.SUBMIT_BUTTON)

You get: When user clicks submit (or given... I am still not convinced there is a difference)

... Okay. Great. You have a new syntax. What problem doesnit solve?