Yes - I am talking to all of you incompetent VPs, Senior DIR and DIRs. That's the post.
28 replies (most recent on top)
have ever see a post that has more likes (on this site)???
Get rid of specialists
@10c - so ad hominem attacks and outright lying!
initial trouble was done decades ago mostly
was preceded by "Many others here just use racist tropes ignoring the fact that the..." and followed by "...in the US by people without even the most basic software skills." The full sentence has a very different meaning. It refers to the initial trouble from way over 25 years ago which does not deny the totality of the trouble that went on across what is now over more than four decades across what became four different broken routing and switching operating systems.
if its decade old code you can not fix it in all these 25 year?
The number of software engineers that Cisco has churned since its founding over 40 years ago has to number well in the tens of thousands where there were long stretches when Cisco spent 75% of its development budget failing to fix the code so clearly they were not capable of fixing all the bugs over that more than 40 year timeline. Massive numbers of new bugs were added along the way.
seems like people LRed you blaming SA warning on your head.
I followed ISO 9000 process, including running static analysis and correcting rather that ignoring warnings before checking in code. I was also able to go back to large blocks of code I had written years earlier in critical paths and noted there were no changes during that time which meant it had sufficient functionality, performance and quality the first time.
please vote for vivek !
Just because he's worth $2.5B doesn't mean he knows anything about government, but then again you apparently still work for Cisco and you don't know anything about software so I'm guessing that's why you're such a big fan.
initial trouble was done decades ago mostly
mam.. you are not getting the point.. what are people doing all these 25 years? if its decade old code you can not fix it in all these 25 year? you stuck with SA and comiler warnings? seems like people LRed you blaming SA warning on your head. please vote for vivek !
@xs thanks vivek!
this guy/gal really stuck in late 90's,
You think the 2020s are the 1990s. That's massive dysfunction.
Its easy to blame 25 year old code
The cr-p code from a company founded at the end of 1984 had 25 year old code by 2001? That's also massive dysfunction.
The reason you chuckle heads use ad hominem attacks is either because you know the code has been garbage the entire time and can't face that fact or far worse you don't know the code has been garbage the entire time.
Many others here just use racist tropes ignoring the fact that the initial trouble was done decades ago mostly in the US by people without even the most basic software skills. The Indian people I worked with at Cisco were equally as bad as the white people I worked with at Cisco. Cisco's problems weren't ethnic culture, they were corporate culture.
this guy/gal really stuck in late 90's, not sure why he/she is hanging around this forum. May be still has csco stocks(options) in portfolio.
effectively gcc 2.95.3 which wasn't released until March 2001 and the port went into the 2010s stabilizing on gcc 4.2.1
Its easy to blame 25 year old code, what the heck people are doing all these 25 years?.
This thread is not the right one to discuss this topic.
Our competitors joke Cisco is a top heavy company many talkers little doers
nope, i have seen all those, seems like you are stuck in late 90's.
The starting point of the port was effectively gcc 2.95.3 which wasn't released until March 2001 and the port went into the 2010s stabilizing on gcc 4.2.1 which was released in July 2007. If you were really there you'd know what lead to having to rewrite so much code over a decade.
The other issues persisted at least well into the 2010s when I left Cisco, and the bugs I have to deal with as a customer in the 2020s shows Cisco still can't do basic development and testing. Think "when I turn on the box do all the major subsystems actually come up or is the only solution rolling back to an earlier release?" noting these kinds of problems go back decades across a variety of platforms.
You also likely arrived after the ten year "port" of a major OS to a newer version of GCC
nope, i have seen all those, seems like you are stuck in late 90's. Now a days people at Cisco do not add boat loads of code, just bug fixing and breaking things and playing politics to climb corporate ladder.
that is because 3rd world experts are not able to even do bug fixing properly, its not a result of adding boat load of code at once.
I am guessing you are not in development side of things.
I'm guessing you are one of the clueless children who never ran static analysis on any major Cisco code base over more than 30 years. You also likely arrived after the ten year "port" of a major OS to a newer version of GCC or the shutdown of development ever few months decades ago to hide warnings each time they exceeded 100,000 on another OS. These code bases were destroyed internally from the start here in the good old US of A.
@hs deflection is your forte.
You need to use that skill in a different field - not it tech.
Above is not happening at Cisco any more.
The bugs I've had to deal with as a customer recently say otherwise.
that is because 3rd world experts are not able to even do bug fixing properly, its not a result of adding boat load of code at once.
I am guessing you are not in development side of things.
Above is not happening at Cisco any more.
The bugs I've had to deal with as a customer recently say otherwise.
never seen a post with this many likes
i guess the forum approves the message
I'm far more concerned with those working overtime to check in massive damage to the code bases.
Above is not happening at Cisco any more. Only bug fixing for engineers and promotions for those looking over the shoulders.
Deadwood didn't leave Cisco with so many bugs that the lions share of the development budget went to bug fixing. I'm far more concerned with those working overtime to check in massive damage to the code bases.
this post has a lot of engagement
i wander why
@cb why do you say Cisco will not change?
Don’t forget ab the “leaders” who gatekeep and steal the ideas of the ICs under them too! We should be able to survey our bosses to the VPs.
who is down voting these comments? is dead wood drifting thru the layoff forums?
@a7 💯
At some point, there needs to be real transparency around bloated administrative layers and whether they are creating proportional value. The people building, selling, supporting, and moving the business deserve a fairer share. Every company is flattening. If Cisco does not do the same, it is only a matter of time before employees, customers, and the market start questioning Cisco’s relevance.
Two things are true:
Cisco may be the most over-managed company in the US.
Cisco will not change.
💯
Cisco can easily lay off 50%. The company is full of deadwood who talk big and deliver zero.
that dead wood holds you by your paycheck.
too late, LR list already submitted.