Thread regarding Cisco Systems Inc. layoffs

Nothing will make Cisco great again

nothing will make cisco great again. not even if you fired everyone and only took in

the IOS-XE, XR and NXOS codebase is a fragmented mess of 100s of buggy components spread across dozens of teams and VP/director empires in 5 major locations (sjc, ott, rtp, england, bgl). nothing can make it reliable when a feature needs some 15 comps to work smoothly together.

nobody wants to lose their power, or clean up org boundaries or merge and collapse stuff into leaner formats. the PD / PI separation is a walking train wreck. PD teams find things broken when PI does some change for xyz feature and PI has no resources to test properly on all types of hw.

a startup would throw out most of the old code and start afresh. unfortunately there is a long 15 year tail of deployed code to support and put band aids on.

yes cisco's overall engineering team quality has declined from the heydays but thats only part of the story. if you rolled back and time and brought in the same teams on the current situation, they'd still end up in the same mess.

Reposted from @WKoF355-3kny

by
| 2030 views | | 4 replies (last ) | Reply
Post ID: @OP+WNES46O

4 replies (most recent on top)

I heard that another LR massive layoff coming in March, CX will be on spotlight again.

by
| | Reply
Post ID: @azsc+WNES46O

I recall the days of the old sonet mailing list. Some real gurus used to teach there. Very learned and willing to share.

by
| | Reply
Post ID: @1qmx+WNES46O

Late 90s to early 2000s classic Cisco was email alias “flaming”, for internal product / TAC tech support. People would post researched questions to mailer aliases, and the alias owners would make usually make good effort to assist you in resolving the issue. Your responsibility was to properly research the issue, and ask a well thought out purposeful question. Failure to research or ask a well thought question would often result in a snippy remark or candid questioning of your logic. People learned, were candid, and sometimes were perhaps slightly embarrassed when they didn’t follow directions of the subject matter experts. Nowadays, most would potentially look for a safe-space or be offended by such candid feedback. Times have changed. Being innovative sometimes takes having thick skin, the days of the mailer alias flame, and quick innovation and resolution, and the diving customer catch are long gone.

by
| | Reply
Post ID: @1bfu+WNES46O

Cisco used to be the big dog in moving packets from A to B. They had the ASICs, the chassis, and the software. They were close to their customers and implemented the features the customers needed to build the networks they envisioned. Cisco's leadership was unquestioned, and it got to the point where CIOs asked Cisco to tell them what to buy. Nobody got fired for buying Cisco, and if I build a network the way Cisco tells me to, it will work great and my boss will think I'm a star.

Then their leadership in ASICs started to wane, and they started to move to 3rd party off-the-shelf chips. Then competitors caught up. Then networking boxes became a commodity.

Think of Cisco like Microsoft: one of the good things about Microsoft was their focus on backwards compatibility, which meant everything to businesses through the 90s. But then each advance became harder due to the need to maintain that compatibility. Cisco suffer a similar fate. New innovations break older networks, and suffer from customer inertia (don't fix what isn't broken) whereas new entrants and competitors don't have that problem.

With the leadership in enterprise and SP networking diminishing, Cisco attempted to move higher in the stack, with services and other devices. Their device experiments have mostly failed - even the startups that had mindshare when bought, were ruined.

Now it's a software-centric world, and Cisco don't have it in their DNA. Everything fails, and it's frankly embarrassing.

Question to people still at Cisco: Which BUs are still innovating and producing good products?

by
| | Reply
Post ID: @eha+WNES46O

Post a reply

: