A woman was shopping at the local supermarket where she selected:
A half-gallon of 2% milk
A carton of eggs
A quart of orange juice
A head of romaine lettuce
A 2 lb. can of coffee
A 1 lb. package of bacon
As she was unloading her items on the conveyor belt to check out, a drunk standing behind her watched as she placed the items in front of the cashier.
While the cashier was ringing up the purchases, the drunk calmly slurred, ‘Ya mus be single.’ The woman was a bit startled by this proclamation, but she was intrigued by the drunk’s intuition, since she was indeed single. She looked at the six items on the belt and saw nothing particularly unusual about her selections that could have tipped off the drunk as to her marital status.
Curiosity getting the better of her so she said: ‘Well, you know what, you’re absolutely right, but how on earth did you know that?’
To support increased responsiveness to business needs, an enterprise is considering a move to monthly site releases.
Increased frequency of releases places additional demands upon the engineering, QA and release teams with regard to developing, maintaining, testing, and tracking multiple lines of development. The challenge to the enterprise is how to balance the engineering team’s need for ongoing development, which is often experimental in nature and uncertain in outcome (the “what”), with those of the business whose focus is more schedule-driven, and thus highly dependent upon calendar time (the “when”).
I travel a lot. On the road, I depend upon wireless connectivity everywhere I go. Recently, I got fed up with the lack of dependable Wifi service (it is horrible at ATL for example), so I purchased a Laptop Connect card. EVDO, 2xG, 3G… if there’s service, this card will pick it up.
This story has four parts: The Card Problem, The Apple Store Experience, the Analysis and The Latch Fix. If you are only interested in the fix, skip down to that part.