public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muzaffer Ozakca <muzaffer.ozakca@bilten.metu.edu.tr>
To: linux-kernel list <linux-kernel@vger.kernel.org>
Subject: Re: university studies?
Date: Thu, 02 Aug 2001 14:36:38 +0300	[thread overview]
Message-ID: <3B693B46.585CC416@bilten.metu.edu.tr> (raw)
In-Reply-To: <Pine.LNX.4.33.0108020438460.8206-100000@terbidium.openservices.net>


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.
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.

After getting the theory and completing the understanding by practice,
learning a programming language is just a detail. Always solving
problems "C" style, may not be the best approach, a functional language
may better suit the needs -usually not in our course.

As far I could see, kernel programming (talking about the whole)
requires the use of computer science, heavily.


Ignacio Vazquez-Abrams wrote:
> 
> On Thu, 2 Aug 2001, Riley Williams wrote:
> 
> > One thing I will add, from long experience: If you learned BASIC
> > first, then learn Pascal BEFORE you try to learn C or C++ as you'll
> > come out a much better programmer than trying to learn C or C++
> > directly after BASIC.
> 
> Once you've finished learning BASIC, unlearn all the crap you won't need for
> Pascal.
> 
> Also, add Python for good programming style (or replace BASIC and Pascal
> with it entirely if you're feeling brave) and some sort of FP to sharpen your
> pure algorithmic skills. If you don't want to go into full-fledged Lisp, then
> take a look at XSLT.
> 
> PHP is good if you're going to do anything web-oriented, but it's very similar
> to C, so...
> 
> Also, Perl doesn't hurt, but I've found that it isn't entirely neccessary if
> you can deal with sed and awk, which I also suggest you pick up.
> 
> --
> Ignacio Vazquez-Abrams  <ignacio@openservices.net>
> 
> -
> 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-02 11:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01  5:22 university studies?  peter revill
2001-08-01  7:06 ` Riley Williams
2001-08-01 11:46   ` Erik Mouw
2001-08-01 14:12     ` Ian Stirling
2001-08-01 19:31       ` Anders Peter Fugmann
2001-08-02  7:24     ` Riley Williams
2001-08-02  8:48       ` Ignacio Vazquez-Abrams
2001-08-02 11:36         ` Muzaffer Ozakca [this message]
2001-08-02 15:45           ` Crutcher Dunnavant
2001-08-02 17:12           ` Ignacio Vazquez-Abrams
2001-08-02 15:42       ` Daniel Phillips
2001-08-02 18:13       ` Brad Stewart
2001-08-02 18:23         ` Alan Cox
2001-08-02 18:46           ` J . A . Magallon
2001-08-03 10:05           ` Matthew Gardiner
2001-08-03 10:51             ` szonyi calin
2001-08-03 13:02               ` asmith
2001-08-03 14:32                 ` szonyi calin
2001-08-05 11:32                   ` asmith
2001-08-05 14:09                     ` szonyi calin
2001-08-05 14:19                     ` (OT) " Chris Wedgwood
2001-08-06 10:05   ` Sean Hunter
2001-08-02  3:39 ` Rik van Riel
2001-08-02  8:26 ` David Weinehall

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=3B693B46.585CC416@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