The author is incorrectly using the term "declarative" when he's really describing "imperative". Stateful OOP is in no way declarative.

It's also unclear what the thesis is. He says to not ask objects about their state, then later advocates for CQRS, which does exactly that.

This seems to fit a couple other things. Functions to "get device capabilities" from device drivers are misguided to some extent. Also, web sites checking capabilities of your browser should be considered an anti-pattern.

I stopped at his argument about getting a string with the contents of RED.

That's why you have a variable. Which is a specific named property of an object.

var lastName ="RED"

Umm. It's his last name?