Nope. It's not even about being a "better developer". It's about being (and becoming) a master developer.
>If you are hired as a developer you may be useful to have a "smorgasbord" of experiences, depending on the role.
Then that company doesn't need a master, but just a generalist that can wear many hats with some competence.
>Someone who has only used C++ but 'gone deep' might be less useful here.
Which is neither here, nor there. The advice is how to become a master programmer (e.g. in C++), not how to become useful in a company that needs devs to tackle many roles.