Sorry Jeff, but you do not have the authority to make this statement,
People who don't really know much about databases are the ones that frequently suggest the approach [code-first].
That is probably based on a personal bad experience, or even the result of the humor from a bad day. Not a truth that can be universally applied.
I do not want to be rude or disrespectful, but your position is pointless and contradictory, in summary you said that people who suggest the code-first approach "frequently" are not proficient DBAs or they will not revise the generated script properly. So what is left for them? The database-first approach. Implicitly you are suggesting that an individual that is not able to revise a DDL script should write it and model the business logic of an application.
The OOP languages have a lot more instrumentation for business logic modeling and prototyping (e.g. abstract classes, interfaces, empty methods and etc.). For the sake of productivity DBAs can and should take advantage of generated DDL scripts considering the inalienable responsibility of revising it and applying the improvements and corrections that are invariably necessary.