From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] really Pottering vs UNIX
Date: Thu, 14 Sep 2017 22:42:55 -0700 [thread overview]
Message-ID: <d92047c5a36c6e72bd694322acb4ff33e3835f9f@webmail.yaccman.com> (raw)
In-Reply-To: <CAEoi9W4RhN5Tfou4GOpnNMGOWRT5GMXN_TnLQKjgfo8LXAHEkg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
More to do with a sense for quality. Often developed through
experience
(but not just that). I think what we need is a guild system for
programmers/engineers. Being an apprentice of a master craftsman is
essential for learning this "good taste" as you call it.
I guess I'm not so totally against guilds per se. 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). 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.
Maybe a guild is a bit too stuffy, 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.
I don't think I would have found this in a book or long midnight hours
hacking away...
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170914/3013a1fc/attachment.html>
next prev parent reply other threads:[~2017-09-15 5:42 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 [this message]
2017-09-15 13:26 ` Clem Cole
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=d92047c5a36c6e72bd694322acb4ff33e3835f9f@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).