Skip to content
loading...

re: Goldilocks and the Three Behavioral Patterns - A Design Patterns Intro VIEW POST

FULL DISCUSSION
 

There are some fascinating ideas here but I'm skeptical of the incessant use of classes for everything. Like the PersonStates. Those aren't semantically classes, they're just constant structs with references to each other. the Bear class at the end seems the most superfluous Why would he write a class when literally all he needs to do is call wakeGoldilocksCommand.execute()?

code of conduct - report abuse