The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] really Pottering vs UNIX
Date: Fri, 15 Sep 2017 09:26:04 -0400	[thread overview]
Message-ID: <CAC20D2OYbqL-zygWsmpypo88k5scHWyn3=sjf=akwSp57eCNcA@mail.gmail.com> (raw)
In-Reply-To: <d92047c5a36c6e72bd694322acb4ff33e3835f9f@webmail.yaccman.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3224 bytes --]

below...

On Fri, Sep 15, 2017 at 1:42 AM, Steve Johnson <scj at yaccman.com> wrote:
>
>
> I guess I'm not so totally against guilds per se.
>
> ​Dan I hear you, but I think I agree with Steve here..​




>  Since I believe that programming (at least is a profession) is a service
> industry, I think that doesn't come naturally to a lot of otherwise bright
> people (including, I might add, me).
>
> ​Amen.. I think this is the key point, I was trying to make.  What I
called 'good taste' was being show examples.   Reading others code.
Thinking about a problem.    Think about simple, ugly CS problems and why
they are hard or ugly.  Your moral equiv of cleaning a few latrines.

​




>  Back when I was writing FORTRAN, I was working for a guy with very high
> standards who read my code and got me to comment or, more usually, rewrite
> all the obscure things I did.  He made the point that a good program never
> dies, and many people will read it and modify it and try to understand it,
> and it's almost a professional duty to make sure that you make this as easy
> as possible for them.
>
>  Amen
​ !!!   ​
I worked as an assembly programmer supporting TSS and York/APL when I first
broke in.
​  I had exactly the same experience.  Were as one of my friends did not.

I'll not name the person here because he's a good friend and many of you
know him.   But a one-time officemate of mine at start up and MIT grad​
were working on a system. And I was b*tching at him about something he had
written.   It was marvelous code, quite ingenious.   His comment was "Well
I only comment stuff I did not understand."


I look at him agast.   I said... "'Fred' you are on the smartest guys I
have ever known.  There is not much you don't understand.   Comment it for
us mortals please."

This was a lesson I was taught very early in my career (there are usually
spelling and grammar errors because of my dyslexia, but my comments are
usually parsable and understandable 40 years later - even by me).



>
> Maybe a guild is a bit too stuffy,
>
> ​Right - the image seems heavy weight, which is not what I intend.



> but being mentored by someone with their head screwed on straight, and
> consequently making a point to seek out excellent examples of the
> programming art and learn from them had a profound effect on my skill as a
> programmer and my career.
>
> ​Exactly!!!​

>
> I don't think I would have found this in a book or long midnight hours
> hacking away...
>
> ​And to those people that took the time to guide and teach me, I am
forever indebted. My hope is that I am able to pay them by helping the next
generation a small amount, and trying to keep their ideas and spirits alive
in those new programmers.  I hope the new programmers do continue to write
new things and extend the art, but as I said recognise, they do their work
the shoulders of some wonderful and great people starting with tools and
ideas that hopeful they understand they learned from those masters.

Only time will tell. ​


>
> Steve
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170915/c366af6a/attachment-0001.html>


  reply	other threads:[~2017-09-15 13:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 20:46 Clem Cole
2017-09-14 21:15 ` Bakul Shah
2017-09-15  1:24   ` Dan Cross
2017-09-15  1:39     ` Wesley Parish
2017-09-15  3:00     ` Kurt H Maier
2017-09-15  5:42     ` Steve Johnson
2017-09-15 13:26       ` Clem Cole [this message]
2017-09-15 19:10       ` Chris Torek
2017-09-15 19:19         ` Paul Winalski
2017-09-16 18:05         ` [TUHS] How do we learn about maintainability - was " Toby Thain
2017-09-16 19:12           ` [TUHS] Maintainability, Guilds, RMS, etc. all lumped into one Jon Steinhart
2017-09-17 18:50             ` Bakul Shah
2017-09-18 14:44           ` [TUHS] How do we learn about maintainability - was Re: really Pottering vs UNIX Clem Cole
2017-09-15  6:43     ` [TUHS] " Bakul Shah
     [not found] <mailman.1021.1505464341.3779.tuhs@minnie.tuhs.org>
2017-09-16 20:09 ` David
2017-09-18 14:17   ` Clem Cole
2017-09-18 14:23     ` David

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='CAC20D2OYbqL-zygWsmpypo88k5scHWyn3=sjf=akwSp57eCNcA@mail.gmail.com' \
    --to=clemc@ccc.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).