The map is not the territory. You've heard this before and I've quoted it before . The longer quote (due to Alfred Korzybski) from which the snappy soundbite originated adds some valuable context: A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness. I was thinking about that this week as I came to a product new to me but quite mature with a very rich set of configuration options. When I say rich , I mean — without casting any shade, because I have been there and understand — it is set in multiple locations, has extensive potential effects, and is often difficult to understand. For my current project I consider it crucial to get a non-shallow view of how this works and so I began to explore. While there is some limited documentation it is, as so often, not up to date so mostly I worked in the codebases. Yes, plural, because this product spans multiple r...
In simpler times you had to go out of your way to find useless motivational banalities. There'd be an aisle in the shops that you could easily avoid or a spot on the office kitchen wall next to the milk rota that you could stare straight past while the kettle boiled and you fantasised about another job. These days, unless you've vacated social media, it's much harder to avoid having decontextualised generalities with a side of misleading infographics thrust in your face. I scroll hard past that crap but I was reminded of one that comes around frequently the other day. It goes something like these ( 1 , 2 , 3 ): "Ready to unlock your 38X potential in just one year?" "Imagine being offered a 365% return on any investment!" "Every day: 1% stack or 1% slide. You choose." Naturally, "better" and "return" and "stack" are pretty vague and the directions for achieving these easy wins are even more so...