From: Muzaffer Ozakca <muzaffer.ozakca@bilten.metu.edu.tr>
To: linux-kernel list <linux-kernel@vger.kernel.org>
Subject: [Re: university studies?]
Date: Sat, 04 Aug 2001 13:10:38 +0300 [thread overview]
Message-ID: <3B6BCA1E.F967482A@bilten.metu.edu.tr> (raw)
Crutcher Dunnavant wrote:
>
> ++ 02/08/01 14:36 +0300 - Muzaffer Ozakca:
> >
> > > I don't think, one should learn all the "hot" languages of the day to
> > > become a good programmer. A computer science student should (and will)
> > > learn the theoretical background that lays beneath. Data structures,
> > > graph theory, computational linguistics, compiler theory, OS, AI, so on.
> >
> > Hmm. Thank you, Knuth.
You're welcome :)
> >
> > > Practical studies such as programming projects will let the students
> > > solid the theory. These thoughts are not actually mine, most of the
> > > computer science departments -more or less- follow a cirriculum
> > > appreciating these ideas, I think. However, a kernel (or systems)
> > > programmer should also know basics of microprocessors, interrupts, etc.
> > > and programming in assembly, besides the theory given in a university.
> >
> > They also need to understand large parts of security, and system API
> > design.
Sure things should be added, they were examples..
> >
> > > After getting the theory and completing the understanding by practice,
> > > learning a programming language is just a detail.
> >
> > I disagree. This is equivalent to saying, once I am an archetect, it is
> > easy for me to build houses. Tools and practices take incredible amounts
> > of time to master. Languages take years, and learning the
> > non-algorithmic parts of hacking, like techniques for keeping namespaces
> > clean, or designing APIs to be extensible, or just tracking code; all
> > these are time devouring.
> >
No, I don't say if you know a PL (a tool) then you're a
programmer (or
an architect). Everybody can learn C, it is simple (I like it), if you
consider the reserved words, structs, unions, etc. But not everybody
can
program well or right. Tools, of course, take time to learn, what I say
is background is more important than "one" or a bunch of tools. No
university or school can teach every good tool nor can teach every
aspect of kernel programming.
Experience is the way to be a good programmer, nobody is born
with it.
> > > Always solving problems "C" style, may not be the best approach,
> > > a functional language may better suit the needs -usually not in our course.
> >
> > But, ultimately, computers are procedural. FP helps /prove/ algorithms,
> > but it is a terible way to actually run them.
> >
> > --
> > Crutcher <crutcher@datastacks.com>
> > GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++
> > R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
Muzaffer Ozakca
Researcher/Software Engineer - muzaffer.ozakca@bilten.metu.edu.tr
TUBITAK-Bilten-ODTU - Communications Systems and Comp. Networks Group
ODTU, Ankara, Turkey
http://www.bilten.metu.edu.tr tel: +90-312-210 1311
reply other threads:[~2001-08-04 10:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B6BCA1E.F967482A@bilten.metu.edu.tr \
--to=muzaffer.ozakca@bilten.metu.edu.tr \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®