I guess by now it's pretty settled down and unanimous that SOLID is an extremely bad way to organize your code, and that Clean isn't very good and has about the same odds of helping or harming you.
But extending the complaint to all acronyms isn't helpful. ACID, OLAP, EBITDA, etc are perfectly good names with clear meanings that can be easily discovered.
I'm not sure you can even get majority agreement of what SOLID code looks like, let along unanimous agreement on it being bad.
You don't know many c# devs, then.
I have met exactly 1 developer that both followed the Microsoft recommended practices and didn't think they were bad.
His legacy is making code brake even now.
> I guess by now it's pretty settled down and unanimous that SOLID is an extremely bad way to organize your code
Hardly. Not settled down, still less unanimous.
"Extremely bad"? What are the actual material consequences of the decision? Relate it to business outcomes
Why are you talking to the OP like they're a bot?