From owner-freebsd-chat Mon Sep 29 19:38:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26588 for chat-outgoing; Mon, 29 Sep 1997 19:38:06 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26575 for ; Mon, 29 Sep 1997 19:37:57 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id WAA02125; Mon, 29 Sep 1997 22:37:36 -0400 (EDT) Date: Mon, 29 Sep 1997 22:37:33 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: "Joel N. Weber II" cc: peter@grendel.IAEhv.nl, chat@FreeBSD.ORG Subject: Re: Microsoft brainrot (was: r-cmds and DNS and /etc/host.conf) In-Reply-To: <199709300039.UAA27996@melange.gnu.ai.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Sep 1997, Joel N. Weber II wrote: > You're more of a designer > than an actual programmer. There are other people that are better > in that, like, well, us. You don't need a computer in the designing > phase. > > I don't think that computer science necissarily teaches good design, > either. At high school level, you'd be right. Not so at a good university, tho. Data structures (one course I'm presently taking) is all about design. Same is true of the operating systems course I took. In fact, if there's one big glaring hole that exists in university classes here, it's style; students are discouraged from reading each other's code, and there is no emphasis on asking students to read anyone else's code (such as some the the freely available code in FreeBSD). I think that reading some of the code in FreeBSD would teach good style, something that is sadly lacking in many students. Course, that just makes me look better. > > At least, none of the computer courses at my high school seem to teach > it adaquately. You can't learn the principals involved in writing a big > program from looking at toy problems that are no longer than a hundred > lines each. It's sort of silly watching a teacher explain how to break > Pascal programs of 50 lines into several procedures. For a program that > short, you can't see the value of procedures. When you're writing a > 15000 line program, you start to see the use of breaking up a program > like that. > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------