How I Learned to Stop Worrying and Love the State Machine

Re:How I Learned to Stop Worrying and Love the State Machine by aryehof on Wednesday February 28, 2018 @07:12AM (#16482428)

The original advice was to use nouns to "identify candidate classes", rather than "determine classes".

Sadly when confronted with a problem, the majority of programmers can get no further than writing down lots of nouns, perhaps dozens of them, with no idea how to combine the few actually required into an object-oriented design.

OO isn't fundamentally about messaging. That is incorrectly assuming that object-orientation began with Smalltalk, Alan Kay and Dan Ingalls. Smalltalk's "messaging with objects, all the way down" approach largely ended with its popular use and the widespread adoption of Java. Java's object model is entirely based on Simula (James Gosling Sept 2017).

[ Parent | on HN ]

Re:How I Learned to Stop Worrying and Love the State Machine by e12e on Thursday March 01, 2018 @01:32PM (#16494701)

The battle is lost now, but I think it's unfortunate that we use "OO" both for class oriented domain modelling, and object oriented state persistence with message passing for composition.

Technically the latter is about object instances, the former about object/class (data/domain) modelling.

[ Parent | on HN ]