Monday, April 23, 2007

Software Confidentiality Clause

The three worst marketing mistakes you can make

marketing or marketing is what makes us to a position that leads us to make a sale. A good marketing makes sales are simpler. A bad marketing technique can make a sale impossible.

If we marketing to strangers, some of them raise their hand and be with some potential interest in what we offering. We

marketing with our clients to encourage them to a new level of products or services we offer.

Most of us spend a lot of time, money and effort into marketing. For most of us is the key activity that we use to differentiate ourselves from our competitors ara.

But when we fail to keep promises we make virus marketing release 3 / 33 on us.

virus 3 / 33 destroy the marketing done in the past and make more difficult a new successful marketing - at least some possibilities - in the future. And for most virus 3 / 33 is a process of "do it yourself."

virus 3 / 33 is the word of mouth marketing on steroids, but in reverse. Here's how it works.

When you meet a promise, offering great service, is under budget and saves customers more money than you had originally said, they (customers) will tell 3 people. And this is usually because you are seeking be recommended.

But if you spoil everything, do not do what you said to do, or service failure in any way, in the opinion of the customer, he (the customer) will tell 33 others. This can be a complete disaster.

know that what I say is true. Remember the last time you got a poor restaurant service and many people have said about this.

There are three ways to ensure that marketing made will fail.

Do what he said he would

In 2006, I met the author of a book marketing event Search Engine Strategies in New York City. And I've been receiving your newsletter and heard a few things about your book.

Friday, April 20, 2007

Anorexia Nervosa Research Paper

Top 20 Phrases programmers

The Blog "Under the Sun " I found the 20 responses that a programmer gives the "testers" or users when their program does not work. All these statements as true and painful for those of us who have served as developers or testers who sometimes do not realize how common are our slang.

Let's start the countdown:

20. "Wow, how strange ..."

19. "That had never happened before"

18. "Yesterday it worked well"

17. "How could this have happened?

16. "It must be a hardware problem"

15. "What did you write the program to crash?"

14. "It must be something wrong with your data "

13. "I have not touched that module in weeks"

12. "It should be working with the wrong version"

11. "It's just an unfortunate coincidence"

10. "I can not test everything"

9. "This can not be the cause of that"

8. "This program works, but that has not been proven"

7. "Someone must have stuck his hand in my code"

6. "Sure you do not have a virus on your system?"

5. "While not working, how it feels using it? "

4. "You can not use that version on your system"

3. "Why do you want to do it that way?"

2. "Where were you when the program failed?"

1. "On my machine works fine"

I would add others to the list:

  • Already tried restarting the application? and you already restarted the PC?
  • Already tried reinstalling the application?
  • The CD must have been badly burnt
  • evil must have been discharged.
  • Did
  • should not work that way?
  • That's not a mistake, that's how it works.
  • This is a bug in a component of the Framework.
  • Already installed the security update for your system?
  • least the repository are corrupted.
  • works, but I must correct.
  • did not have time to finish it.
  • That's not in the requirements.
  • was made for safety.


And here are the answers that would neutralize the top 10:

10. "I can not test everything"
Right, therefore it was the problem.

9. "This can not be the cause of that."
Yes, you can.

8. "It works, but has not been proven yet"
Non sequitur.

7. "Someone must have stuck his hand in my code"
So please retrieve it.

6. "I check for viruses on your system?"
Yes, many times.

5. "Even if it does not work, how you feel using it?"
As if it worked.

4. "You can not use that version on your system."
Yes, Yes I can.

3. "Why do you want to do it that way?"
Because I'm emulating a system user who does not know who would do this.

2. "Where were you when the program failed?"
In my office, looking for another error in your code.

1. "It works on my computer"
can not load your machine with you everywhere. This is not your machine.