From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] Design and Workmanship
Date: Mon, 15 Sep 2003 09:59:37 +0300 [thread overview]
Message-ID: <81132473206F3A46A72BD6116E1A06AE479C67@black.aprote.com> (raw)
applause, no, standing ovations
Hardly possible to express it more clearly. Almost any sane adult can be taught good workmanship
by trial and error; whereas good design indeed seems to be something, mm, 'ethereal', that some
have and some don't. Unfortunately the classic universitas-style CS education (at least here
in Estonia) tries to mold everybody into an designer slash scientist. This per se isn't that bad, but
in the process workmanship gets lost because nobody ever gets their hands dirty. The net result
is that alot of horrible code floats around, designed by people who don't have it, programmed
by people who don't have it.
Tiit Lankots
next reply other threads:[~2003-09-15 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 6:59 Tiit Lankots [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-15 6:33 Laura Creighton
2003-09-15 8:41 ` boyd, rounin
2003-09-15 16:02 ` Dan Cross
2003-09-15 19:52 ` boyd, rounin
2003-09-16 15:13 ` Dan Cross
2003-09-16 15:18 ` mirtchov
2003-09-16 23:44 ` boyd, rounin
2003-09-15 14:42 ` Wes Kussmaul
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=81132473206F3A46A72BD6116E1A06AE479C67@black.aprote.com \
--to=t.lankots@aprote.ee \
--cc=9fans@cse.psu.edu \
/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).