Sponsored links


Valid XHTML 1.0!
Valid CSS!



Product: Book - Paperback
Title: ASP.NET Website Programming: Problem - Design - Solution, C# Edition
Publisher: Wrox
Authors: Marco Bellinaso, Kevin Hoffman
Rating: 5/5
Customer opinion - 5 stars out of 5
Best detailed tech book ever read


Don't want to repeat what others have said. I am going to add something new here.
1. Please read this book from cover to cover, even you are not interested in other topics like news, forum and etc. New concepts and techniques are poping up right and left along the reading. Many techniques are introduced and implemented only once in different parts of the book, so read on and get the whole picture.
2. Pay close attention to SitePrincipal and SiteIdentity which I found most difficult to grasp, but once you understand it, they are pretty cool ideas.
3. I have tried very hard to make the most of VS studio to do the job for me instead of doing a lot of manual coding like almost all ASP.NET books are doing. There are so many tips out there to make the best use of the IDE to minimize the amount of manual coding one has to do. Some of my tips:
a. You can drag and drop style sheets into your page and save your typing
b. Your best layout control is still Table. Don't use grid layout.c. You can place controls on the designer, so the VS IDE will generate necessary aspx code for you. If you are not satisfied with the way IDE placing the code, you can just cut and paste it into another place.
I also read programming asp.net by J Liberty. It's a fine introductory book, you may want to read that one before you read this book.



Product: Book - Paperback
Title: The Ultimate History of Video Games: From Pong to Pokemon--The Story Behind the Craze That Touched Our Lives and Changed the World
Publisher: Three Rivers Press
Authors: Steven L. Kent
Rating: 4/5
Customer opinion - 4 stars out of 5
Lots of good stories, little to pull it together


An exhaustive account of the business of games, with plenty of inside information. Not much theory or analysis about why any of it happened, but that's not important for the probable audience of this book.
If you want to know about how the various genres developed, this is not the book. If you want to review the history of companies and remember some good old games, this one is great.



Product: Book - Paperback
Title: Learning Perl, Third Edition
Publisher: O'Reilly
Authors: Randal L. Schwartz, Tom Phoenix
Rating: 5/5
Customer opinion - 5 stars out of 5
Great for unix and c types


I purchased Learning Perl as a unix user and novice C progammer. As a webmaster, I needed to learn more about Perl so I could write and debug cgi scripts in the language. Coming from my unix/c background, the text was very clear and easy to understand. Schwartz does a great job of using code snippets to explain what he says.



Product: Book - Paperback
Title: How to Break Software: A Practical Guide to Testing
Publisher: Addison Wesley
Authors: James A. Whittaker
Rating: 5/5
Customer opinion - 5 stars out of 5
If you really want to learn testing, buy this book.


This book is part of the new wave of testing books that challenge not only the conventional wisdom about test process, but also challenge conventional wisdom about how to teach and write about testing. People who prefer testing textbooks that preach paperwork and process will be shocked, shocked, to discover that there are a lot of us who think it's a tester's job to find important bugs fast. We want books that give us strategies for actually finding problems. Paperwork and process help some, but not enough. We need something more. We need test-designer-sits-down-at-the-keyboard know-how.
As a test designer, myself (and a competitor of Whittaker's) I can certainly find things to nitpick about this book. But I won't do that here, because the big picture is far more important. That picture is simply this: if you are confused about what to do to uncover problems in software before it ships, EVEN IF you have no specifications to test from and EVEN IF no one listens when you rant about "quality assurance processes" they should follow, then there are only a few testing books yet published that will help you. This is one of them.