
Besides baseless huge numbers and predictions of overwhelm, another trick is the accross-the-board generalizations that we all have deep, deep problems that only one more dashboard can solve. Dahboard Fever. Marketing departments love to wow us: “each of your network users will have 87 IoT devices on them by next year- YoUR NETWORK IS NOT READY”.It’s hard to get excited about new features added to old problems.
#INSSIDER OFFICE KEY CODE#
It’s fun seeing RF test facilities and such, but the radios usually aren’t the issue- it’s substandard code that runs the radios. In this spirit I would also like to hear honest explanations about how whatever new stuff is coming is developed with higher QA standards than in the past applied. I sincerely hope that we don’t hear about “new” anything being added to product sets that need to be sunsetted for everyone’s benefit. The delegates in the rooms at MFD4 will be all too familiar with hidden TCO that comes with lack of QA and rushed-out-the-door code and hardware.

But don’t charge me today for what I can’t use for 6-12 months. Back to the fair play thing- roadmap feautures are fine. If it’s buggy, incomplete, “coming in Q1 next year”, bundled with a slew of other functions we really don’t want, or implemented with an out-of-touch developer’s view on wireless, it is not worth a premium.
#INSSIDER OFFICE KEY LICENSE#
And some of you have lost your sense of fair play in favor of squeezing every rediculous cent out of long-time loyal customers with obscene, over-complicated license paradigms that are poorly disguised as “innovative”. Hear me now vendors: license away- but know that fair play counts. Over-Licensed Proprietary Features Masked as Innovation. Vendors have the right to charge whatever they want, and some have certainly turned complex licensing paradigms into huge cash cows.There needs to be more to the presentation than “AND WE FREAKIN’ USE AI- NOW CUT US A P.O.!”

Just because a vendor has incorporated artifical intelligence, machine learning, SDeverything, analytics, etc, it doesn’t mean the product won’t ultimately be problematic. I’m all for letting the world know that these processes are at work under the hood- but companies also have a way of overselling buzzwords.


(If you’re not familiar with Mobility Field Day or the Field Day franchise, have a look here.) As I bang this blog out, the agenda features: With another Mobility Field Day 4 coming up soon, I can’t help but ponder what this year’s briefings will bring.
