From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] Comments on "C"
Date: Sun, 4 Sep 2016 10:03:15 -0700 [thread overview]
Message-ID: <d56e080af9cdc376a0a5916207b033bb.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1609030701590.78806@aneurin.horsfall.org>
Before I headed off to my first summer job, my mother, who was working as
a programmer, gave me some good advice: "before you throw away a deck of
cards, put a rubber band around it...". Saved my butt twice that
summer...
Incidentally, I figured the other day that a Petabyte of data, if punched
onto punched cards, would make a deck that was 6 times higher than the
distance to the moon...
Steve
> On Thu, 1 Sep 2016, Norman Wilson wrote:
>
>> Programming well requires a lot of thought and care and careful
>> rereading, and often throwing half the code out and re-doing it better,
>> and until we can have a programming community the majority of whom are
>> up to those challenges, we will continue to have crashes and security
>> vulnerabilities and other embarrassing bugs aplenty, no matter what
>> language is used.
>
> I think I saw that in CACM: "Prepare to throw out half your code, because
> you will anyway".
>
> Then there was the time I saw a Uni student, when, ambling down the
> corridor at UNSW Comp Sci, he tripped and spilled the entire deck of
> cards; after laughing for a while, I helped him to put them through the
> reader-sorter (fortunately, they were sequenced, I think).
>
> When I think back on some of the code I wrote, I still shudder... Mind
> you, this was back in the days of the IBM-360 and the PDP-11, and I'd only
> just graduated, m'lud.
>
> --
> Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
> suffer."
>
next prev parent reply other threads:[~2016-09-04 17:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 9:17 Norman Wilson
2016-09-01 15:11 ` Clem Cole
2016-09-01 21:47 ` Tim Bradshaw
2016-09-02 0:11 ` Mary Ann Horton
2016-09-02 7:10 ` Steve Simon
2016-09-02 10:02 ` Steve Nickolas
2016-09-02 14:13 ` Random832
2016-09-02 21:23 ` Dave Horsfall
2016-09-04 17:03 ` scj [this message]
2016-09-05 13:07 ` Ron Natalie
2016-09-04 22:24 ` Nemo
-- strict thread matches above, loose matches on Subject: below --
2016-09-09 2:43 Doug McIlroy
2016-09-08 13:30 Noel Chiappa
2016-09-08 14:22 ` Tony Finch
2016-09-08 19:20 ` Ron Natalie
2016-09-08 22:06 ` Dave Horsfall
2016-09-09 3:02 ` Ronald Natalie
2016-09-09 6:06 ` Diomidis Spinellis
2016-09-09 21:15 ` Mary Ann Horton
2016-09-08 12:35 Doug McIlroy
2016-09-09 17:07 ` scj
2016-08-28 18:21 Dave Horsfall
2016-08-29 0:37 ` Marc Rochkind
2016-08-29 0:42 ` Larry McVoy
2016-08-29 1:54 ` Steve Nickolas
2016-09-08 1:19 ` Blake McBride
2016-08-29 3:16 ` Greg 'groggy' Lehey
2016-08-31 10:02 ` Tim Bradshaw
2016-08-31 12:59 ` John Cowan
2016-08-31 13:32 ` Ron Natalie
2016-08-31 14:37 ` John Cowan
2016-08-31 13:57 ` Brantley Coile
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=d56e080af9cdc376a0a5916207b033bb.squirrel@webmail.yaccman.com \
--to=scj@yaccman.com \
/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).