On Wed, Sep 21, 2005 at 03:55:06PM +1000, Benno wrote: > On Wed Sep 21, 2005 at 13:09:52 +1000, Taryn East wrote: > >what nobody else is going to bite? :( > > I think this is because great code is code is due to the absence > of suckiness rather than the presence of brilliance. At least > IMHO.[1]
Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it. From SIGPLAN Notices Vol. 17, No. 9, September 1982, pages 7-13. So the best code is code you look at and say "is that it - I could have done that", even though you probably couldn't have. If you're interested in systems, I'd suggest starting with an intermediate step of some good books first, the obvious ones that spring to mind are Lions' Commentary on UNIX 6th Edition, with Source Code - John Lions Advanced Programming in the UNIX Environment - Stevens TCP/IP Illustrated - Stevens Linux Kernel Development - Robert Love (top levels of the kernel) IA-64 Linux Kernel - David Mosberger (how an architecture really works) Once you've got some idea jump in and start programming something. Follow Rusty's driver tutorial from LCA, write toolbars for Mozilla, fix that annoying bug in Gnome. You'll soon see how things hang together, and identify what is good and what isn't. It's like learning a musical instrument; you can read about guitar technique (and that's certainly part of it) but you really need to sit there and strum the thing to get any good. -i
signature.asc
Description: Digital signature
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
