On Tue, Jan 03, 2006 at 05:06:02PM -0600, L. V. Lammert wrote: > One thing you will *NOT* find in any college courses are system-level > coding principles & practices. OS code is written in C, which is FAR > different than 'application level' coding taught in the vast majority of > courses.
L.V. - the school I went to did have a small handful of courses that did include labs/assignments/projects that included this type of programming. Most of the curriculum was based on more abstract notions, but there are some systems-oriented courses. The undergraduate OS class I took, for example, invovled writing a memory manager and a shell. The graduate OS class I took included a "write your own OS" project. We also had a compiler course that involved writing your own compiler, etc, etc. > Also: > > 1) Read code > 2) Play with code [snip] > et seq. > > I think you get the idea. The only way to write OS code is to basically > teach yourself. While your higher-ed experience may have been different than mine, I totally agree that writing and reading code is the best thing you can do to learn. I might add that one thing that has helped me to figure out what code to read and what to write is to identify something *I* would like to see implemented, and try to implement it myself. bc -- Benjamin Collins <[EMAIL PROTECTED]> 'Broadly speaking, the short words are the best, and the old words best of all.' --- Sir Winston Churchill [demime 1.01d removed an attachment of type application/pgp-signature]
