I once asked someone on the forums why they wanted a particular solution. I did this because they were asking for a technique that seemed like a lot of unnecessary work. I was attempting to provide a better answer that met their true needs within the abilities of FileMaker. In other words, why give a man a fish when he really wants a fishing pole. The response I received was, "Why is not relevant to how." Wow! This guy couldn't be any more wrong. Such a shortsighted approach to programming is not uncommon which is why I'm writing this article. It's your job as a developer to ask your clients "why"! So... let me tell you why.

View the full article