From: Sean Hunter <sean@dev.sportingbet.com>
To: peter revill <arevill@bigpond.net.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: university studies?
Date: Mon, 6 Aug 2001 11:05:04 +0100 [thread overview]
Message-ID: <20010806110504.C4570@dev.sportingbet.com> (raw)
In-Reply-To: <20010801052200.25526.qmail@webmail.com> <Pine.LNX.4.33.0108010801550.9176-100000@infradead.org>
In-Reply-To: <Pine.LNX.4.33.0108010801550.9176-100000@infradead.org>; from rhw@MemAlpha.CX on Wed, Aug 01, 2001 at 08:06:16AM +0100
I did a graduate diploma in Jazz, contemporary and popular music, and further
postgraduate music study. I am now doing my MSc in computer science. Lack of
a degree in computer science (or even a science-related subject!) has never
significantly hindered my career as a developer.
Sean
On Wed, Aug 01, 2001 at 08:06:16AM +0100, Riley Williams wrote:
> Hi Peter.
>
> > 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
>
> Personally, I did "B.Sc. Computer Studies", but I suspect the actual
> course title is irrelevant, and it's the modules you do in the course
> that matter. Here's what I would regard as important:
>
> 1. A thorough knowledge of programming in C. Knowledge of C++
> will help.
>
> 2. Experience of programming hardware will definitely help.
>
> 3. The ability to think logically is a definite advantage, and
> tends to result in 90%+ of your programs working first time.
>
> Additions, anybody?
>
> Best wishes from Riley.
>
> -
> 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/
>
next prev parent reply other threads:[~2001-08-06 10:15 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
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 [this message]
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=20010806110504.C4570@dev.sportingbet.com \
--to=sean@dev.sportingbet.com \
--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