Robots is one of my kid's favorite movies. I like it too. "See a need. Fill a need." is the motto of the main character. He's a young inspiring inventor. It's a phrase he heard as a child from one of his role models, Big Weld, an older, successful inventor. I struggle with wanting to do things right. To provide the right solution at the right price and on the right schedule. And that's all well and good. Great goals. "Right" isn't always easy to quantify. Who gets to define "right" in this case?

Choose a platform, a language a framework. Define the specs and create and architecture. But dang, how do I know if it's "right?" It isn't when I say it's right. It's when the users say it's right. That's the key. Isn't it? If it doesn't fill a need - and provide a good experience - then it isn't right. Even if my architecture is perfect, my code pretty and I've got a green light on all my tests.

Yeah, I know, the "acceptance test" is the final test and of course if that doesn't pass it isn't right. But it is still possible to do something that is accepted, but still not right.

So, it doesn't matter if you use Ruby, PHP, ASP.NET (Web forms or MVC), mySQL, MSSQL, Oracle, Linux, Windows, Mono, Perl, TDD, BDD or any other software, tool, platform or framework. If you don't fill the need you don't win.