From: khm@sciops.net (Kurt H Maier)
Subject: [TUHS] really Pottering vs UNIX
Date: Thu, 14 Sep 2017 20:00:06 -0700 [thread overview]
Message-ID: <20170915030006.GB50485@wopr> (raw)
In-Reply-To: <CAEoi9W4RhN5Tfou4GOpnNMGOWRT5GMXN_TnLQKjgfo8LXAHEkg@mail.gmail.com>
On Thu, Sep 14, 2017 at 09:24:44PM -0400, Dan Cross wrote:
>
> I think a better system than putting us into this rigid hierarchy system is
> to think of programming as somewhat analogous to writing; it requires
> proofreading and good editing. Some authors are better than others;
> practice helps a lot, writers workshops can help, seeking out advise and
> mentorship from more accomplished writers similarly, etc.
It's a good thing real engineers don't put themselves on these
pedestals. We wouldn't have any bridges left.
I'm glad NCEES is making efforts to formalize 'software engineer' as a
class of PE; maybe in another hundred years or so I'll be able to
believe promises that programmers make.
khm
next prev parent reply other threads:[~2017-09-15 3:00 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 [this message]
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=20170915030006.GB50485@wopr \
--to=khm@sciops.net \
/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).