Difference between revisions of "Talk:3003: Sandwich Helix"
Line 29: | Line 29: | ||
The first rule of communication is "Always talk about communication." [[User:RegularSizedGuy|RegularSizedGuy]] ([[User talk:RegularSizedGuy|talk]]) 15:36, 25 October 2024 (UTC) | The first rule of communication is "Always talk about communication." [[User:RegularSizedGuy|RegularSizedGuy]] ([[User talk:RegularSizedGuy|talk]]) 15:36, 25 October 2024 (UTC) | ||
− | + | : I'm pretty sure the first rule is "Context Matters" and "Helix Sandwich" conveys that by the lack of it.[[Special:Contributions/172.70.126.228|172.70.126.228]] 20:28, 27 October 2024 (UTC) | |
− | I'm pretty sure the first rule is "Context Matters" and "Helix Sandwich" conveys that by the lack of it.[[Special:Contributions/172.70.126.228|172.70.126.228]] 20:28, 27 October 2024 (UTC) | ||
Possibly the best real-world example of this is the Biblical Book of Revelation. It's an example of apocalyptic writing, which means 'writing in code', not necessarily 'talking about the end of the world' (although it does also do that, which is where the confusion has arisen). And that's sort of the point - most of the context which would enable us to understand the book properly has been lost. For example, scholars generally accept that the 'beast' whose number is 666 is a reference to a real historical person, and that the number 666 is supposed to tell the reader that person's identity... but there's no consensus on who that person is. The fact that there is evidence to suggest that the number was altered (from 616) by later editors doesn't help. [[Special:Contributions/172.70.90.109|172.70.90.109]] 05:47, 28 October 2024 (UTC) | Possibly the best real-world example of this is the Biblical Book of Revelation. It's an example of apocalyptic writing, which means 'writing in code', not necessarily 'talking about the end of the world' (although it does also do that, which is where the confusion has arisen). And that's sort of the point - most of the context which would enable us to understand the book properly has been lost. For example, scholars generally accept that the 'beast' whose number is 666 is a reference to a real historical person, and that the number 666 is supposed to tell the reader that person's identity... but there's no consensus on who that person is. The fact that there is evidence to suggest that the number was altered (from 616) by later editors doesn't help. [[Special:Contributions/172.70.90.109|172.70.90.109]] 05:47, 28 October 2024 (UTC) |
Revision as of 17:02, 28 October 2024
Sandwich presumably refers to compliment sandwich, but I don’t know what the helix is. --Galaktos (talk) 14:03, 25 October 2024 (UTC)
- I think sandwich refers to the context itself, as in, the context of something is both what is before that and what is after. 172.71.222.236 15:19, 26 October 2024 (UTC)
- Maybe Models of communication#Dance? --Galaktos (talk) 14:12, 25 October 2024 (UTC)
- The word "Helix" may be a reference to the previous comic. CategoryGeneral (talk) 14:36, 25 October 2024 (UTC)
- The moral of this story is "People will try to find meaning in anything, even things that are directly stated to be meaningless."172.70.176.43 23:01, 26 October 2024 (UTC)
That title text makes me reasonably upset. What nitwit decided "smart quotes" AND incompatible default encodings was a good idea? 172.70.174.203 16:45, 25 October 2024 (UTC)
- I'm inclined to blame Apple because Mac OS Roman (1989) postdates Windows 1252 (1987). Both of these extended ISO 8859-1 with curly quotes but chose different code points. Davidhbrown (talk) 03:26, 28 October 2024 (UTC)
- Hi, Davidhbrown. Speaking of curls, note the difference between "Mac OS Roman" and "Mac OS Roman". And come into the edit to see how neater the source is! (Even compared to [[]]s marked to go to "wikipedia:..."). HTH, HAND. 172.68.205.151 11:33, 28 October 2024 (UTC)
It seems that something like this could happen over time naturally if it's a saying that "everyone knows" so that real meaning stops being said, and then eventually that bit of information disappears. For instance KISS "Keep it simple, stupid" has a negative connotation, but the idea is very sound. So people keep saying the abbreviation but stop saying the full version, and new people hearing it the first time might get the basic idea without knowing why. Eventually even the meaning could be lost, and it could just become something that people say without knowing why. Maybe the assume the ancient designers and engineers liked to make out when they saw complex things. Andyd273 (talk) 17:58, 25 October 2024 (UTC)
- Frums - Options 162.158.91.14 04:18, 26 October 2024 (UTC)
- KISS Keep it simple, stupid was originally keep it stupid simple. An emphasis, not an insult. --PRR (talk) 05:12, 26 October 2024 (UTC)
- "Keep it stupid, simple" still sounds like an insult. These Are Not The Comments You Are Looking For (talk) 03:07, 27 October 2024 (UTC)
- https://en.wikipedia.org/wiki/KISS_principle#Origin --PRR (talk) 18:31, 27 October 2024 (UTC)
- Note for recent editors... You can use that link as
{{w|KISS principle#Origin|~insert some link text here~}}
to get it to look like ~insert some link text here~. I think we're getting some new users who seem not to be aware of this handy template, and/or being lazy about it. (I also indented your comment, for the circumstances.) 162.158.74.118 19:01, 27 October 2024 (UTC)
- Note for recent editors... You can use that link as
- https://en.wikipedia.org/wiki/KISS_principle#Origin --PRR (talk) 18:31, 27 October 2024 (UTC)
- maybe keep it stupidly simple? 172.69.34.176 (talk) 04:56, 27 October 2024 (please sign your comments with ~~~~)
- Nope. That's a sweet thought, but comes from the US Navy in 1960, and indeed started as "Keep it simple, stupid!". 172.68.71.159 15:52, 28 October 2024 (UTC)
- "Keep it stupid, simple" still sounds like an insult. These Are Not The Comments You Are Looking For (talk) 03:07, 27 October 2024 (UTC)
Infodump: To my knowledge the only five encodings resulting in "’" for utf-8 encoded "’" are Windows-125X where X is an even decimal digit. 162.158.154.78 (talk) 15:25, 27 October 2024 (please sign your comments with ~~~~)
This is similar to the number 42 in Hitchhikers Guide to the Galaxy, in that the answer is known, but the exact question (=the context) has been lost. See HHGG Fandom wiki --Cavac (talk) 09:33, 28 October 2024 (UTC)
Minor grammatical point; please feel free to skip this. I just tweaked "a communication technique [...] which meaning has not been lost." to "a communication technique [...] whose meaning has not been lost.". "Of which the meaning" or "whose meaning" both work, but the latter is less contrived. People keep forgetting that "whose" can refer to objects, as well as to people. <https://en.wiktionary.org/wiki/whose#Determiner>
The first rule of communication is "Always talk about communication." RegularSizedGuy (talk) 15:36, 25 October 2024 (UTC)
- I'm pretty sure the first rule is "Context Matters" and "Helix Sandwich" conveys that by the lack of it.172.70.126.228 20:28, 27 October 2024 (UTC)
Possibly the best real-world example of this is the Biblical Book of Revelation. It's an example of apocalyptic writing, which means 'writing in code', not necessarily 'talking about the end of the world' (although it does also do that, which is where the confusion has arisen). And that's sort of the point - most of the context which would enable us to understand the book properly has been lost. For example, scholars generally accept that the 'beast' whose number is 666 is a reference to a real historical person, and that the number 666 is supposed to tell the reader that person's identity... but there's no consensus on who that person is. The fact that there is evidence to suggest that the number was altered (from 616) by later editors doesn't help. 172.70.90.109 05:47, 28 October 2024 (UTC)
I don't think the "helix" refers to software development. It could be about the helical model of communication, which conveys communication as a non-linear process.
This is perhaps a joke with these simplistic "rules" of communication (like the compliment sandwich), which portray communication as something much simpler.
If we assume that communication is complex and non-linear (as the helical model of communication portrays), we might conclude that there is no such thing as "#1 rule of communication"; something that could be observed by the misuse of the "compliment sandwich". 172.70.47.87 (talk) 15:38+, 25 October 2024 (please sign your comments with ~~~~) (Assuming all the above is the same IP editor, tweaking their comment.)
- Ah, thank you. I added the Spiral (for development) because I couldn't find the Helix one (for communication), and I thought this was the best linkable item out there. Now I know it's Helical, I've found it and I can put a link on your addendum and perhaps remove my original 'placeholder'. That's collaborative communication! ;) 172.70.91.77 15:56, 25 October 2024 (UTC) (PS, please sign Talk contributions, and wikilinks are a good idea if you can add them. ;p )
I took the opposite point from that in the explanation so far, especially with the title text: Even if the encoding is wrongly specified, it's possible to figure out what was meant by some sequence of bytes. I imagine the teacher using a different nonce every time to make the point about the #1 rule of communication: Words don't have inherent meaning, it is acquired through use. (Though if I'm the only one with this interpretation it kind of sinks my idea I guess). Hcs (talk) 10:18, 26 October 2024 (UTC)
Is it not true that Cueball could basically be demonstrating the #1 rule, i.e. context is important, and that sometimes language is self-repairing? 172.69.214.109 14:42, 26 October 2024 (UTC)
- <=========>
- ∞∞∞∞∞∞∞
- <=========>
Helix sandwich. That did not render well.- TenGolf 172.69.58.19 18:20, 27 October 2024 (UTC)
- Like it now? (There are better ways, but is the simplest.)172.68.205.134 18:28, 27 October 2024 (UTC)