[ale] [Fwd: James Gosling will be speaking at the Sept. AJUG meeting]

Christopher Fowler cfowler at outpostsentinel.com
Wed Aug 30 17:21:17 EDT 2006


On Wed, 2006-08-30 at 10:11 -0400, Step wrote:
> You've hit on a big problem: how the heck do newbies know where to get
> good code examples?  The only relatively safe approach I can think of
> is to buy expensive books, but even that doesn't approach a guarantee.
> The other option is to hang out in IRC or sitepoint.com or something
> and ask people, but then the person who doesn't know any better has to
> wade through people's opinions and try to make a decision on something
> they're not qualified to understand....ah well, so much for the
> information age.  ;) 

The "Classics" by Richard Stevens, K&R.  That is a place where you get
on how to write good code.

Another method is looking at source code.  Look at OSS projects. Large
projects that don't usually commit patches from crap code. 

When it comes to the "right way" many people have their own opinion.
The best advice for a newbie is to write as much code as possible.  Make
mistakes and learn from those mistakes.  You can only get so much from
school.  




More information about the Ale mailing list