Roelof,
I don't think CRC cards or the GRASP patterns or anything
like that
addresses your immediate needs.�� Based on other questions
of yours it
seems to me that your problem is not *organising* the
responsibilities in an
OO program, but decomposing a problem into
responsibilities in the first
place.�� I think this is perhaps the most important part of
programming, and
the hardest to learn, not least because very few of us are
good at teaching
it.�� We're not very good at teaching it in mathematics
either.�� I do not think
your issues are anything to do with Pharo, Smalltalk, OOP,
or programming
as such.
One symptom of the general problem that I've noticed is
that I see code as
a very fluid sort of thing where pieces can be moved
around and recombined,
while many people think of code as something solid and
rather brittle.
I was thinking of writing up a short description of what I
was thinking for a
RosettaCode example anyway.�� Would that help?
Thank you, Richard. I appreciate your offering
this. I am not a teacher, so your help is truly appreciated!