6/30/2011

Judith Miller Guide to Period Style Curtains and Soft Furnishings Review

Judith Miller Guide to Period Style Curtains and Soft Furnishings
Average Reviews:

(More customer reviews)
Thoroughly enjoyed the book. Just wish it had many MORE instructions for making some of the period treatments.

Click Here to see more reviews about: Judith Miller Guide to Period Style Curtains and Soft Furnishings

There is no style so coveted in interior decoration as authentic period style, and there is no name so identified with period style decorating as Judith Miller. This beautifully illustrated book provides detailed instructions on how to create authentic period looks using curtains, draperies, and soft furnishings. Included are photographs of a wide range of period rooms with step-by-step sewing instructions for 14 projects and inspiration for hundreds more.From tapestry cushions to four-poster bed hangings, from swagged and tailed window coverings to wing chair covers--every aspect of period draperies and soft furnishing is covered, including photographs of swatches of classic fabrics still available today and backed up by a directory of international suppliers of these period-style fabrics.With hundreds of period ideas shown in more than 450 full-color photographs and step-by-step diagrams, Judith Miller's Guide to Period-Style Curtains and Soft Furnishings is the essential guide for home and professional decorators alike."[Judith Miller's] latest book is full of elegant and simple period rooms with stunning window treatments and a trove of other decorating ideas."--Better Homes and Garden's Window & Wall Ideas

Buy Now

Buy cheap Judith Miller Guide to Period Style Curtains and Soft Furnishings now.

Paranormal Investigator: True Accounts of the Paranormal (Volume 1) Review

Paranormal Investigator: True Accounts of the Paranormal (Volume 1)
Average Reviews:

(More customer reviews)
Ordered the book as curious to read about his accounts in the field. Starts with his childhood experiences which kick-started the authors curiosity into all realms of the paranormal making him become what he is today...
I fully respect how the guy steps back and does his research thoroughly, and in re-enacting the situations after the occurrences happen - hence debunking. Love how he gives out a detailed description in the book on each location along with the equipment he uses, which you'll find a fair few tips well worth noting down, along with the usage of the MV-1 goggles he himself designed. Also mentions the safety of himself and fellow investigators whilst on Investigations. He shows a lot of respect for the buildings, the owners and other teams/students, but how he shows respect for the spirits, shows in his words. That I like...
I enjoyed reading the Old Coney Cemetery and hopes one day he revisits. The Poltergeist chapter was my favourite part in the book as it made me start to speed read - and I only do that when I'm thirsty for more... : )
Only downside of the book is the pictures, I wish were a little better as some are notably dark.
This guy is well worth looking into. He's the next big thing in the Paranormal. I give Mr. Lancaster a big thumbs up and hope to see more of his field/written work. The Paranormal world could do with more guys like this out there in the Para/field.
But, I totally enjoyed reading it. It was a very interesting and educating read. I recommend this book to anyone and everyone. Especially novices in the field. For if you are starting out and need some kind of teacher to look up too. This one I would recommend...
Looking forward to another one of his written works...

(To understand the ghost, one must first understand the human that once was...)

Click Here to see more reviews about: Paranormal Investigator: True Accounts of the Paranormal (Volume 1)

Paranormal Investigator: True Accounts of the Paranormal, is a non-fiction book focusing on eight well documented cases of paranormal activity as chronicled by paranormal researcher Stephen David Lancaster II.From his first childhood encounter to experiences twenty years later, Lancaster opens the folders of his files sharing some of the most productive, memorable and indisputable cases from his years of paranormal research.The haunting evidence of Poogan's Porch Restaurant, the Brentwood Wine Bistro, the Music House, Emily's House and others are included.The book also includes an in depth look into the Industrial Facility case that was featured on NBC Universal in October 2009 where they revealed Lancaster's video footage of the infamous Cowboy Ghost.

Buy Now

Buy cheap Paranormal Investigator: True Accounts of the Paranormal (Volume 1) now.

6/29/2011

Software Testing and Quality Assurance: Theory and Practice Review

Software Testing and Quality Assurance: Theory and Practice
Average Reviews:

(More customer reviews)
This book is very inconsistent in helping you learn. For example, chapter 10 is full of notation on finite state machines, but things are hardly explained at all. There is hardly any reasoning for why you are generating all of these various sequences. Then look at chapter 17 and you get definitions like:
Learnability: The capability of the software product to enable the user to learn its applications.
Operability: The capability of the software product to enable the user to operate and control it.
Attractiveness: The capability of the software product to be liked by the user.
How can you go from the insanely complex finite state machine stuff to telling someone what attractiveness is. And they never vary to say "the capability of the software product". The book wastes time writing that out where it could be using that time to explain the concepts that are actually difficult. It definitely seems the book was written by two different people.

Click Here to see more reviews about: Software Testing and Quality Assurance: Theory and Practice

A superior primer on software testing and quality assurance, from integration to execution and automation
This important new work fills the pressing need for a user-friendly text that aims to provide software engineers, software quality professionals, software developers, and students with the fundamental developments in testing theory and common testing practices.
Software Testing and Quality Assurance: Theory and Practice equips readers with a solid understanding of:
Practices that support the production of quality software
Software testing techniques
Life-cycle models for requirements, defects, test cases, and test results
Process models for units, integration, system, and acceptance testing
How to build test teams, including recruiting and retaining test engineers
Quality Models, Capability Maturity Model, Testing Maturity Model, and Test Process Improvement Model

Expertly balancing theory with practice, and complemented with an abundance of pedagogical tools, including test questions, examples, teaching suggestions, and chapter summaries, this book is a valuable, self-contained tool for professionals and an ideal introductory text for courses in software testing, quality assurance, and software engineering.

Buy NowGet 18% OFF

Buy cheap Software Testing and Quality Assurance: Theory and Practice now.

6/28/2011

The Boundary-Scan Handbook Review

The Boundary-Scan Handbook
Average Reviews:

(More customer reviews)
When I needed to write a few JTAG/TAP drivers this book was the best reference I could find. When I was debugging a TAP bug this book was perfect. So, despite the shortness of this review, the book is complete and well written.

Click Here to see more reviews about: The Boundary-Scan Handbook

