I didn't like it. It was too much theory based without enough recognition of practice. I and a very small company used it ~25 years ago. It wasn't good enough & we eventually dumped it. I can't give you reasons why as it was too long ago but I don't have a good memory of it.
I do remember of the Eiffel book that Meyer was a bit too keen on emotive arguments over factual.
I'm not talking about OOP. Meyer was hard on pre and postconditions (which were massively oversold), but these were functionally no more than assertions. He had holes in his object system. He had holes in other parts of the type system. He was not an object zealot IIRC.
It could have been interpreted badly - I was just pointing out he was from the generation that pushed OOP everywhere similarly to FP folks these days, and downplaying the problems inherent in Eiffel/OOP, similarly to FP folks that see no major issues in their own space. A single sentence can't explain the massive contribution he had on programming and Agile anyway.
I misinterpreted it because there's a rash of people who post throwaway dismissive stuff (always without any justification) and yours looked exactly like that. So, my apologies. I'd suggest a mention of your personal experience would have been valuable here; actually getting lessons off the guy is a big deal.
I do remember of the Eiffel book that Meyer was a bit too keen on emotive arguments over factual.