Not knowing too much about sound engineering myself, I tried comparing it to software engineering. At the end of the day what matters is your output and learning along the way. It seems the author has a gripe with people calling themselves producers. If someone said I can’t call myself a software engineer until I had interned at XYZ company and understood Kubernetes, Docker, Typescript, AWS, Rust, etc. I would say ok…
Maybe a better software analogy here would be to compare producers to product managers. Great PMs are truly gold, but the PM role’s technical requirements are nebulous, and there are plenty of PMs who don’t know how to write code, and don’t know how to craft a good product, and don’t know how to communicate with customers effectively, essentially having no skills required for the job, but able to talk convincingly to enough of the right people to get hired and keep their jobs.