Q: You are considering whether to buy a product. You look at the reviews. Would the following review decrease or increase the chances of you buying the product? Review title: Light duty Gerber from China Product review: It's a lightweight folder from Gerber / China. The liner lock is weak and does not lock the blade well at all. I would have sent it back but it's not worth the effort and shipping cost's. It does have an hollow ground blade which is good but I have no idea what kind of steel the blade is made from. The knife is light and small, just count your fingers after each use!
A: increase


Q: You are considering whether to buy a product. You look at the reviews. Would the following review decrease or increase the chances of you buying the product? Review title: Bad Choice Product review: I purchased two of these thinking that they would be great for my daughter and I, we had taken classes to learn how to make Sushi and when we got this and tried it we found it to be a big waste of money.It is a silly machine that does not work at all...if you want to make sushi use a mat, it is much easier. This is a bad choice and waste of your money.
A: decrease


Q: You are considering whether to buy a product. You look at the reviews. Would the following review decrease or increase the chances of you buying the product? Review title: great replacement Product review: I had misplaced all the electronic connections for my Samsung. Amazon is the only place where I found what I needed. I had checked stores but could not find what I was looking for Now I can listen to music again and store my photos.
A: increase


Q: You are considering whether to buy a product. You look at the reviews. Would the following review decrease or increase the chances of you buying the product? Review title: Enjoyable but slanted Product review: I enjoyed this book quite a bit. It's a pretty quick read, and is quite funny in spots. The book's aim is to provide Project Management "tidbits", especially related to software development. I agreed with most of the conclusions, especially the ones about delaying coding and (almost) eliminating debugging, and the ones related to the effectiveness of smaller teams. The book is slanted, however, a bit too much towards the programmers. The author recommends running software development projects with no pressure, and, essentially, no deadline. I've never heard of any project, especially a software development project, that completed effectively with those guidelines (or lack thereof). Overall though, I recommend it.
