your Second Brain is a privateknowledge collection designed to serve a lifetime of learning andgrowth, not just a single use case

But it is more difficult in a world of manuscriptsthan in the era of printing to evaluate what constitutes a note—that is, a piece ofwriting not meant for circulation but for private use, say, as preparatory toward afinished work

a principle I use is: If you have an accessor, use the accessor rather than the raw variable or mechanism it's hiding. The raw variable is the implementation, the accessor is the interface. Should I ignore the interface because I'm internal to the instance? I wouldn't if it was an attr_accessor.

Also, Sandi Metz mentions this in POODR. As I recall, she also advocates wrapping bare instance variables in methods, even when they're only used internally. It helps avoid mad refactoring later.

But suddenly I'm using a raw instance variable, which makes me twitch. I mean, if I needed to process has_sauce before setting at a future date, I'd potentially need to do a lot more refactoring than just overriding the accessor.

The Object.getPrototypeOf() method returns the prototype (i.e. the value of the internal [[Prototype]] property) of the specified object.

In short, I think the idea of public methods being actions works just fine as an api.

OER matters not because textbooks matter. OER matters because it highlights an example of how something central to our public missions, the transfer of our foundational disciplinary knowledge from one generation of scholars to the next, has been co-opted by private profit. And OER is not a solution, but a systemic shift from private to public architecture in how we deliver learning.