Boundary-Scan, formally known as IEEE/ANSI Standard1149.1-1990, is a collection of design rules applied principally atthe Integrated Circuit (IC) level that allow software to alleviate thegrowing cost of designing, producing and testing digital systems. Afundamental benefit of the standard is its ability to transformextremely difficult printed circuit board testing problems that couldonly be attacked with Ad-Hoc testing methods into well-structuredproblems that software can easily and swiftly solve. IEEE testing standards of the 1149 family are living entities thatgrow and change quickly. The Boundary-Scan Handbook, Third Edition isintended to describe these standards in simple English, rather thanthe strict and pedantic legalese encountered in the standards. Over180 drawings and 40 tables illustrate important concepts. Forty-sixDesign-for-Test rules are provided, with complete explanations. The fundamental 1149.1 standard is now over 13 years old and has alarge infrastructure of support in the electronics industry. Today, amajority of custom ICs and Programmable Logic Devices have 1149.1implementations. The Boundary-Scan Handbook, Third Editionupdates the information about 1149.1, which has been revised asrecently as 2001. It contains a description of the 1149.4 "AnalogBoundary-Scan" standard, and gives a tutorial on analog testingtechnology. It then introduces the recently released IEEE 1149.6"Advanced I/O" standard, which extends Boundary-Scan to deal withAC-coupled differential signaling now becoming common in higherperformance system. Finally, since a board test system provides asuitable environment for programming non-volatile Programmable LogicDevices, the IEEE 1532 standard is described which extends the 1149.1access protocol into the device programming domain. This forms anessential tools for testing boards and systems of the future.

Buy NowGet 29% OFF

Buy cheap The Boundary-Scan Handbook now.

VLSI Test Principles and Architectures: Design for Testability (Systems on Silicon) Review

VLSI Test Principles and Architectures: Design for Testability (Systems on Silicon)
Average Reviews:

(More customer reviews)
This is a great book for Test/DFT engineers and EDA engineers developing test tool. It gives a thorough review of lot of concepts and techniques employed in practice which cannot be found if you look at a general testing book. This also makes it an excellent resource to prepare for interviews.

Click Here to see more reviews about: VLSI Test Principles and Architectures: Design for Testability (Systems on Silicon)



Buy NowGet 41% OFF

Buy cheap VLSI Test Principles and Architectures: Design for Testability (Systems on Silicon) now.

6/27/2011

Debugging Applications for Microsoft .NET and Microsoft Windows (Pro-Developer) Review

Debugging Applications for Microsoft .NET and Microsoft Windows (Pro-Developer)
Average Reviews:

