While it is indeed more convenient to use my iPhone as a GPS than a dedicated GPS unit, I have had a few incidents that made me realize that Apple has no clue how to do maps and driving directions. Here is a couple of illustrations.
It used to be that enterprises wishing to reach their employees 24/7 invested in smartphones specifically designed for enterprise IT. In case anyone forgot those were typically Blackberry or Windows Mobile, neither of which was a pleasant device for a consumer to use.
Then everyone got themselves iPhones and people started carrying a personal iPhone and a work Blackberry. Corporate IT departments realized they could save thousands per year by coming up with ways to get people to use their personal smartphones for work. As an added bonus it became difficult for employees to leave their personal phones at home.
Meanwhile RIM and Microsoft continued to produce devices that people would never buy for their personal use. So the pressure built up within the IT departments to not only make cross platform enterprise apps, but also invest in native iPhone and Android apps.
Photography is my hobby and my favorite store for supplies is B&H. They are owned and operated by an Orthodox Jewish family. Today happens to be Shabbat and they are closed from Friday afternoon till Saturday evening. Sometimes they are closed for days at a time during Jewish holidays as well. Yet, they have a loyal following of customers who will patiently wait to place their orders, however important they might be. Neither is B&H particularly concerned about lost sales. I respect them for that.
In August, 2000 Joe Spolsky wrote "The Joel Test: 12 Steps to Better Code". That was 14 years ago, and since then I've developed my own, more up-to-date version based on the original "Joel Test" as well as my own experience.
When started each software project goes through a period of active development when the rate of new features being added is very high. This stage flattens out and starts declining as the project begins to take shape and the rate of bug fixes begins to outweigh new feature development. It is at this point in the lifecycle when crucial decisions must be made about the future of the product.
I was ordering a new suit for myself today. The salesman eagerly showed me 3-4 different suits within the price range and style I was looking for. I am tall and skinny and it's always been a pain to find a well fitted suit for me.
We settled on two that seemed to look good to both me and the salesman. I was taken to the measuring room where the tailor grumbled about the pants being too baggy and the jackets being to slack which would have required too many alterations to make them fit.
The salesman tried to defend his recommendations and the tailor responded that the size was so off it was going to be a complete custom work. "Why does everyone want to be a tailor?" he grumbled.
I often get emails from recruiters that are total non-sequitors. I think I make it pretty clear in my LinkedIn profile and on this blog what my background is. But more often than not I get emails with job leads that have nothing to do with my background or interests.