From owner-freebsd-doc Sun Jan 23 23:28:38 2000 Delivered-To: freebsd-doc@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 19E4E15111; Sun, 23 Jan 2000 23:28:20 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id CAA32844; Mon, 24 Jan 2000 02:28:24 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 24 Jan 2000 02:28:23 -0500 (EST) From: Chuck Robey To: "William A. Maniatty" Cc: msmith@FreeBSD.ORG, FreeBSD-doc@FreeBSD.ORG, asmodai@wxs.nl, freebsd-hackers@FreeBSD.ORG, grog@lemis.com, maniattb@cs.rpi.edu Subject: Re: Learning the FreeBSD Kernel In-Reply-To: <200001240716.CAA02016@richard.cs.albany.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 24 Jan 2000, William A. Maniatty wrote: > Both Chuck Robey and Mike Smith have some points, but that won't > stop me from giving my opinion :-). Mike is correct that experience is > key to being a solid systems software developer, who writes device drivers. > Now the next question is how can someone get experience? By developing > systems software (which by the way they should only do if they have > experience at it :-)). > > Traditionally there are two approaches: > 1) Have a friend available and bug them for help when you get stuck :-) > 2) Read the documentation. > 3) Read the code and lose a whole lot of productivity without certainty > of figuring it out on your own. > 4) Dismiss the whole problem as unmanageable and throw your > weight behind a more productive project. I know where Mike's coming from. Wait until the next guy posts on the list "I don't really know how to program, but please tell what 'C' is, and how to write a device driver". We had a pretty nasty flamewar over that maybe (I think) 9 months ago, and it still hurts folks, to be accused of conceit, when the guy was asking a grossly unanswerable question, and wouldn't believe it couldn't be boiled down to a 4 paragraph "device drivers for dummies" thing. Mike wants to avoid dealing with a horde of folks like that. I can't really blame Mike, it's impossible to make people understand that you can't boil everything down to a 30 second sound bite. BUT I still wish there was a map to interfaces. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message