* Ian Wienand <[EMAIL PROTECTED]> spake thus:
> 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.
good point!
> 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
<snip>
thanks, I'm always on the lookout for good books. I'll add these to the
list.
> Once you've got some idea jump in and start programming something.
<grin>
have been for 5 years now - which I guess is part of my point: I'm not
a beginner programmer, I know how to program reasonably well. I was
hoping to find any methods that would take me beyond reasonable into
excellent...
books help with that - and I devour them regularly; programming helps,
but it's a bit of a blind search. I figured that looking at smart code
would also help.
I fully agree that actually writing it is better than reading it, but I
also figured there'd be no harm in reading good stuff on top of all the
rest :)
Cheers and thanks,
Taryn
--
This .sig temporarily out-of-order.
We apologise for any inconvenience
- The Management
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
