Best Practices from 'Hard Code'

I picked up a book while I was at PDC. it is a best practice book for software developers. And it is excellent. I really like Steve McConnell and the stuff that he writes but "Hard Code" from Eric Brechner (writing as the deliberately provocative "I M Wright") is just as solid on technique, and has a really good line in snappy titles and no-nonsense talk. (one of the early articles is called "Development schedules, flying pigs, and other fantasies")

The content is based on articles written by Eric for in-house magazines at Microsoft. The intention was to spark debate about what you should be doing when you try to construct systems out of software, and the best ways to make sure you do it right.

If you write code for a living, or are a student learning how to write code for a living, or just want to find out what makes developers go tick (and probably cuckoo as well) then this is a great book to get. Strongly recommended.

Comments

[JDog - Joel Parkey]

Sounds like a good book.

Good news is that Battleships is almost finished!

I may require help generating Random numbers as my C# doesn't like it too much :(

So far so good Rob.

[Shawn]

Interesting, I have the Code Complete Second Edition, some of it at this point in my development is over my head, but have read many good things about the book.

I may have to look into this book also then....