I've got to disagree, because representing everything as an object involves a serious amount of cognitive overhead. You're limiting yourself to things that can be represented as objects and still make sense, plus you've got to write the code to make your ideas fit into the object box (methods, interfaces, this, public private etc).

I've been working on some networking protocols, and I started by modeling each node as an object. Seemed to make sense. But there's a lot of overhead. Send, receive methods etc etc, and then you've got to instantiate them and then collect the data from the objects afterwards to see how the network did. I switched my code over to being a bunch of stateless functions that operate on a network graph and stuff got a lot less verbose.

This is not necessarily always the case, but I would hate working in an environment where I was forced to always use a very specific metaphor for my work.