Hit in CX today.
27 replies (most recent on top)
@4thd+1nyM6ze5, keep trolling. It's easy to brag anonymously about "regular promotions and hight IPFs every year." Read the hundreds of posts here complaining bout how hard it is to get promotions at Cisco. You must be an SVP by now, huh?
I wasn't desperate or pathetic to come back as a red badge. I'm not a lackey and I don't work in a basement. I worked in IT my first time around and I got cut as part of a cost-cutting measure because I had too much experience and cost too much for the IT employee budget. I was called by a Cisco manager who knew me and wanted me on his team and asked to come back. I can in as a red badge because he could get that req opened immediately and could flip it to an employee role in a year. To come back as an employee directly, it would have taken 1-2 yrs. I've probably got as many yrs as a Cisco employee as you do, so cry me a river.
My initial comment was about how "knowledge" is lost when Cisco lets people go. That "knowledge" may be documented, or may not be, and even when it is documented, as often as IT switches wiki tools, it's easy to lose documentation if the new people don't know what to migrate and keep. Remember these: IWE, WebEx Social, Jive and then ICX/IBM Employee Communities? I commented how the team I left failed to keep their sh-t documented and protect their core "knowledge" and then IT was having to reach out to me about some old, legacy server, but you think I'm the incompetent one. Learn to f-ing read instead of skimming it and making assumptions to stroke your ego.
ip route 0.0.0.0 255.255.255.255 my.lr.now.please
Right, I don't understand networking, even though I get regular promotions and high IPFs every year. I'm not the one getting LR'd and then being so desperate and pathetic to come back as a red badge - if that should ever happen to me, I'd have a job at HPE, Juniper, or Amazon tomorrow. Cisco will keep me around because I would cost them more in business than what they are paying me.
You on the other hand, are likely some Cisco IT lackey working in the basement, which is about as low as it gets.
So many people crying in their beer on this site over being LR'd - blaming capitalism, age discrimination, yada, yada, yada... after reading your crybaby post, I'm starting to think the majority of these LRs were actually deserved.
Tell me you don't understand networking without telling me you don't understand networking, yet you work for a networking company.
The phrase "I work at Cisco" gives you an 80% hit rate. Large scale network operations involve a wide range of technologies and even at the highest technical levels the experience of most at Cisco tends to be surprisingly narrow. I'll upvote anyone who can cite Chambers' quote which is most responsible for this condition.
@3cyp+1nyM6ze5 As a third party observer the other guy was obviously right. Cope harder.
@3rkr+1nyM6ze5, learn to f-ing read.
It wasn't my server build as I was no longer on the team. My stuff was documented when I was responsible for the servers. I was only responsible for providing the server and the OS when it was built and deployed. The app team was responsible for deploying the application(s) that ran on it and documenting that setup. My documentation was still available, but it was on some older internal wiki site that was decommissioned in favor of some newer internal wiki site and the person(s) who came after me didn't see fit to migrate that content, so that's not my fault. The fact that the app team failed to document their deployment, the dependency of the IP address or need to update a firewall if it changed, etc. is not on me.
No IP addresses were hard coded in a program. The processes connected to a server by name, which uses DNS to resolve the IP address of that host. But because that host is behind a firewall, and firewalls only let connections through based on rules using IP addresses, it didn't match any rules due to having a new IP address. Tell me you don't understand networking without telling me you don't understand networking, yet you work for a networking company.
Funny how I got asked to come back to work on another team and have been here ever since, while the original team has had 80% turnover due to poor management. They couldn't even manage to keep their documentation up to date, keep the emergency points of contact for the server up to date, etc.
Keep on trolling since it obviously makes you feel better about yourself by trying to tell others how bad they are. You fit in perfectly with all the others at Cisco that are dragging the company down.
So let me get this straight, you failed to document your server build and you hard coded IP addresses in the program, and that's somehow the company's fault? No wonder they LR'd you!
@2hak+1nyM6ze5, I wish I could upvote your comment 100x.
I give you the pure cynicism of unbridled capitalism that never bothers thinking about the human impact or what those LRs do to the company's future. Low morale, expertise vanished, stalled processes, difficulty recruiting : conveniently ignored. As long as someone profits, nothing else matters.
The loss of expertise and corporate knowledge is probably the biggest loss. Sure, you can re-hire contractors or less experienced employees to replace the person you LR'ed, but how many things are considered too basic to document because "it's just known" by everyone on the team and then after 2-3 yrs, the team is gone and no one knows that "basic" stuff.
I was LR'd and came back as a contractor about 18 mo later to work on a different team. I had been responsible for a server refresh a couple of yrs before I was LR'd and it turns out that it came up for a refresh again while I was a contractor on the new team and the host support info wasn't updated to remove my name as a point of contact, so I was contacted and had to refer them to the old team's manager. Turns out no one left knew what that server's purpose was, if it was still needed, etc. and they turned it off. Suddenly lots of stuff broke because it was doing back-end automated processing. When they turned it back on and tried to replace it with a new server, I got called in the middle of the night because they couldn't "find" the processes that needed to be migrated to run on the new server and didn't realize that some of the processing it did accessed files on another server behind a firewall and could no longer reach it because the IP address had changed. I had to tell them I couldn't help them as I didn't have access to the old or new server and that I wasn't on that team any longer, and as a contractor, I couldn't work more than 40 hrs per week and I'd put in my 40 hrs by 5PM Fri and it was now 3AM on Sat, so leave me the he-l alone.
It's amazing how the bean counters will calculate how many people need to be cut, and by when, in order to minimize how much they have to pay the cut people, but they don't count the cost to the company. I got cut by a company that wanted to close an office in TX. They let 7 people go, including me, the Monday after Thanksgiving. Between the 2-wks notice, plus the 2-wks severance for signing the agreement, my employment terminated on Dec 28th. That company paid out the entire year's 401(k) employer matched funds to all employees a/o Dec 31, so they didn't have to match my entire year's 401(k) contributions saving them 4%. Then, 6 months and a few days later, now that that office was down to 49 employees, they laid everyone off the Friday following the early-to-mid week 4th of July holiday and managed to avoid having to provide job search services because they didn't meet the 50 employees in a 6-mo period window threshold. The funniest thing about my sudden termination was that I'd worked over the weekend trying to build and deliver a release to QA because development had not finished writing all the necessary code changes before Fri and in the development rush, they'd made a bad merge that left a directory empty, so when QA tried to start their tests, they had a whole series of stuff fail. I had the code checked out Mon morning and was trying to fix the bad merge when I was called into the conf room to be terminated, and I was the only tool admin, so when they shut off my workstation and disabled my account(s), no one else could use admin rights to uncheckout the code so they could check it out and commit the fix and had to call the tool's support hotline to have support tell them how to elevate someone to an admin. It took them 3 days to get the code built and packaged for QA when it could have been done in just a few hours if they'd called me into the conf room later in the day or the next day. I had zero sympathy for them given that they screwed me out of my 401(k) match. And I had to rub in it to all of those people who tried to tell me how "good' 4 weeks of severance was and ask them how they liked it that following July.
Capitalism at it's finest.
LRs almost always have a positive impact on stock price because they're considered a cost cutting measure which increases margins. I give you the pure cynicism of unbridled capitalism that never bothers thinking about the human impact or what those LRs do to the company's future. Low morale, expertise vanished, stalled processes, difficulty recruiting : conveniently ignored. As long as someone profits, nothing else matters.
"Really? Then why are they almost always announced during earnings calls?"
Cisco has conducted layoffs for 15 years, I believe layoffs are priced into the stock price by now. Maybe layoffs are a good distraction to avoid discussing our products?
A corporation that makes money solely from network equipment isn't growing.
Layoffs are inconsequential to the stock price.
Really? Then why are they almost always announced during earnings calls? Look back at the stock trends leading up to an earnings call, followed by the LR announcement that they're taking cost cutting measures to "realign resources to priorities" and see what the stock prices do the next couple of days.
July 17. Mostly contractors and blue badges outside the US.
"No major LR will happen before end of Q4 and numbers are announced. That would ki-l the stock price."
Layoffs are inconsequential to the stock price. The only thing that would harm the stock price would be new competitors. Huawei allowed to sell networking equipment in North America... or Arista obtaining lucrative government contracts.
Neither of those will happen. Cisco will continue to print money, and the ELT will get their 6th beach house.
19 LRs are happening.
No major LR will happen before end of Q4 and numbers are announced. That would ki-l the stock price. It works out better if Chuck presents the bad numbers and then says that Cisco will (insert FY24's buzzword for layoffs) x percent to focus on y priority. That'll keep the stock from tanking and that is the name of the game when your salary package is mostly options.
What's the over/under on CX being spun out into it's own company fully owned by Cisco (for now)? That would put an arms length distance between that bloated train wreck and the rest of Cisco.
LR before fiscal year end are usual red badge and they don't count. They're non-employee sc-m.
Was told to ask team don't take PTO if no emergency, will be announced next week in collaborate BU.
LRs rarely happen 2 weeks before end of fiscal. Next month all bets are off.
please stop the "19" troll posts
Have not heard about it. Was on a call with a couple of CX folks today. Fake news!
Troll post. No LRs are occurring
Fake news
You guys know what's the LR Package for US ?
It’s part of the larger restructuring effort for Q4. Upwards of 1.9k across multiple BUs are impacted. Heard from a reliable source.
Region, please.
CX who? Such a large crowd in there. Wonderful bouquet
Which portion of CX? How many? What’s the notification date? Last date? Severance like?