When writing a book as in your C# in Depth, how do you strike the balance between recycling old material and covering the language's newest features? For example do you leave out stuff that was done in a particular way under an older C# version since under a newer version alternative ways of going about the same thing have been introduced?