From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] really Pottering vs UNIX
Date: Thu, 14 Sep 2017 14:15:25 -0700 [thread overview]
Message-ID: <880AF6DC-A8C8-49C3-B874-A0879406BBDD@bitblocks.com> (raw)
In-Reply-To: <CAC20D2M9E0TdK-wnLjMDbDF+qfnWgJCEikBq0RmrT9=oFSGEuQ@mail.gmail.com>
> On Sep 14, 2017, at 1:46 PM, Clem Cole <clemc at ccc.com> wrote:
>
> I think you are actually touching on an idea that has been around humanity for a long time that is independent of the computer field. We call it "good taste." Part of acquiring good taste is learning what is in bad taste, a heavy dose of experience and frankly the ability to evaluate your own flaws.
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.
>
> Part of "good taste" is getting the job done and on time. Being "good enough" and moving on to the next thing. Sun (certainly at the beginning) was pretty good at this idea. The UNIX team clearly got a lot of it right.
Agreed.
[Just nitpicking here! I think we agree on the underlying concept]
next prev parent reply other threads:[~2017-09-14 21:15 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 [this message]
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
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=880AF6DC-A8C8-49C3-B874-A0879406BBDD@bitblocks.com \
--to=bakul@bitblocks.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).