My Beef with a few .Net books

[Denaes]

I have purchased a few .net books and I'm sure not as many as some of you all have, but I do have some annoying beefs with some of them.

 

#1. Supporting a company first, you second

Microsoft does this the most. I go to buy a book on OOP and Components and a requirement on it is SQL Server 2000! It doesn't say SQL Server 2000 or MSDE, just SQL Server 2000.

 

Its not a book on databases, but its an assumption that if you want to program componants or OOP in VB.Net you have a $2000 piece of software laying around.

 

Now at some point in this book (which uses a running example) they introduce SQL Server 2000. As its a running example, you cna't go on unless you have it. You can't skip the chapter because the next chapter built on the SQL Server 2000 stuff you just did.

 

It just seems like they purposefully set up the example to make it like this, so you'll need the extra software.

 

#2. Page Fluffing with ASP.Net

 

One example was the same book as above with OOP and Componants. I have a few other books like this.

 

I buy a book about VB.Net, a specific topic, databases, etc. Then randomly there are entire chapters on the basics of the subject and asp.net.

 

Why? Two reasons I can think of. First is page fluffing. Wow, its soo thick! Too bad 1/4th of it is on a subject you don't want. Second would be to get you to read the basics, then tell you "welp, there isn't enough room to cover more than the basics of ASP.Net, buy our ASP.Net book on this subject"

 

Every time I get one of these books, I look over at ASP.Net chapters, then over at my ASP.Net books and shake my head. I swear I have "the basics of ASP.net" enough times over that I think I could fit another 5 (hefty sized) books on the shelf if I cut out those dead weight pages.

 

[/Rant]

[wyrd]

#1: Anything SQL Server can do, MSDE can do. I don't see the big deal there.

#2: A wise man recently told me, "Take what you can use and leave the rest." A books price has nothing to do with how many pages are in it, so what's the big deal? If you feel like delving in to ASP.NET, it's there later.

 

On a related subject, I've gone away from "learn such and such" type books in the last few years. It's all rehash and repeated stuff, just with a different syntax. What I buy now are books that are considered classics and can be applied to any language. ie; Design Patterns, Code Complete, etc. Rarely, if ever, will I buy a book for a specific language, and I only will if it's damn good and highly recommended by NUMEROUS experts in the field, AND referenced in many articles. An example would be Effective C++ by Scott Meyers. Any other type of book is nothing more than toilet paper.

Edited March 9, 2004 by wyrd

[Denaes]

You're right about #1 and #2, but just because you're right doesn't mean I can't complain :p

 

Heck, what kind of list only goes to #2? A pretty sad one that burned out.

 

I'm gonna get Design Patterns, I've got this sweet Refactoring book, but I'm not at a stage in software development that I can use it.

[Robby]

Imagine if they didn't cover ASP.NET in those books :) How many more complaints would there be?

[Joe Mamma]

On a related subject' date=' I've gone away from "learn such and such" type books in the last few years. It's all rehash and repeated stuff, just with a different syntax. What I buy now are books that are considered classics and can be applied to any language. ie; Design Patterns, Code Complete, etc. Rarely, if ever, will I buy a book for a specific language, and I only will if it's damn good and highly recommended by NUMEROUS experts in the field, AND referenced in many articles. An example would be Effective C++ by Scott Meyers. Any other type of book is nothing more than toilet paper.[/quote']

Yeah, I forgot how good design patterns was. I pulled that off the shelf after seeing it mentioned in a thread elsewhere a couple of days ago. been sleeping with it since.

 

Reminds me of a poster I saw at UCSB. . . A hot girl standing out side a door tapping her foot, in the background is a computer nerd hunkered over his computer, caption reads 'why do you think they call it UNIX?'

 

Same idea goes for database books. Buy books on theory, then implementation is a matter of exploring online help.

 

Anyone ever take differential equations? you always spend a lot of time on the general solutions and then a relatively short period applying particular solutions.

 

A great source for books are used book stores in college towns.

 

joe mamma

[irasmith]

I am finding Professional C# to be a great resource. But I am also getting to the point where it's clicking that a lot of things are the same among languages, it's just the syntax that is somewhat different.

 

What I am quickly discovering is how vast and useful a resource msdn is. I realize it will take me a while yet to make the shift from bound books to electronic format, but it is getting easier as I work with it. :)

[Denaes]

I am finding Professional C# to be a great resource. But I am also getting to the point where it's clicking that a lot of things are the same among languages' date=' it's just the syntax that is somewhat different. [/quote']

 

Yeah, its to the point were you only need to learn the syntax to apply what you know.

 

Unless the program is an abberation and does things differently... like comparing VB6 to VB.Net. The really basic fundementals will translate, but many advanced really won't. In this case you'll probobly need a book to help you alone