Re: Timeless Classics of Software Engineering

"Sergio Navega" <snavega_at_intelliwise.com> wrote in message news:<4107cf6a$1_7_at_news.athenanews.com>...
> "Marshall Spight" <mspight_at_dnai.com> escreveu na mensagem
> news:epPNc.177055$IQ4.107932_at_attbi_s02...
> > "Steve Johnson" <stevejohnson1972_at_yahoo.com> wrote in message
> news:949ec44a.0407280704.12141129_at_posting.google.com...
> > > I'd like to hear thoughts on what books, in your opinion, are true
> > > classics in the field of software engineering.
> >
> > I can't vouch for it myself, but I hear a lot of people mention
> > "Code Complete" by Steve McConnell.
> >
> >
>
> I also vote for "Code Complete". It is a remarkable (although excessively
> lenghy) work. If you don't want to face its 850+ pages, there's a smaller
> alternative:
>
> Maguire, Steve (1993) Writing Solid Code. Microsoft Press.
>
> These two books are classics by any definition (and both were written
> by "Steves" and published by Microsoft Press).

_Writing Solid Code_ should be considered only an appetizer. It's got the attitude, but really only a few good examples. It's also strongly oriented towards writing C code. The notion it plugs is "keep trying to improve" and that is good. It was one of the first books I read that had that particular message. Go ahead and read it, but *DON'T* stop after that. Get _Code Complete_ as soon as you can afford the money and time.

The "effective C++" books are excellent also, and available as a package for cheap on CD.
Socks Received on Thu Jul 29 2004 - 19:05:09 CEST