Alphaville wrote: ↑Sun Apr 04, 2021 12:01 am
but the problem seems to be (and i see @jacob explaining and reexplaining not to do this) people are getting hung up on the "points" as a kind of scoreboard or a game system or a morality chart, rather than grasping the... gestalt,
hence... remove all the columns and use cartoons instead
To me the Wheaton Scale seems pretty contained in scope which I think makes it more digestible. Plus, like you said, it's a cartoon, and it more/less tells a story. The ereWL summary seems broader in scope.
One of the challenges with a table format is that a reader (reasonably) looks for correlation across rows as well as down columns. I'd guess many of us (certainly me) self-assess at significantly different levels across the columns.
I think for some of us the mapped progression down some of the columns doesn't reflect our personal evolution. Just as an example, the vacation/activity column is one I have a lot of trouble identifying with.
So my table consuming mechanism produces an array of scores with one of the allowed values being N/A. I dunno what to do with the array other than to mentally file it away as a curio.
If I'm understanding jacob correctly it's
a path rather than
the path. I'm not into permaculture myself, but I suspect someone could find blueprints to get a pretty good jump on the process. The breadth of ere means, to borrow a common phrase from bogleheads.org, "Many roads lead to Dublin."
Maybe a good activity for those who's skin the ereWL table has gotten under would be to make a personalized version of it (whatever rows and columns you want). Going from your zero point to your today point and trying to understand what happened under the hood might a) give you better understanding/context of the global ereWL table as well as suggest a road map that's meaningful to you. Or, you can file the whole subject away as a curio. Chances are your subconscious will chew on it and if you open the curio cabinet one day down the road you might have an aha moment that unlocks another piece of the puzzle.
A big part of my past job responsibilities was to be sort of a translator between people who wallowed neck deep in all the technical details all the time and those a step or two or three higher in the management chain. The latter often being intelligent and highly competent people, just in a position where they have to look from the outside in rather than the inside out. So I totally get the instinct of wanting to see a clear, distinct takeaway. I think there's just to much breadth in scope.