That's a rather facile response. Is that what Google should say to the guy who is complaining in the article?
"Oh, you need more than 10,000 contacts? Well, why don't you just find a creative solution to the problem instead. Creativity comes from limits!"
Trust me, I'm sure this guy will find a creative solution to his problem, just as I ended up finding a creative solution to my own problem.
But I'd be extremely wary as a developer of presuming to know more about your customer's problem space than they do, and that all they need is a little dash of creative thinking to get around whatever limitation your software may have presented them with.
I apologize for being so oblique, but I wasn't responding to the article, merely the line:
> It's a shame because limitations like these ultimately place limits on your creativity.
I understand what you mean, but this statement still bothers me. Needing more than 10,000 contacts may be a requirement for many reasons, but creativity does not seem like one of them to me.
Gotcha. I likewise think I now better understand where you were coming from in your comment. "Creativity" was probably a poor word choice on my part -- perhaps "capabilities" would have been better, as in, "It's a shame because limitations like these ultimately place limits on what the software is capable of doing."
"Oh, you need more than 10,000 contacts? Well, why don't you just find a creative solution to the problem instead. Creativity comes from limits!"
Trust me, I'm sure this guy will find a creative solution to his problem, just as I ended up finding a creative solution to my own problem.
But I'd be extremely wary as a developer of presuming to know more about your customer's problem space than they do, and that all they need is a little dash of creative thinking to get around whatever limitation your software may have presented them with.