Bourbaki dangerous bend symbol
en.wikipedia.org
en.wikipedia.org
https://github.com/rybak/scripts/blob/master/config/ps1_noti...
It works together with very dumb script in $PATH, which prints a readme file if one is found in the current directory.
https://github.com/rybak/scripts/blob/master/commands/readme
After reading your comment I still don’t think one of the lines is a road’s edge?
Do you know if either interpretation is the official one?
EDIT: Just took another look and I see it now. The line near the car’s left tire doesn’t actually align with that tire!
Easy to clear up (by Australian/NZ folks), do these show up on straightaways? Are they mirrored to indicate which direction the bend is going to be?
> The line near the car’s left tire doesn’t actually align with that tire!
could be:
- pointing to and suggesting the other wheel on the right side, more like materialising an envelope of the skid marks instead of realistic skid marks themselves
- stylisation of the overall 180 rotation, emphasising the overall spin out of control movement
I've always interpreted it as a cartoony car version of what your legs do when slipping on ice - sliding out from under you in random directions.
But yeah, the design makes this very hard to recognise and suggests more the "two crossed tire lines" interpretation which gives this a cartoonish, tongue-in-cheek vibe, which is completely unfitting.
Good idea, bad execution I think.
I think the cartoonish feel actually helps, though, as it makes it more memorable.
When it rains anywhere, the road is always slippery for the first half hour or so because of accumulated car gunk that has to wash off. So if it rains infrequently and briefly, it's not much of an overstatement to flatly say "slippery when wet".
But this means that the symbol can excuse, or even incentivize writing exactly such "dangerous bend" passages instead of e.g. structuring the argument or the learning order differently, so the thinking trap doesn't occur in the first place.
I think it' a very useful didactic technique to show common misconceptions of something, or popular simplistic but wrong interpretations of a concept. But then it's important to explain what exactly the misconception is and why it is wrong, and not just put a "beware, here be misconceptions" sign next to the introduction of the concept.
(disclaimer: am son of two Mathies who met in a combinatorics lecture)
Given I'm an IT bod: it will be the ones pertaining to name resolution and ... time.
+1. Also curious to see where it should be positioned on the page. The wiki page says it goes in the margin. I tried searching github for 'u2621' to find examples but couldn't spot any rendered examples yet (only code).
- "brace yourself, here be dragons"
- "til now it was a bit of a treadmill, but that's a part you probably don't want to fast read"
- "on the surface this may look innocuous but there are tricky subtleties that you may not want to overlook"
/*
* You are not expected to understand this.
*/Many readers hereabouts read English as a second language. It took me roughly two seconds to ensure that my meaning was spelled out. This response, rather longer 8)
https://www-cs-faculty.stanford.edu/~knuth/diamondsigns/diam...
They don't ? (well, not a full arrowhead, but wedged head and tail)
https://evs-profilepics.s3.amazonaws.com/production/cdr/imag...
(The important bit being that it indicates which direction is the first turn going to be)
> to mark passages tricky on a first reading or with an especially difficult argument.
When I try this (on macOS) echo -e "\u26A0" it gives the 'triangle with an exclamation mark in it' icon (i.e. https://imgur.com/a/SJbl67s).
I think there's no exact unicode equivalent of the dangerous bend symbol?
I'm fully aware Russia does not have a literal 'Z' glyph.
It’s a fun little game I have with a circle of text friends. Almost everything you see there was updated last week. Sometimes you’ll find something that was updated a few months ago. Two years is epic.
// Hold on to your butts...