From: mike.ab3ap at gmail.com (Mike Markowski)
Subject: [COFF] On having a slash
Date: Mon, 13 Apr 2020 10:10:50 -0400 [thread overview]
Message-ID: <c372b770-a323-aa9b-11ee-1bce57479c3f@gmail.com> (raw)
In-Reply-To: <CAC20D2NqzecA-YN6VdEE7QHXtEv19UC0NKaevKYxCL5HK_CqBg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
Showing the usefulness of that, back around 1985 I was in a training
session at Unisys and the instructor told us about his time as a
programmer in Vietnam during wartime. He was part of a group that
modified software for artillery fire control systems in the field, and
each time one of the soldier programmers got orders to return home he
would leave an easter egg in the code. A few days later a message might
pop up saying, "Drinking a beer at home watching tv, wish you were
here??" or little things along those lines. The instructor said one
guy, however, went into the code and globally replaced variable names
with combinations of 1, l, 0, O. Since the 1/l and 0/O were displayed
identically, the programmers didn't find the prank funny. Our
instructor said as he traveled the US training groups, he hoped he would
find the guy. 10 or 15 years later he was still more than a tad angry.
All for lack of slashes and serifs.
Incidentally, living in Austria I was surprised to see ones commonly
written looking nearly like upside down Vs.
Mike Markowski
On 4/13/20 8:38 AM, Clem Cole wrote:
> FWIW -- I still slash both zeros and sevens. I was probably 12 when I
> was taught that trick, plus the print head of an ASR33 slashed zero's
> and 1, l, 7 were all distinct. So sat the time, it seemed cool and
> advanced. Then it just became a habit, and as we know, old habits are
> difficult to change and frankly, I never saw the reason to stop. My
> handwriting is a bit of a mess as it is, so anything I do the make it
> clear has always been considered a good thing by people around me.🤔
>
> On Mon, Apr 13, 2020 at 7:31 AM David Barto <david at kdbarto.org
> <mailto:david at kdbarto.org>> wrote:
>
> Yes. When I took my first programming class at UCSD they
> specifically went through the numbers and alphabet showing the mark
> up and being very careful to go over 0, 1, 7 and O multiple times.
> I’ve stopped slashing my 0, and I still slash my 7. IDK why I
> stopped the one and not the other.
>
> A long time ago, in a universe(ity) far far away.
>
> David
next prev parent reply other threads:[~2020-04-13 14:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 9:01 dave
2020-04-13 11:30 ` david
2020-04-13 12:38 ` clemc
2020-04-13 14:10 ` mike.ab3ap [this message]
2020-04-13 14:21 ` thomas.paulsen
2020-04-13 14:23 ` imp
2020-04-13 12:53 ` paul
2020-04-13 14:12 ` imp
2020-04-13 15:29 ` krewat
2020-04-13 15:40 ` pdagog
2020-04-13 13:21 ` thomas.paulsen
2020-04-13 13:23 ` cym224
2020-04-13 13:36 `
2020-04-13 17:35 ` paul
2020-04-13 22:09 ` dave
2020-04-14 13:34 ` dfawcus+lists-coff
2020-04-14 14:23 ` gdmr
2020-04-13 22:12 ` krewat
2020-04-13 23:21 ` dave
2020-04-14 0:12 ` grog
2020-04-14 2:57 ` paul.allan.palmer
2020-04-13 15:14 rudi.j.blom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c372b770-a323-aa9b-11ee-1bce57479c3f@gmail.com \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).