And that's the usual fallacy (just ignore the bad stuff).

But if you work with C++ in professional context, you will encounter it somewhere (library, teamate's PR, legacy code, LLM output, book / blog / conference ...). |

You actually need to know the bad stuff to be able to judge it and discard it.