I write this piece fresh on the heels of Day 1 of 2020’s Mobility Field Day 5. Mist (Now a Juniper company) talked for about six years yesterday, and it was fairly riveting, end to end. It was one of those marathon sessions that needs a little time to settle in your brain before you can resolve it, figuring out what you actually liked to hear and what maybe raised some red flags. Let’s talk about those red (well, maybe a pale red, sorta orangey-pink) flags that sprouted in my mind as I slumbered on the whole thing.
Mist Systems has had a fantastic run as a late-comer to a competitive industry filled with incumbents. That’s not easy, and their AI-inspired story has served them well. Now, we see the company moving i’s own cheese, and I can’t help but think about maybe a few areas of concern.
- Mist is no longer its own little WLAN product line bubble. Mist started off as a wireless-only product line. That let it focus on one discreet area with all of its development and quest for excellence. Sure, AI has been a key ingredient. But AI is not a magic wand. Just because you use it, doesn’t mean you have the Golden Ticket forever. NOW, Mist is spreading its methodology into the Juniper LAN side of its new house… the bigger you go, the more places there are for things to go wrong. The more opportunities there are for code bugs…
- Mist has finally introduced a respectable AP product line. Again, Mist has had the luxury of not offering many APs to date. Life has got to be easier on the development side when your product set is smaller, I’m guessing. We see it frequently from other vendors- certain model APs are prone to issues and bugs. Will Mist bump into the same sort of customer-facing shame now that they have some diversity of AP lineup? Or will their promised self-debugging whizz-banginess eliminate that as a potential? Time will tell.
- The um… well… uncomfortable thing to mention. I have the utmost respect for Mist’s senior leadership. Their results to date with injecting the AI/higher reliability story into an industry often fraught with overpriced buggy code suck speak for themselves. However- some of Mist’s senior folks come from that world of buggy code suck. They helped to author the very realm they now take potshots at. I mention this only to make the point that nobody is perfect with a perfect past, and that history sometimes repeats itself. In the buggy code suck world, complexity only exasperates the buggy stuff, and Mist, as an overall operational paradigm, is very much becoming more complex as it matures. Ergo… more opportunities to stumble? Hopefully, they can keep it on the rails and not fall victim to the past woes that some of their own Bigs have at least partial ownership of elsewhere in the industry.
That little burst of sunshine aside, it really was a thought-provoking session. See it for yourself here, and feel free to leave me a comment below.