(More customer reviews)
Being John Robbin's greatest fan, I have been monitoring the release of this book right after it appeared on amazon. Once It hit the market for real, I got a copy via express delivery and I have to say it's worth the wait. I haven't actually read the whole think yet but its very impressive so far.
John walks the reader through debugging without tears. This edition of the book does contain a lot more information and is very current (a little too current cos all the binaries were built with VS .NET 2003 which is not in the market at this time.
However, this didn't hinder me since I have a copy of the RC. The first part of the book covers coding practices that will reduce the need to debug in the first place. The other parts of the book go into the dirty details of going after bugs with full confidence. From native win32 to managed code to multithreading; its all here.
If you're tired of scratching your head even when you have a debugger in front of you, stop reading my review and get yourself a copy of this book right away.

Click Here to see more reviews about: Debugging Applications for Microsoft .NET and Microsoft Windows (Pro-Developer)

Learn lethally effective, real-world debugging techniques for Microsoft Windows operating system-based applications. This classic book has been updated with all-new coverage of .NET application debugging tools, techniques, and scenarios.

Buy Now

Buy cheap Debugging Applications for Microsoft .NET and Microsoft Windows (Pro-Developer) now.

6/26/2011

Software Testing and Continuous Quality Improvement, Third Edition Review

Software Testing and Continuous Quality Improvement, Third Edition
Average Reviews:

(More customer reviews)
"Software Testing and Continuous Quality Improvement" by William E. Lewis, is a superb QA/BA reference for any organization seeking to improve their Quality Processes. Starting with a brief history of the recognition and measurement of software Quality, it quickly moves on to detailed descriptions of the QA process, frameworks, testing techniques, the relationship of business requirements to QA testing (excellent for BA's), various testing methodologies, a very large and detailed explanation of AGILE methodologies, Project Management as it relates to QA, the importance of Measurement in any QA process, Test Automation, SOA Testing, and Testing Tools. This is a true QA REFERENCE tome that should be in the library of every QA professional who is seriously interested in improving the QA process (and thereby the Quality of their organization's products)! In addition, the companion CD includes dozens of useful templates to jump-start a robust QA initiative. Bill Lewis is a Quality-obsessed professional who has great knowledge and experience in the field. He also created a fine suite of test case development tools, which help create meaningful test data, reduce risk, and increase productivity. They can be found at http://smartwaretechnologies.com/. Needless to say, I highly recommend this book!

Click Here to see more reviews about: Software Testing and Continuous Quality Improvement, Third Edition

It is often assumed that software testing is based on clearly defined requirements and software development standards. However, testing is typically performed against changing, and sometimes inaccurate, requirements. The third edition of a bestseller, Software Testing and Continuous Quality Improvement, Third Edition provides a continuous quality framework for the software testing process within traditionally structured and unstructured environments. This framework aids in creating meaningful test cases for systems with evolving requirements. This completely revised reference provides a comprehensive look at software testing as part of the project management process, emphasizing testing and quality goals early on in development. Building on the success of previous editions, the text explains testing in a Service Orientated Architecture (SOA) environment, the building blocks of a Testing Center of Excellence (COE), and how to test in an agile development. Fully updated, the sections on test effort estimation provide greater emphasis on testing metrics. The book also examines all aspects of functional testing and looks at the relation between changing business strategies and changes to applications in development.Includes New Chapters on Process, Application, and Organizational MetricsAll IT organizations face software testing issues, but most are unprepared to manage them. Software Testing and Continuous Quality Improvement, Third Edition is enhanced with an up-to-date listing of free software tools and a question-and-answer checklist for choosing the best tools for your organization. It equips you with everything you need to effectively address testing issues in the most beneficial way for your business.

Buy NowGet 22% OFF

Buy cheap Software Testing and Continuous Quality Improvement, Third Edition now.

The Career Programmer: Guerilla Tactics for an Imperfect World (Expert's Voice) Review

The Career Programmer: Guerilla Tactics for an Imperfect World (Expert's Voice)
Average Reviews:

(More customer reviews)
If you are a programmer who is constantly persuing self-improvement of your software development skills, but is frustrated by your social development environment (i.e. Management), this book is for you. You care enough about yourself to try and fix your troubled environment. After you finish this book, I suggest giving Pete McBreen's Software Craftsmanship a read, and follow that with Alistair Cockburn's Agile Software Development. Duncan's book shows software development as a battleground of politics and ego-tanks-Duncan suggests ways to survive that crazy mess. If you actually want to change the way you develop software, McBreen and Cockburn show you the door.
I finally finished the Career Programmer after putting it down so many months ago because...I found it...depressing. Why? I lived that crazy mess. However, I have a hard time pinning down who his intended audience is--the Sr. Programmer, the middling programmer, the junior programmer? He certainly addresses all of these, sometimes from paragraph to paragraph. I suppose that he's writing to them all, or more appropriately-to the program manager that's been promoted from Sr. Engineer. I guess this because he talks about accurately tracking your activities (a PSP tactic), Managing your Team, and Putting together your Testing Team. This is obviously a mix of topics that's going to apply to a project manager.
Duncan repeatedly puts the onus on the reader to be responsible for these activities because no one else, and certainly not your management will do these things for you. (Depressing.) He compliments this advice with more survivalist wisdom on politics: don't stick your head too high and get fired. Don't lay too low and ignore the politics game and get fired for becoming redundant. Make sure to kiss up and make sure to praise management but suggest ideas on how their protect could be "better" with ideas from the other corner of your mouth at the same time.
This endless list of survival tactics is guidebook material for beginning programmers, but like I said, if he's writing to project managers, it behoves the project manager (or Sr. Programmer) to teach their Jr. programmers these tactics. It would be a very intimidating book to read for the entry level programmer. However, entry level programmers, in my experience, don't read much (they Know How To Program: bring it on!) and it's the team lead programmers who by discovering failure, start reading these books. Thus, this book is yet another depressing account of Thinks You Should Have Known.
Duncan, in his wisdom, points out something that many a programmer has oft reflected on: career path. He doesn't talk about this to much point, but his section on it says: have a thought about what kind of developer you want to be before you jump into the industry and let it mold you into something you regret. How many of us feel molded even now? Too many. I reflect on how a doctor or a lawyer could easily make the same kind of mistake--let their industry whisk them along and wake up to find themselves as a profession in a field they failed to choose.
However, this book is saturated with irony: almost all pointed advice Duncan gives is to subvert the system. Sneak in your testing staff. Sneak in your design time. Lie about what you're doing to give your self time to do things management is too ignorant to approve of. Duncan writes: life is too short to work for clowns, but if you have to pull these stunts to build a development team, to what degree of clown do you stop working for? People concerned about the reality of the software industry should pay attention to the reality presented in Duncan's book.
I think that many of the topics that Duncan raises in his book are artifacts of Scientific Management and Software Engineering. The environments that Duncan describes - offices full of idiotic ego-battles where people talk about producing software - would not exist were Pete McBreen's vision of software development the existing reality (a reality where people cared about getting the work done as it reflects their reputation).
I also find it interesting to note that much of what Duncan writes has been written by Steve McConnell in Rapid Development and Software Project Survival Guide. However, McConnell and Duncan describe something much closer to the Software Engineering environment than what, in my experience, is actually the reallity for smaller application development projects. I had echoed the ideas McConnell promoted for lack of any better writing on software development. However, after reading McBreen and Cockburn's respective works, my views on how to develop applications have radically changed towards the Craftsman approach. McConnell, in After the Goldrush provides many good arguments for the Licensing of Software Engineers, McBreen compliments McConnell's tack that such licensing efforts-are only rarely applicable.

Click Here to see more reviews about: The Career Programmer: Guerilla Tactics for an Imperfect World (Expert's Voice)


Unrealistic schedules, unstable releases, continual overtime, and skyrocketing stress levels are legendary in the software development industry. Unlike traditional occupations such as accounting or administration, the software business is populated with programmers who are as creative and passionate about their work as musicians and artists. But for most programmers and project managers, it is a complete surprise when they enter the business world and find that internal politics, inept management, and unrealistic marketing drive the process, rather than a structured and orderly approach based on technical issues and quality.

This guide, delivered with the wit and aplomb to make a serious topic entertaining and palatable, will help you survive the programming industry in 2006. The Career Programmer explains how you can work within the existing system to solve deadline problems and regain control of the development process. Youll master self-defense techniques to shield yourself, your project, and your code from corporate politics, arbitrary management decisions, and marketing-driven deadlines. Author Chris Duncan provides proven, practical, hands-on solutions designed to work even when tested by the political and chaotic realities of the business environment. Issues are addressed from the points of view of both the programmer and project manager, and steps are illustrated from all perspectivesfrom large-scale teams down to projects with a single developer. For you, the end results will mean less overtime and stress, higher-quality software, and a more satisfying career.


Buy NowGet 19% OFF

Buy cheap The Career Programmer: Guerilla Tactics for an Imperfect World (Expert's Voice) now.

6/25/2011

Code Leader: Using People, Tools, and Processes to Build Successful Software (Programmer to Programmer) Review

Code Leader: Using People, Tools, and Processes to Build Successful Software (Programmer to Programmer)
Average Reviews:

(More customer reviews)
"Code Leader" is a book for developers who have been on a few projects and are ready to take that next step beyond just the "code" part of "coding." The book covers topics like when to build components vs. when to buy them, good testing practices, automating your build, and analyzing your code to learn where to improve it. Each topic is addressed at a reasonable pace, not miring you in super-low-level detail but providing enough information to get the point across.
As you read it, you'll find that much of it sounds like common sense, like some long-forgotten tidbit that you didn't realize you already knew. That's the strength of the book - bringing those things to light and showing you the benefits. The best example of this is the "Done is Done" chapter, bringing up the idea that sometimes when a developer says that a task is "done," there really are things left to do... and ideas on how to solve that so when someone says something is "done," all of the i's are dotted and t's are crossed.
At the end, the book brings all of the lessons together in a case study showing a developer performing a task from beginning to end and using the tenets described in the book. It's a good way to put everything into perspective and solidifies the concepts.
If you already practice things like test-driven devleopment and continuous integration; if you already know about the benefits of the MVP/MVC patterns (and use them); if you already know what dependency injection is and how it affects your testability; if you've got some nicely structured source control policies and do branch/merge per task (and know why that's good)... you may not get as much out of this book. You're probably already doing most of the stuff discussed and don't need to be sold a car you've already bought (so to speak).
Only two technical downsides to this book:
First, while the content could apply to any software development project in any technology, most of the tools mentioned and code samples are specifically .NET-oriented. That may be a little off-putting to non-.NET developers, but if you can get past that, you'll be rewarded.
Second, the text is abnormally small. I compared it to some of the other Wrox books I've got and there's got to be a two-or-three point size difference here, which makes the book lightweight but might give you a little eyestrain.
If you're looking for complementary books to this one, check out Coder to Developer: Tools and Strategies for Delivering Your Software by Mike Gunderloy. The two offer similar types of advice - ways to go beyond "just coding" and take your projects to the next level. While there are some overlapping topics, the two really are more complementary, each offering great guidance to help you sharpen your saw.

Click Here to see more reviews about: Code Leader: Using People, Tools, and Processes to Build Successful Software (Programmer to Programmer)



This book is for the career developer who wants to take his or her skill set and/or project to the next level. If you are a professional software developer with 3–4 years of experience looking to bring a higher level of discipline to your project, or to learn the skills that will help you transition from software engineer to technical lead, then this book is for you. The topics covered in this book will help you focus on delivering software at a higher quality and lower cost. The book is about practical techniques and practices that will help you and your team realize those goals.
This book is for the developer understands that the business of software is, first and foremost, business. Writing code is fun, but writing high-quality code on time and at the lowest possible cost is what makes a software project successful. A team lead or architect who wants to succeed must keep that in mind.
Given that target audience, this book assumes a certain level of skill at reading code in one or more languages, and basic familiarity with building and testing software projects. It also assumes that you have at least a basic understanding of the software development lifecycle, and how requirements from customers become testable software projects.
Who This Book Is Not For: This is not a book for the entry-level developer fresh out of college, or for those just getting started as professional coders. It isn’t a book about writing code; it’s a book about how we write code together while keeping quality up and costs down. It is not for those who want to learn to write more efficient or literate code. There are plenty of other books available on those subjects, as mentioned previously.
This is also not a book about project management or development methodology. All of the strategies and techniques presented here are just as applicable to waterfall projects as they are to those employing Agile methodologies. While certain strategies such as Test-Driven Development and Continuous Integration have risen to popularity hand in hand with Agile development methodologies, there is no coupling between them. There are plenty of projects run using SCRUM that do not use TDD, and there are just as many waterfall projects that do.
Philosophy versus Practicality: There are a lot of religious arguments in software development. Exceptions versus result codes, strongly typed versus dynamic languages, and where to put your curly braces are just a few examples. This book tried to steer clear of those arguments here. Most of the chapters in this book deal with practical steps that you as a developer can take to improve your skills and improve the state of your project. The author makes no claims that these practices represent the way to write software. They represent strategies that have worked well for the author and other developers that he have worked closely with.
Philosophy certainly has its place in software development. Much of the current thinking in project management has been influenced by the Agile philosophy, for example. The next wave may be influenced by the Lean methodologies developed by Toyota for building automobiles. Because it represents a philosophy, the Lean process model can be applied to building software just as easily as to building cars. On the other hand, because they exist at the philosophical level, such methodologies can be difficult to conceptualize. The book tries to favor the practical over the philosophical, the concrete over the theoretical. This should be the kind of book that you can pick up, read one chapter of, and go away with some practical changes you can make to your software project that will make it better.
That said, the first part of this book is entitled “Philosophy” because the strategies described in it represent ways of approaching a problem rather than a specific solution. There are just as many practical ways to do Test-Driven Development as there are ways to manage a software project. You will have to pick the way that fits your chosen programming language, environment, and team structure. The book has tried to describe some tangible ways of realizing TDD, but it remains an abstract ideal rather than a one-size-fits-all technical solution. The same applies to Continuous Integration. There are numerous ways of thinking about and achieving a Continuous Integration solution, and this book presents only a few. Continuous Integration represents a way of thinking about your development process rather than a concrete or specific technique.
The second and third parts represent more concrete process and construction techniques that can improve your code and your project. They focus on the pragmatic rather than the philosophical.
Every Little Bit Helps: You do not have to sit down and read this book from cover to cover. While there are interrelationships between the chapters, each chapter can also stand on its own. If you know that you have a particular problem such as error handling with your current project, read that chapter and try to implement some of the suggestions in it. Don’t feel that you have to overhaul your entire software project at once. The various techniques described in this book can all incrementally improve a project one at a time.
If you are starting a brand new project and have an opportunity to define its structure, then by all means read the whole book and see how it influences the way you design your project. If you have to work within an existing project structure, you might have more success applying a few improvements at a time.
In terms of personal career growth, the same applies. Every new technique you learn makes you a better developer, so take them one at a time as your schedule and projects allow.
Examples: Most of the examples in this book are written in C#. However, the techniques described in this book apply just as well to any other modern programming language with a little translation. Even if you are unfamiliar with the inner workings or details of C# as a language, the examples are very small and simple to understand. Again, this is not a book about how to write code, and the examples in it are all intended to illustrate a specific point, not to become a part of your software project in any literal sense.
This book is organized into three sections, Philosophy, Process and Code Construction. The following is a short summary of what you will find in each section and chapter.
Part I (Philosophy) contains chapters that focus on abstract ideas about how to approach a software project. Each chapter contains practical examples of how to realize those ideas.
Chapter 1 (Buy, not Build) describes how to go about deciding which parts of your software project you need to write yourself and which parts you may be able to purchase or otherwise leverage from someplace else. In order to keep costs down and focus on your real competitive advantage, it is necessary to write only those parts of your application that you really need to.
Chapter 2 (Test-Driven Development) examines the Test-Driven Development (or Test-Driven Design) philosophy and some practical ways of applying it to your development lifecycle to produce higher-quality code in less time.
Chapter 3 (Continuous Integration) explores the Continuous Integration philosophy and how you can apply it to your project. CI involves automating your build and unit testing processes to give developers a shorter feedback cycle about changes that they make to the project. A shorter feedback cycle makes it easier for developers to work together as a team and at a higher level of productivity.
The chapters in Part II (Process) explore processes and tools that you can use as a team to improve the quality of your source code and make it easier to understand and to maintain.
Chapter 4 (Done Is Done) contains suggestions for defining what it means for a developer to “finish” a development task. Creating a “done is done” policy for your team can make it easier for developers to work together, and easier for developers and testers to work together. If everyone on your team follows the same set of steps to complete each task, then development will be more predictable and of a higher quality.
Chapter 5 (Testing) presents some concrete suggestions for how to create tests, how to run them, and how to organize them to make them easier to run, easier to measure, and more useful to developers and to testers. Included are sections on what code coverage means and how to measure it effectively, how to organize your tests by type, and how to automate your testing processes to get the most benefit from them.
Chapter 6 (Source Control) explains techniques for using your source control system more effectively so that it is easier for developers to work together on the same project, and easier to correlate changes in source control with physical software binaries and with defect or issue reports in your tracking system.
Chapter 7 (Static Analysis) examines what static analysis is, what information it can provide, and how it can improve the quality and maintainability of your projects.
Part III (Code Construction) includes chapters on specific coding techniques that can improve the quality and maintainability of your software projects.
Chapter 8 (Contract, Contract, Contract!) tackles programming by contract and how that can make your code easier for developers to understand and to use. Programming by contract can also make your application easier (and therefore less expensive) to maintain and support.
Chapter 9 (Limiting Dependencies) focuses on techniques for limiting how dependent each part of your application is upon the others. Limiting dependencies can lead to software that is easier to make changes to and cheaper to maintain as well as easier to deploy and test.
Chapter 10 (The Model-View-Presenter Model) offers a brief descr...

Buy NowGet 29% OFF

Buy cheap Code Leader: Using People, Tools, and Processes to Build Successful Software (Programmer to Programmer) now.

6/24/2011

The Best Software Writing I: Selected and Introduced by Joel Spolsky (v. 1) Review

The Best Software Writing I: Selected and Introduced by Joel Spolsky (v. 1)
Average Reviews:

(More customer reviews)
I recently received a copy of The Best Software Writing I by Joel Spolsky. As with his other book, it's an entertaining read with a number of enlightening insights into what I do for a living...
Joel Spolsky has gathered a number of blog entries, essays, and speeches that showcase (in his opinion) the best writings by software professionals. He feels (and I have to agree) that most programmers and developers will avoid writing at all cost, and as a result are not very good at it. You end up with either indecipherable ramblings or dry monotone typing that is akin to enduring some form of medieval torture. And I confess... I probably have strayed into both those areas a few too many times for the sanity of my readers. But by showcasing techno-geeks that can write coherently and with a touch of humor and entertainment, Spolsky hopes to raise the overall level of writing competency in the industry. I don't know if he'll be successful, but it definitely can't hurt...
Because the writings cover a wide range of topics, there's something for everyone. Or conversely, not everything will appeal to every reader. "Style Is Substance" by Ken Arnold is (for me) a great piece that advocates making programming style a built-in element of a language. Think of the time you'll save by killing off all style wars up front. The cartoon piece "Excel As A Database" will cause all developers to think Rory Blyth must work somewhere in their company with their users. And "A Quick (And Hopefully Painless) Ride Through Ruby (With Cartoon Foxes)" will, although rather strange, give you more information about Ruby in a shorter period of time than you ever thought possible. On the other hand, "A Group Is Its Own Worst Enemy" by Clay Shirky was something I seemed to have to slog through. You may well have just the opposite reaction on any or all of these. It's one of the fun things about this compilation... :)
While you can obviously go out and find all this stuff on-line at the various sites, odds are you won't find what you don't know about. Joel brings together a nice mixture of thoughts and concepts, all packaged within an expert writing style. If you're a professional developer, you probably should pick up a copy and see how writing can be done well...

Click Here to see more reviews about: The Best Software Writing I: Selected and Introduced by Joel Spolsky (v. 1)

It's nice having a collection of high-quality writing related to software and the business in one place instead of trawling the Web for it. Meryl K. Evans, meryl....an entertaining read with a number of enlightening insights into what I do for a living...The whole book is fantastic though, and you should absolutely pick it up...in dead tree form.This is a book worth checking out, even if you're not a software developer.With a nod to both the serious and funny sides of technical writing, The Best Software Writing I: Selected and Introduced by Joel Spolsky is an entertaining read and a guide to the technical writing literati.The Best Software Writing contains writings from:
Ken Arnold
Leon Bambrick
Michael Bean
Rory Blyth
Adam Bosworth
danah boyd
Raymond Chen
Kevin Cheng and Tom Chi
Cory Doctorow
ea_spouse
Bruce Eckel
Paul Ford
Paul Graham
John Gruber
Gregor Hohpe
Ron Jeffries
Eric Johnson
Eric Lippert
Michael Lopp
Larry Osterman
Mary Poppendieck
Rick Schaut
Aaron Swart
Clay Shirky
Eric Sink
why the lucky stiff

Buy NowGet 35% OFF

Buy cheap The Best Software Writing I: Selected and Introduced by Joel Spolsky (v. 1) now.

Your Old Wiring Review

Your Old Wiring
Average Reviews:

(More customer reviews)
This book is a great resource for the non-professional who has to evaluate and/or repair old residential electrical systems. It is well-organized, thoroughly safety-oriented, and practical. The author, David E. Shapiro, is a master electrician with substantial experience. He not only translates the National Electrical Code into practical advice for the do-it-yourselfer, he isn't afraid to express his opinions and recommendations, which is rare in this kind of book. This kind of practical advice, based on long experience, is more valuable than the just-the-facts approach taken by so many DIY authors.
There are two problems with the book, however, and both are related to the graphics. Many of the photographs are blurry or otherwise unhelpful, and there are a number of places in the text where more phtotographs or illustrations would be quite helpful. I would have given this book five stars if the graphics were done as professionally as the text.
Finally, the book doesn't really deal with the "knob-and-tube" type wiring found in many older homes. The author is clear that many subjects are beyond the scope of this entry-level book, and knob-and-tube is one of the subjects that doesn't make it in.

Click Here to see more reviews about: Your Old Wiring

*Written by a master electrician this book shows homeowners and do-it-yourselfers how to go behind the walls of their old homes and correct messy, outdated wiring*Packed with over 250 photos and illustrations, 10 common wiring projects (like installing ceiling fans) and before and after photographs*The only house wiring book that shows how to identify and correct old electrical wiring, simply and safely

Buy NowGet 5% OFF

Buy cheap Your Old Wiring now.

6/23/2011

Python: Create - Modify - Reuse Review

Python: Create - Modify - Reuse
Average Reviews:

(More customer reviews)
I really wanted to like this book. As a professional C# developer, I have been learning Python the last few weeks. I got this book in hopes that it would provide some interesting projects.
I could not bring myself to like this book. It was a painful read because this book demonstrates poor and obsolete programming practices. I feel like this book would probably set a beginner back instead of helping them move forward. I would recommend almost any other Python book over this one.
The book does have seven fairly interesting projects, covering a wide breadth of the Python standard library (xml parsing, database access, file input/output, etc) and some web-based projects. That is why I wanted to like it. It covers interesting topics. However, this is not enough to make up for the sloppy editing, obsolete user interfaces, and poor programming practices. I will detail some of the problems below.
Sloppy editing - For example, look at the code sample at the top of page 31. This wouldn't even "compile" in Python's editor IDLE, because of the incorrect indenting.
....elif choice == "4":
........snapshothelper.showHelp()
.........else:
........if choice != "5":
............snapshothelper.invalidChoice()
The "else:" is intended wrong and then on page 32 the same code is excerpted except it has been copied incorrectly:
....elif choice == "4":
........snapshothelper.showHelp()
....else:
.........snapshothelper.invalidChoice()
You can see that the author corrected a mistake in the main block of code but then did not correct it in the excerpt.
This is just the tip of the iceberg for code blocks that will cause errors upon running them inside Python.
On to the next problem - The user interface for the command-line projects looks like something out of MS-DOS 3.1. In other words, it is extremely outdated, cumbersome and it's not even programmed effectively. The error messages are obtuse and don't even cover all the cases. Frankly, I expect a lot more from an author with an extensive background in testing. For example, in page 70, the "elif" block never checks for choices that are not 1 through 5. If you have an invalid choice it will cause a SQL error and print the error message "THERE WAS A PROBLEM MODIFYING THE RECORD" even though the error was caused by an invalid choice.
My final complaint is that the author does not follow Pythonic practices or even best practices from other languages. For example, the Try-Except blocks (page 79 for example) include large swaths of code instead of just the small section that will actually throw the exception. Also, the Except clause does not catch particular error classes but instead every error. These violate basic best practices for any language. Another example of not being very Pythonic is the lack of list comprehensions like on page 37 (also note that this sample includes inconsistent indentation and would likely cause the Python interpreter to fail):
....for item in filelist:
............if item.find(extension) != -1:
................snaplist.append(item)
This could easily be re-written in the Pythonic way:
....snaplist = [for item in filelist if item.find(extension) = -1]
Unfortunately, I could go on and on talking about things I don't like about this book. The bottom line is that I don't recommend it.

Click Here to see more reviews about: Python: Create - Modify - Reuse

Python: Create-Modify-Reuse is designed for all levels of Python developers interested in a practical, hands-on way of learning Python development. This book is designed to show you how to use Python (in combination with the raw processing power of your computer) to accomplish real-world tasks in a more efficient way. Don't look for an exhaustive description of the Python language––you won't find it. The book's main purpose is not to thoroughly cover the Python language, but rather to show how you can use Python to create robust, real-world applications.
In this respect, the goal is similar to foreign-language books that identify themselves as "conversational,” focusing on the vocabulary and concepts that people will need the most. Likewise, I focus specifically on the Python knowledge needed to accomplish practical, specific tasks. Along the way, you will learn to create useful, efficient scripts that are easy to maintain and enhance.
This book is for developers with some experience with Python who want to explore how to develop full-blown applications. It is also for developers with experience in other languages who want to learn Python by building robust applications. It is well-suited for developers who like to "learn by doing,” rather than exploring a language feature by feature. To get the most out of the book, you should understand basic programming principles.
Because this book is project-based, you can approach it in numerous ways. You can, of course, read it from cover to cover. Chapters 2 through 8 each cover a different project, so the chapters are independent of each other. However, because each chapter project is covered individually, there may be some overlap of information. I also sometimes refer to explanations of particular topics covered in previous chapters. This will help to reinforce important concepts.
The end of the book contains two appendixes. The first one is a listing of Python resources you can check out for more information. The second one will help you with installing additional components used in some of the examples.
This book starts with a basic overview of the Python language, designed for those familiar with other languages but new to Python. It is followed by several chapters, each of which describes a complete project that can be used as-is or modified and extended to suit your particular purposes. You'll find applications that access databases, take advantage of web technologies, and facilitate network communications, to name a few. In addition, and more important than the technologies you will be introduced to, you will learn how to use Python to solve real challenges. Following these chapters are two chapters that cover accessing operating system resources and debugging and testing, respectively.
Each project chapter contains complete instructions describing how to install and use the application, so you can actually see the program run as you learn how to construct and use it, including how the project was designed and prototyped. This book is intended to be both a reference guide and a learning aid, teaching you how to build solutions with Python and providing reference information on a wide variety of Python programming concepts.
It is hoped that this book will help you have fun with Python and build useful applications, and—unlike my experience with building a deck—without sore thumbs.
This book is framed around the code itself. This is because developers are typically looking for how to do something; and, as with many activities, you learn how to do something by watching how others do and trying it yourself. If you want to know how a for loop works, you'll find for loops in my code, but that's not the thrust of the book. Instead, this book shows you how to do things: how to build a content management system, how to build a test management system, how to set up a system for tracking customer follow-up, and so on. Along the way, you'll learn how to communicate with a SQL database, how to act as a web server or communicate with one, how to access operating system services, and more.
There are three basic components to the book:

Chapter 1 is a brief overview of the Python language.

Chapters 2–8 cover seven different programming projects, which illustrate various technologies and techniques available to Python developers.

Chapters 9–10 cover additional, advanced topics, which will help you as you build Python projects.

The project chapters have a consistent structure:

Overview: What does the application do?

Using the program

Design

How it all fits together

Modules involved

Code and code explanation

Module/class 1 explanation

Module/class 2 explanation

Minor code file explanation

Testing, including suggested tests

Modifying the project, including some suggested adaptations

Summary

Each project is designed with classes that can be reused and accessed for multiple purposes. This is one of the main benefits of object-oriented programming, so designing for reusability is a main focus of the book. The book contains the following chapters:
1. Python Basics
This chapter is a basic primer on the Python language, and it functions as either a quick tutorial for experienced programmers new to Python or a refresher for programmers with Python experience.
Part I: The Projects
2. Directory/File Snapshot Program
This project demonstrates how to interact with files, create and manipulate data structures, and provide user output. It also touches on code design issues to improve code maintainability. Often when installing or uninstalling software, or verifying changes to a file system, it can be valuable to take a "snapshot” of the files and directories, along with their size and last-modified time. The script introduced in this chapter does just that. This chapter also explores how to capture a directory listing into a Python list, and explains how to query this list for particular values.
3. DVD Inventory System
This project takes advantage of Python’s capability to access and manipulate data in a SQL database. The application enables multiple users to log in to a website that provides access to a DVD inventory database. Permissions are set such that some users can add, modify, or delete entries, whereas other users have read-only access to the data.
4. Web Performance Tester
This project shows how to communicate with a Python web server and retrieve information regarding how long it takes to receive requested items from the web server. Although writing Python programs to work on a single computer can be useful, the real power of Python can be seen when it is used to script communication between computers on a network. Most networks contain several web servers. A nice feature of Python is that it can act as a lightweight server for various Internet protocols, such as HTTP (web) and ftp. This application enables you to monitor performance of HTTP traffic on your network.
5. Customer Follow-Up System
This project shows how to present a web form to the user and retrieve data from it, how to automatically format and send e-mail through an SMTP server, and how to generate an HTML-formatted report. The task for the second example is to automatically generate a customer comments e-mail message based on information the customer enters in a form. It uses the mod_python Apache module to take the information entered in the HTTP form and then utilizes a Python script on the web server to send that information to an SMTP server for mail delivery.
6. Test Management/Reporting System
This project makes use of the unittest module to run tests against an existing application, and creates a framework for reporting test results. Testing is a vital process for developing software. This application enables users to run tests for a given piece of software, to list the previous test runs by date, to show test run results for any previously run tests, and to output the results of any test run as HTML for viewing in a web browser.
7. Version Management System
This project connects to a list of servers via telnet, checks the application version of a pre-set application list, and displays its results both as output and to a log file. Often, a system administrator needs to patch systems or ensure that systems have the latest application versions installed. This script is an easy way to accomplish that task. It makes use of Python’s capability to emulate a telnet client and log in to remote systems and perform functions on that remote system.
8. Content Management System
This project explores Plone, a popular content management system based on Python and Zope (a Python-based application server). Because Python is a very mature language, numerous applications have been built on top of it. A great thing about working with Python-based applications is that you get the benefit of a full-blown application but you can still use Python to configure and customize it.
Part II: Advanced Topics
9. Interacting with the Operating System
When writing scripts "in the real world,” often it is critical to be able to access services available through (and particular to) the operating system you happen to be on. For example, suppose you wanted to read or modify the Window Registry? Or you wanted to get the Linux process ID of a particular process that is running? Is such a thing even possible? Definitely—and this chapter shows you how.
10. Debugging and Testing
Because I am a software tester myself, testing is a subject that is certainly close to my heart. In...

Buy NowGet 35% OFF

Buy cheap Python: Create - Modify - Reuse now.

6/22/2011

Organic and Chic: Cakes, Cookies, and Other Sweets That Taste as Good as They Look Review

Organic and Chic: Cakes, Cookies, and Other Sweets That Taste as Good as They Look
Average Reviews:

(More customer reviews)
ORGANIC AND CHIC: CAKES, COOKIES, AND OTHER SWEETS THAT TASTE AS GOOD AS THEY LOOK by Sarah Magid is AMAZING! It is absolutely one of the most beautiful cookbooks that I have ever seen. As you can see, the cover photo is just filled with incredible looking desserts; and all of the pictures in the book are just like this. I would actually consider placing this cookbook on my coffee table because it's that gorgeous. Plus, I'd kind of like to have it handy because I really enjoyed looking at all of the recipes and decorating ideas.
Not only is this cookbook filled with beautiful pictures, but there are just loads of yummy-looking recipes. The book starts with recipes for cakes and cupcakes (along with frosting, curds, and filling recipes), then it has a section on cookies and bars, a section on reformed junk food, and one on farmers' market sweets. There is another section that will appeal to a lot of moms titled children's goodies which has easy, cute recipes geared towards little ones. The book ends with a wonderful chapter on Ms. Magid's design techniques along with step-by-step instructions.
I was pleasantly surprised by this cookbook not because of its recipes and photos, but rather because the instructions and explanations were so detailed and clear. The recipes and instructions for decorating were extremely easy-to-follow. Now making my cakes as gorgeous as the ones in the book might be a challenge, but I think that's because of my lack of skill and definitely not the fault of the instructions. And since I am not a regular consumer of organic foods, I loved how Ms. Magid explained the benefits of going organic as well as some name brands for organic baking goods. The last few pages of the cookbook also include explanations of various baking tools and how best to use them. I actually learned a great deal just by reading Ms. Magid's advice.

Click Here to see more reviews about: Organic and Chic: Cakes, Cookies, and Other Sweets That Taste as Good as They Look



Buy NowGet 34% OFF

Buy cheap Organic and Chic: Cakes, Cookies, and Other Sweets That Taste as Good as They Look now.

Academic Advocacy for Gifted Children: A Parent's Complete Guide Review

Academic Advocacy for Gifted Children: A Parent's Complete Guide
Average Reviews:

(More customer reviews)
Barbara Jackson Gilman of the Gifted Development Center wrote this book to assist parents who need assistance in advocating for their gifted children. Because Barbara has worked closely with gifted children and their families for over 15 years, and parented her own gifted children, she knows firsthand that highly intelligent kids need support just as any other children who are outside the norm. She has seen the damage that may be done when gifted kids are not challenged in school, and has worked with many brilliant kids who tune out or give up and drop out of school. This book also contains heartfelt essays written by Quinn O'Leary. Quinn shares his reflections on growing up as a precocious boy who didn't often find adequate challenge in school.
Academic Advocacy for Gifted Children-A Parent's Complete Guide is a complete handbook on advocacy, but also a useful resource for parents who are striving to understand their gifted children. Barbara explains that gifted children often experience the world differently, and devotes a generously sized chapter one to this topic. Chapter two is titled, "What Do We Mean By Gifted?" and it covers asynchrony, personality traits, levels of giftedness, and more. Chapter three will be tremendously helpful to those who are still considering testing or assessment, as well as those who are trying to determine what exactly, their child's test results mean. Sometimes it is important to choose the right instrument for testing. Gilman states, "The WPPSI-III can be given to six-year-olds, but the WISC-IV is usually a better choice when the child is likely gifted." My son's score on the WPPSI taken at age six was in the gifted range, but nowhere near what we'd anticipated based upon his developmental milestones. I wish we'd known enough to request the WISC. School administrators tend to assess more kids who are at the lower end of the spectrum, and are not always familiar with how to do things with extremely bright children.
Chapter seven outlines varieties of gifted programs and educational options. Gilman is a proponent of homeschooling, especially for kids who are highly to profoundly gifted. She points out which school programs are more successful for gifted students, and which are not so successful. The further reading suggestions at the end of the chapter include some terrific books, articles, and websites related to gifted education.
The must-read chapter for parents who need help with school advocacy is chapter eight. The author carefully walks the reader through the steps necessary to get academic accommodations in place. She explains, " Parents should trust themselves to assess the level and urgency of their child's needs, and they can wisely consider various alternatives. Sometimes the best choice is to work with the school and the current teacher to provide accommodations; sometimes it is to move to another classroom, grade, or an entirely different school; and sometimes it is best to remove a child form school altogether. There is no benefit to teaching a child to graciously accept being held back. " If advocacy steps don't lead to an appropriate placement, she advises the reader on when to give up, how to look for a better school, and how to get started in homeschooling.
Gilman also interviewed several extraordinary teachers and talked to them at length about how they work with gifted students. These vignettes will be helpful if a parent is still wondering what it would be like to have their child in the care of a motivated teacher who actually enjoys working with bright students.

Click Here to see more reviews about: Academic Advocacy for Gifted Children: A Parent's Complete Guide

Formerly titled Empowering Gifted Minds: Educational Advocacy That Works, this book is the definitive manual on gifted advocacy for gifted students. The author tells parents and teachers how to document a child s abilities to provide reasonable educational options year by year. This book provides imperative information on testing considerations, curriculum, successful programs, and planning your child s education. It is an essential guide.

Buy NowGet 19% OFF

Buy cheap Academic Advocacy for Gifted Children: A Parent's Complete Guide now.

6/21/2011

Fuzzing for Software Security Testing and Quality Assurance (Artech House Information Security and Privacy) Review

Fuzzing for Software Security Testing and Quality Assurance (Artech House Information Security and Privacy)
Average Reviews:

(More customer reviews)
The introduction to this book mentions its broken up history, being picked up and abandoned a couple times. It definitely shows in the writing, which is unfocused, choppy, and repetitive. Most of the first half is taken up with repetitive descriptions of the general software testing process. The second half contains a summary of one author's thesis on using evolutionary algorithms for fuzzing and the final author's use of various fuzzing tools to try to find hand-inserted vulnerabilities. While the latter half is better than the first, each topic is worthy of a single blog post. Given this book's price and the authors' reputations, I expected more.
At the same time, I read "Gray Hat Python" and it was enjoyable. Even though it had a much broader focus on other topics, it contained more hands-on info on fuzzing tools. I'm also interested in "Fuzzing: Brute Force Vulnerability Discovery", although I have not read it yet.
Don't waste your time on this book. Download the Sulley manual, read the slides from a few Blackhat talks, and you'll be at the state of the art for current fuzzing knowledge.

Click Here to see more reviews about: Fuzzing for Software Security Testing and Quality Assurance (Artech House Information Security and Privacy)

"A fascinating look at the new direction fuzzing technology is taking -- useful for both QA engineers and bug hunters alike!" --Dave Aitel, CTO, Immunity Inc. Learn the code cracker's malicious mindset, so you can find worn-size holes in the software you are designing, testing, and building. Fuzzing for Software Security Testing and Quality Assurance takes a weapon from the black-hat arsenal to give you a powerful new tool to build secure, high-quality software. This practical resource helps you add extra protection without adding expense or time to already tight schedules and budgets. The book shows you how to make fuzzing a standard practice that integrates seamlessly with all development activities. This comprehensive reference goes through each phase of software development and points out where testing and auditing can tighten security. It surveys all popular commercial fuzzing tools and explains how to select the right one for a software development project. The book also identifies those cases where commercial tools fall short and when there is a need for building your own fuzzing tools.

Buy NowGet 16% OFF

Buy cheap Fuzzing for Software Security Testing and Quality Assurance (Artech House Information Security and Privacy) now.

6/20/2011

Miss Mary Bobo's Boarding House Cookbook: A Celebration of Traditional Southern Dishes that Made Miss Mary Bobo's--An American Legend Review

Miss Mary Bobo's Boarding House Cookbook: A Celebration of Traditional Southern Dishes that Made Miss Mary Bobo's--An American Legend
Average Reviews:

(More customer reviews)
Earlier write-ups about Miss Mary Bobo's Boarding House Cookbook intrigued me so I added it to my collection. Reading through it brought back memories of dishes I hadn't thought about -- much less made -- since my Georgia childhood. Then I started preparing them! I could swear that Miss Mary and my mother must have been bosom buddies, maybe even swapped recipes over a pitcher of homemade lemonade. From Southern Iced Tea to Sweet Deviled Eggs and Country Sausage and Gravy on Baking Powder Biscuits and from REAL Cream of Tomato Soup to Best Fruit Salad, the tastes of rich (read lots of cream and butter!)Southern food once again overwhelmed me. Not that every dish was cholesterol-laden -- try the sweet-sour mouth-tingling pleasure of Fresh Tomato Hash or vinegary Garden Fresh Cucumber Salad, for example. The breads are terrific -- and the main yeast one, Country Loaf Bread, adapted easily to the bread machine, producing a light, tasty, "mile-high" loaf. Fresh Zucchini Bread makes great toast and Our Favorite Raisin Bread, lightly glazed, was perfect with Cheese Soup and that wonderful fruit salad. The sauced Boarding House Meat Loaf pleased everyone, as did Our Famous Pork Ribs, Salmon Loaf, Southern Fried Catfish (AND Chicken, of course)and such beloved side dishes as Yankee Limas, Macaroni and Cheese, Southern Corn Pie and Creole Grits (even my grits-despising Minnesota-bred husband had seconds, Summer Squash Casserole and Our Best Baked Beans. Have only started to re-visit the delights of Southern desserts, sampling Old South Butter Cups and Fresh Strawberry Pie -- more to come! Obviously we can't continue at this rate with daily excursions into this wealth of memories and calories, but I plan to highlight at least one dinner a week with such! With thanks from a Southern California gal with happily-renewed memories of an earlier time and place!

Click Here to see more reviews about: Miss Mary Bobo's Boarding House Cookbook: A Celebration of Traditional Southern Dishes that Made Miss Mary Bobo's--An American Legend

Discover the hallmark of Southern food and hospitality with Miss Mary Bobo's Boarding House Cookbook.For years, travelers have come to Miss Mary Bobo's Boarding House, in Lynchburg, Tennessee, for the finest home-cooked meals anywhere.Two meats, an abundance of vegetables and side dishes, homemade breads, desserts, and beverages are all made with the same special care that Miss Mary Bobo used since 1908.This unique cookbook includes over 250 of Miss Mary's favorites still served today, including:-Hummingbird Cake -Spiced Grape Punch -Raisin Biscuits -Baked Chicken with Cream -Hot Potato Salad -Yankee Limas -And more! Give your guests the same delicious Southern dishes served at Miss Mary Bobo's Boarding House.None are difficult to cook, but all are best when prepared by caring hands and served with friendship—a recipe that all boarding houses have found to be foolproof!

Buy NowGet 32% OFF

Buy cheap Miss Mary Bobo's Boarding House Cookbook: A Celebration of Traditional Southern Dishes that Made Miss Mary Bobo's--An American Legend now.

Effective Methods for Software Testing Review

Effective Methods for Software Testing
Average Reviews:

(More customer reviews)
We've been developing a testing group and I wanted a practical reference for software testing. This is not it. The text presumes you're in an extremely mature environment (CMM 3 or higher) and have requirements, design, adequate resources, etc., etc.. I think the book needs more examples, better organization, and practical solutions to the difficulties you're likely to face in managing large-scale testing organizations to be truly effective. If you want LOTS of arcane procedures, though, and are going to work for a gov't. agency--this is your book!

Click Here to see more reviews about: Effective Methods for Software Testing


Written by the founder and executive director of the Quality Assurance Institute, which sponsors the most widely accepted certification program for software testing
Software testing is a weak spot for most developers, and many have no system in place to find and correct defects quickly and efficiently
This comprehensive resource provides step-by-step guidelines, checklists, and templates for each testing activity, as well as a self-assessment that helps readers identify the sections of the book that respond to their individual needs
Covers the latest regulatory developments affecting software testing, including Sarbanes-Oxley Section 404, and provides guidelines for agile testing and testing for security, internal controls, and data warehouses
CD-ROM with all checklists and templates saves testers countless hours of developing their own test documentation

Note: CD-ROM/DVD and other supplementary materials are not included as part of eBook file.

Buy NowGet 25% OFF

Buy cheap Effective Methods for Software Testing now.