Skip to main content

What to do?

I recently bought one of those wireless earbuds from Amazon. I spent some time researching all the available options and finally picked this particular one. It was highly rated on Amazon 5 stars from 54 reviewers (most of them "verified purchase"). Not great but not bad. Anyway, the earbuds arrived and I found this in the box:

Hmm, OK. Very mysterious. As instructed, I sent them an email for further information. Here's what I received:

Funny thing is I really like the ear buds. Excellent build quality and thus far, great performance. They reconnect to my phone 2-3 seconds after taking them out of the case. It's easy to create a good seal...sometimes so good I get that underwater feeling one gets with noise cancelling headphones. Even without the 40% incentive, I would have written a review...that's how much I like the ear buds. But now I feel weird about doing it. I wonder how many of those 54 5-star reviews were motivated by a 40% discount.

As for the 40% discount, I doubt if I'll ever use it. Not unless this set stop working and I decide to buy another from the same company.

So what should I do?

  • Don't write a review, don't take the 40% coupon
  • Don't write a review, take the 40% coupon
  • Write a review but don't take the 40% coupon
  • Write a review, take the 40% and encourage this shady practice

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…