Easily this was the idea that maybe OOP wasn't the solution to everything. It's not exactly a paradigm, but more of a repudiation of one. I still write a majori

Easily this was the idea that maybe OOP wasn't the solution to everything. It's not exactly a paradigm, but more of a repudiation of one. I still write a majority of my code in classes. But you can see a lot of other influences as well: the command pattern (which is more procedural I would say), a lot of LINQ expressions (which are pretty functional), and a whole lot of dumb records being passed to dumb functions (which I got from data oriented thinkers). Anyway the point is, it's not just one paradigm which has made a difference for me. It was realizing that there isn't one paradigm. I can freely import influences from all of them, use them where appropriate, and get a benefit from all of them. Including OOP, but not only OOP.