I know...calling something a mistake and then saying you don't regret it in the same breath is a little contradictory. But stick with me, because that tension is kind of the whole point.

"Wake Up Honey, It's Time For School"

I was in high school when I found the Cisco Networking Academy. While other kids were figuring out what they wanted to do with their lives, I was subnetting. While they were at football games, I was in a computer lab watching routers exchange BGP routes like it was the most exciting thing I'd ever seen...and honestly, it kind of was.

The Academy doesn't just teach you networking. It sells you a worldview. Cisco gear is everywhere. The CLI is king. And if you learn it well enough, you'll never be without a job. That pitch lands a little differently when you're 16 and trying to figure out what adulthood looks like. I didn't just take the class...I bought in completely. The certification, the mindset, the vocabulary, the whole ecosystem. I chugged it and asked for a refill.

What Does The Kool-Aid Taste Like

Some things Cisco burned into me so deep they'll never come out. 'conf t' before I've had coffee. 'show run' as a reflex, not a decision. The subnetting math that lives rent-free in my head whether I need it or not. Packet Tracer labs that I genuinely looked forward to in a way that probably should have been a warning sign about the kind of adult I was going to become.

The CLI felt like a language I was born to speak. Consistent, logical, predictable. You always knew where you were and what to type next. For years, that was just what networking felt like and I had no reason to think it felt any different anywhere else.

Living in a Bubble

Here's the thing about drinking the Kool-Aid young. You don't realize it's Kool-Aid. You think that's just what water tastes like.

For a long time, Cisco was networking to me. Not because I was arrogant about it. I just genuinely didn't have a frame of reference for anything else. Every answer was a Cisco answer because every question I'd ever been asked came from a Cisco classroom. The bubble wasn't uncomfortable. It was warm and familiar and full of commands I already knew.

I didn't know what I didn't know. And that's the most dangerous kind of not knowing.

Enter Juniper

Opening a Junos config for the first time felt like coming home to find someone had rearranged all the furniture and then left a note saying "actually this layout makes more sense." They weren't wrong but I was still annoyed.

My first three questions were: where is the config, why is everything in a hierarchy, and who do I talk to about getting my old CLI back? The answer to all three was "you'll get used to it," which is what people say when they know you don't have a choice.

What really sold me was the commit workflow. In Cisco IOS, you make a change and it's live. Immediately. You learn to be careful or you learn from consequences of doing things in the wrong order. Junos stages everything first. You make your changes, review them, then commit when you're ready. And if you want an extra layer of protection, 'commit confirmed' applies your config but automatically rolls it back in five minutes unless you confirm it. It's Tim Robinson's equivalent of "you sure about that?"

I have never felt more seen by a CLI in my life and my current DevOps mindset was pleased.

Sit Down (hol' up), Be Humble (hol' up)

Learning Juniper this year made me a better engineer. Not because Juniper is better than Cisco in every context...that's debatable, and honestly it's not something I want to write about at the moment. But because learning a second way of thinking about the same problems forces you to ask why in a way you never had to before.

Single vendor environments are comfortable by design. You get fast, you get confident, and you stop poking at the foundations because why would you? Juniper made me poke at the foundations. Some of them were solid. Some of them were just muscle memory I'd never questioned. Both things were good to know.

So was drinking the Cisco Kool-Aid a mistake?

Kind of. It gave me tunnel vision for longer than I'd like to admit. It made my first Juniper config feel like I'd forgotten how to read. It built habits I'm still consciously unlearning in some cases.

But it also gave me a foundation that holds up everywhere I've taken it. The Networking Academy taught me how networks actually work, not just vendor syntax, but real concepts that translate to any box with a CLI. That foundation is the reason I could eventually learn Juniper at all. You can't appreciate a second language if you never fully learned the first one.

So was it a mistake? Sure. Do I regret it? Not even a little. The Kool-Aid built the foundation. Juniper just upgraded the beverage. Espresso now, almond milk, and enough self awareness to admit I didn't know what I was missing. That's growth. Probably.