Sponsored links


Valid XHTML 1.0!
Valid CSS!



Product: Book - Paperback
Title: Sams Teach Yourself ABAP/4 in 21 Days
Publisher: Sams
Authors: Ken Greenwood
Rating: 5/5
Customer opinion - 5 stars out of 5
An excellent book for the beginning ABAP/4 programmer.


I've read a portuguese translated version. It's good for reporting and some dialog transactions, data dictionary, but lacks explanations about forms or sapscripting, or related details ABAP/4 programming such as jobs, transactions, screen painter, etc. If you are looking for reporting, and some dialogs this book is for you.



Product: Book - Paperback
Title: Object-Oriented Software Construction (Book/CD-ROM) (2nd Edition)
Publisher: Prentice Hall PTR
Authors: Bertrand Meyer
Rating: 5/5
Customer opinion - 5 stars out of 5
Awesome


Few, _VERY_ few authors are as knowledgeable, talented, and fun to read as Mr. Meyer. Compared to the dry, repetitive books by the Rational people, this is a source of relief! _Not_ dogmatic at all, definitely not Eiffel centered, although he uses the language as the notation throughout the book, BECAUSE that's the way he proposes to avoid analysis-to-design-to-implementation-gaps. It's worth every minute reading it, IMHO.



Product: Book - Hardcover
Title: Structure and Interpretation of Computer Programs - 2nd Edition (MIT Electrical Engineering and Computer Science)
Publisher: The MIT Press
Authors: Harold Abelson, Gerald Jay Sussman
Rating: 5/5
Customer opinion - 5 stars out of 5
I don't want to sound harsh but


The negative reviewers entirely missed the point of this book. The issues are not c++ versus scheme, nor the gap between the book's examples and real-world programs, nor that recursion is less intuitive than looping.
The real point is to teach some very core foundations of computer science that show up everywhere. For example, supposedly revolutionary XML looks a heck of a lot like a nested scheme list, first described in 1960. And processing an active server page (or Java server page) is very much like the textbook's specialized language evaluator. Finally, c++ polymorphism through vtables and part of Microsoft's COM mechanics are the exact same thing as the book's data-directed programming section.
This is very deep material for a programming newbie to learn outside a course, but for an experienced nerd who's looking for a systematic framework, it's absolutely terrific. I had done lots of lisp and compiler work before reading the book, so many of the concepts were not new. But it's with this framework in mind that I learn new technologies, and this approach greatly speeds up how long it takes to understand each week's "new" hot product/language/tool/mindset. Put another way: why do so many popular computer books take 1000 pages to describe a few trivial concepts?



Product: Book - Paperback
Title: Lessons Learned in Software Testing
Publisher: Wiley
Authors: Cem Kaner, James Bach, Bret Pettichord
Rating: 5/5
Customer opinion - 5 stars out of 5
Context is Everything when "It Depends" is the Answer


Too often, testers ask questions such as "Should I use this test technique?" or "How should I plan my testing?", where the only real answer is "It depends". Successful testing and test planning depends on your context, and that's what Kaner, Bach, and Pettichord have described in this book. Each lesson briefly describes the context in which the lesson is useful. When conflicting practices are useful but in different contexts, such as whether to use IEEE Standard 829 to document testing, the lessons describe when you would want to use which practice and when you would not.
If you're thinking about your testing, and you're not sure what applies to you, this book will help clarify your thinking. This is not a book about how to test per se, but a well-written and useful book about how to think about testing for your organization.