--------------Original Messages:
Date: Fri, 23 Nov 2007 12:58:17 -0500
From: "Roy J. Tellason" <rtellason at verizon.net>
Subject: Re: Teaching kids about computers...
On Thursday 22 November 2007 18:48, Chuck Guzis wrote:
Good point. There is the concept of "depth"
of understanding. Many
people who regard themselves as programming professionals would be
lost without an operating system. Some would be lost without an
assembler. And, sad to say, some would be lost without some sort of
Java facility.
This reminds me of folks I used to run into back in the day that considered
themselves "programmers" -- in dbase!
For some, that's not sufficient. Understanding
how a disk drive
works or what goes on over a TCP/IP connection is essential to them.
Some of us actually enjoy that sort of thing and some just want to be able to
use the end result, or maybe tweak it a bit.
------------Reply:
Well, you've just insulted several thousand professional dBase programmers,
myself included, with your elitist snobbery. I would guess that a competent
dBase programmer would probably have the average small database program
completed and delivered in the time it would take just to lay out, code and debug
the necessary file- and screen-handling routines in most of the other comparable
languages of the day, at least until you'd built up a decent and relevant library.
Tools are developed to make a job easier and do it better; in my opinion taking
advantage of those tools and doing things "the easy way" makes you more
professional, not less.
A programming professional's job is to deliver a product that meets the client's
needs, is well documented and easily maintained, and is delivered on time and
within budget. Knowing or caring about the arcane details of a disk drive or being
able to program an OS-less computer in binary may matter if you're working on
an embedded controller but it's pretty irrelevant if the project is a client
accounting
system for a large financial institution.
What is important is good communication and organizational skills, the ability to
conceptualize, proficiency in the use of whatever tools are appropriate to the job
at hand, and enough humility to give the client what he/she really wants instead
of what he/she *should have*, qualities often lacking in the "hacker"
mentality.
The same applies to the original topic: among the many replies suggesting how
a child *should* learn about computers, I didn't see many suggestions that the
child him/herself might be the best judge and perhaps the best approach might
be to explore what his/her interests are (instead of what yours were), and provide
whatever resources are appropriate and relevant to those interests.
m