mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: peter revill <arevill@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: university studies?
Date: Thu, 2 Aug 2001 10:26:19 +0200	[thread overview]
Message-ID: <20010802102619.A6387@khan.acc.umu.se> (raw)
In-Reply-To: <20010801052200.25526.qmail@webmail.com>
In-Reply-To: <20010801052200.25526.qmail@webmail.com>; from arevill@bigpond.net.au on Wed, Aug 01, 2001 at 01:22:00PM +0800

On Wed, Aug 01, 2001 at 01:22:00PM +0800,  peter revill wrote:
> Ok, im 16 and looking at heading into uni as soon as ive finished year
> 12.  I'm gonna head on over to uni, i am wondering out of curiosity
> what courses most kernel developers have done? im going to do either
> bachelour of computer science, or information technology, at a later
> date, when im done my studies im hoping to help with kernel
> developing, mozilla etc. etc., so i was wondering what people would
> consider the course that gives you "kernel development" sort of
> skillset-mindset any feedback is appriciated, please CC it to my mail
> adress at arevill@bigpond.net.au 

I'd suggest deep studies of Zen/Chan-buddhism, Taoism, logic,
discrete mathematics, c-programming, haskell or ml (functional
programming), algorithm-theory & analysis and a course or two
in operating-system theory.

At least, that's what I've studied. One could argue it didn't help
a lot, but...

The best thing of all to study is source-code, though. Learn from those
who already mastered the art of programming. I've head that Plan 9 is
available as source-code. Get it and learn from the best.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

      parent reply	other threads:[~2001-08-02  8:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01  5:22  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
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 [this message]

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=20010802102619.A6387@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=arevill@bigpond.net.au \
    --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®