Slashdot Mirror


Cisco Exec: Turnover In Engineering No Problem

alphadogg (971356) writes The engineering reorganization currently underway at network giant Cisco Systems is intended to streamline product development and delivery to customers. That it is prompting some high profile departures is an expected byproduct of any realignment of this size, which affects 25,000 employees, says Cisco Executive Vice President Pankaj Patel, who is conducting the transformation. "People leave for personal business reasons," Patel said in an interview with Network World this week. "Similar transformations" among Cisco peers and customers "see personnel change of 30% to 50%."

148 comments

  1. we need the freshest talent! by Anonymous Coward · · Score: 5, Insightful

    No old people, they have too much experience! We need to do things fast and poorly! So we can sell total crap to complete idiots!

    1. Re:we need the freshest talent! by Anonymous Coward · · Score: 0

      Before you can have better management, you're going to need a better America.

    2. Re: we need the freshest talent! by Anonymous Coward · · Score: 0

      Amen brother. Let's see how it plays out in 3 to 5 years.

    3. Re:we need the freshest talent! by Anonymous Coward · · Score: 5, Funny

      We don't need a better America if we can just improve America's approval rating. Fire the engineers and hire more marketing.

    4. Re:we need the freshest talent! by Anonymous Coward · · Score: 1

      Cisco doesn't need to streamline product development, they need to streamline product lines.

      They also need to stop hiring Indian engineers...not that they're all stupid, but many of them have some really bad cultural traits when it comes to product design, support and business.

    5. Re:we need the freshest talent! by Anonymous Coward · · Score: 1

      They also need to stop hiring Indian engineers...not that they're all stupid, but many of them have some really bad cultural traits when it comes to product design, support and business.

      Well, with a Executive Vice President and Chief Development Officer named Pankaj Patel, a Senior Vice President and General Manager named Ravikrishna Cherukuri, and a Senior Vice President and General Manager named Ravi Chandrasekaran, I don't think they will stop hiring them.

      I wish I knew the nationalities of the people that are leaving, and the nationalities of the new hires. I wonder if Americans are being replaced with non-Americans. I'm not saying that's happening - just wondering.

    6. Re:we need the freshest talent! by Anonymous Coward · · Score: 1

      German here - just here to say that I went to school with 1 of the 3 Indians listed above, and I can tell you from my time around "him" that there is absolutely a pro-Indian bias at Cisco, and it has been going on for quite a long time. I'm not saying the reverse doesn't happen elsewhere, but I am saying that it is /definitely/ in play here too.

    7. Re: we need the freshest talent! by Anonymous Coward · · Score: 0

      As a former Cisco person I can tell you that there were very few middle aged or American-by-birth engineers in the development areas of Cisco for many years already.

    8. Re:we need the freshest talent! by Anonymous Coward · · Score: 0

      So what? More socialism? More crony capitalism? More bureaucracy? I'll pass.

    9. Re:we need the freshest talent! by Anonymous Coward · · Score: 1

      As opposed to selling volumes of old crap that still doesn't do basic features becuase you need to speak *every single version * of IOS fluently to figure out what the old configurations were.

      Been there done that. And have you noticed that, at its core, Cisco ASA's are actually a rebuilt CentOS? I took apart the installation tool a few years ago because it demanded a single disk image of over 200 GB, when a little rewrite allowed the OS to be one quite small disk image and the scattered, voluminous log locations go *on a separate disk that you can throw away if they get excessive, the way god intended*. It made virtualizing them much safer and much, much easier.

      Anywy, the CentOS core means that we can expect them to lose capability profoundly in the next few years as RHEL 6 and CentOS 6 get too old to run on the latest hot fiber and network hardware, and they have to upgrade to the over-centralized morass that is RHEL 7 and CentOS 7 with systemd sucking away CPU cycles for logging and service spew that you don't want and should, franly, never have on a stripped down OS.

      I got to walk a Cisco engineer through this little coming downgrade. I'm bringing popcorn to the meetings where they get to explain that that next expensive upgrade will actually hurt performance.

    10. Re:we need the freshest talent! by Anonymous Coward · · Score: 0

      Yeah? Well I went to college with 7 of the 3 Indians listed above.

    11. Re:we need the freshest talent! by Austerity+Empowers · · Score: 1

      You should have no trouble getting a job that requires 5 years of Swift experience or 25 years of Java experience then.

    12. Re:we need the freshest talent! by Anonymous Coward · · Score: 0

      Joke is that are ~ 46,137 people 'John Smith' in the USA. by extension there may be as many as 150,000 people named Pankaj Patel in India.

    13. Re:we need the freshest talent! by Anonymous Coward · · Score: 3, Interesting

      Well, I was one of the (older) American engineers let go in this most recent layoff (of more to come, I am afraid). The development group I was a part of had multiple layoffs (older white engineers) and the future product we were developing has been transferred to India for further development. I don't think this will be the last time this is done ...

      Cisco is transforming it's development organizations from a product centric BU approach, with combined marketing/software/hardware development, to a more centralized approach. Hardware engineers, instead of being associated with a particular product line, will now be viewed as part of a central resource pool, a commodity. They will come and go on a product as necessary.

      This may be more 'efficient' from a financial corporate bean-counting point of view, but what it does is cause all the product specific history and knowledge to be lost, as there is little engineering continuity.

      What it really means is current Cisco management has no idea on how to engineer products; they are not engineers, but are instead bean-counters. Cisco has begun its transformation all right, but I believe it is more to launch itself on a death spiral, much like DEC did in the early 90s when its management lost touch with its engineering roots and became marketing and finance driven.

    14. Re:we need the freshest talent! by ScrewMaster · · Score: 1

      Hewlett-Packard did much the same under Carly FIorina.

      --
      The higher the technology, the sharper that two-edged sword.
  2. Engineers have no future. by Anonymous Coward · · Score: 0

    Just today, I sat in on a lecture that basically said, engineers can expect about 2 years of work and then be put on the chopping block. Get used to it they say.
    Screw that! Do your own startup! Unionize! Fight back at the 'man'. Come on you American wimps! You can beat Cisco with something new!

    1. Re:Engineers have no future. by nucrash · · Score: 4, Insightful

      I can tell you from a company that continually recycles their talent that after a while, watching the talent go out the door and having new blood learn how to fix old problems all over again gets really old. A company that treats their engineers like second hand citizens is a company that I won't invest in. They won't have a future.

      --
      Place something witty here
    2. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      No future? That's great! As soon as Earth hits rock bottom, Cochrane will be depressed enough to invent warp drive. If you want to help him out, get into the liquor business now. He's going to need to be super duper drunk to discover the space warp.

    3. Re:Engineers have no future. by tsotha · · Score: 5, Insightful

      That's my experience too. It's healthy for a company to lose a few percent of its people - after awhile you accumulate dead wood. But once you start treating your technical people like drop-in disposable parts, nobody actually cares if the company is successful. Why would they?

    4. Re:Engineers have no future. by silentbozo · · Score: 5, Insightful

      Agreed. A manager who says that turnover is not a problem is a manager that has no inkling of what engineers do, what exactly their company produces, or how badly they are in trouble when knowledge and experience walk out the door. Either that, or they're lying to your face.

      There's that tipping point when the work gets harder, the code is even more rotted, the "process" is even more constricting, because they know something is wrong but they need to "measure" everything to figure out why. That's when people are running, not walking out the door.

    5. Re:Engineers have no future. by sjames · · Score: 4, Insightful

      Problem is, it's not the deadwood that leaves.

    6. Re:Engineers have no future. by Kylon99 · · Score: 5, Insightful

      "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." - Red Adair

    7. Re:Engineers have no future. by wrook · · Score: 5, Interesting

      Not sure how many employees Cisco has left (didn't RTFA), but a quick glance at Wikipedia indicates that they still probably have more than 50K employees. Of course not all of them are engineers, but I have worked in organizations of that size before. If my experience is common (and I believe it is), they have already gone well pas the point you indicate. Even if they only have 5,000 engineers, it is practically impossible to hire anywhere near that many good people. You are stuffed to the rafters with dead wood. Not only that, but quite a lot of that dead wood will have made it up to management level -- the engineering and political skill sets are orthogonal, and people who are good at politics get promoted.

      This means that the management probably has absolutely no idea how to separate the good engineers from the bad. In other words, just by growing the company to the size that they have, they are in a position where they can't evaluate talent. A 30-50% turnover rate is another way of saying 2-3 year attrition rate. I agree with the manager. This is common in large companies. Because they are unable to distinguish good from bad, they simply cycle through the available talent in a random fashion. They have chosen to go with quantity over quality and his statement makes absolute sense.

      I don't think it is possible to do (for a variety of political reasons), but lets pretend that a company of 5000 engineers could cut back to their top 10% of talant. You'd end up with a solid core of 500 good engineers. Then, let's pretend that you knew how to do whatever it took to keep that talent for 10 year. Would the company be better off? I'm not so sure. I work in a former start up that is trying to scale itself up now. Since I'm fairly senior (possibly indicating I'm better at politics than engineering??? ;-) ) I'm exposed to more of the business end of the company. The CEO is demanding that we double our development group. He knows that this will throw the group into chaos, but he also sees a way to grow the revenue of the company by an order of magnitude if we can do some very specific work. Crucially, it doesn't really matter how badly we do it. It just needs to mostly work.

      Which is better? Grow your revenue by an order of magnitude today and destroy your development team, or carefully grow your development team and trust that opportunities will show up when the team is able to handle them? It's a very difficult call. Personally, I can't fault companies who expand quickly (like Cisco did) and who take the opportunities that were presented. That's what the business guys are paid to do.

      Luckily, the company I work for is wholly owned by the CEO and he has decided (for now anyway) to adopt a more sustainable growth for the company. Again, I am very lucky that our CEO views our team as being the engine of the company and values long term viability. He doesn't have investors trying to take their money out and has the ability to make the choice that leads to a very good place for me to work. Not every company has that luxury.

    8. Re:Engineers have no future. by Anonymous Coward · · Score: 1

      He's pretty much required to downplay it, otherwise they would have to honestly state in their 10-K that turnover would affect future profits.

    9. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      Don't forget the jukebox business! Zefram needs his music, for inspiration.

    10. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      Luckily, the company I work for is wholly owned by the CEO and he has decided (for now anyway) to adopt a more sustainable growth for the company. Again, I am very lucky that our CEO views our team as being the engine of the company and values long term viability.

      Hooo boy. Guess who's on the chopping block next? I hope you've got your resume prepared, because the door is about to hit you on the ass.

      Don't be caught out. Get that resume ready, because the CEO is just going to ditch you and go ahead anyway. Do you really think you're going to stand between him and his luxury yacht and retirement parachute?

    11. Re:Engineers have no future. by JaredOfEuropa · · Score: 5, Interesting

      That's what is being taught in business school. Actually, it's a few things. "It's bad to have your company depending on a single person", which is true. "Standardizing jobs / positions makes it easier to shift people around, making you less dependent on any one of them, and makes recruitment and organizing the work easier if you do this in line with the rest of your industry", which is also true to a degree. Never mind the many negative effects of standardizing jobs; the message to take away from this is not that people are drop in replaceable parts. If you did all this correctly, it'll be easier to replace a leaver, but it doesn't mean that replacing one person doesn't come at a high cost, and doesn't mean that adding or replacing many people at once is still extremely hard to do without messing up the works.

      Sadly I see my share of managers who do get the idea that people can be swapped in and out at no cost. Needless to say their teams are not the high performers.

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    12. Re:Engineers have no future. by Anonymous Coward · · Score: 3, Interesting

      Agreed. A manager who says that turnover is not a problem is a manager that has no inkling of what engineers do, what exactly their company produces, or how badly they are in trouble when knowledge and experience walk out the door. Either that, or they're lying to your face.

      There's that tipping point when the work gets harder, the code is even more rotted, the "process" is even more constricting, because they know something is wrong but they need to "measure" everything to figure out why. That's when people are running, not walking out the door.

      Oh god, the "metrics" thing. They did that at my last job, to the point it got ridiculous because you spent more time trying to update the 10 different 'tracking systems' than you did doing actual work. It even got to the point where to take a vacation day you had to update the group sharepoint calendar, plus two other systems, plus send email on it to 3 different people (any one of which could reject the request for whatever reason). It got to the point where I was *glad* when they laid me off because the technical part of the job (the 'interesting' part) was disappearing into a realm of spending 50%+ of your time updating the various systems for keeping track of the 'metrics' on what you were really supposed to be doing (or what I thought I should be doing - actual work not 'make work').

    13. Re:Engineers have no future. by DarkAce911 · · Score: 2

      a 30-50 percent turnover rate is not sign a of a healthy company, normally companies that are doing that, had a massive downsizing and got rid of the wrong people. You don't lose half your companies employees if things are going well. I expect that hiring is way up at their Indian and Chinese design centers considering who they have in charge of their Engineering team.

    14. Re: Engineers have no future. by Anonymous Coward · · Score: 2, Funny

      "... deadwood that leaves ..."

      Aha! I see what you did there.

    15. Re:Engineers have no future. by drinkypoo · · Score: 1

      Even if they only have 5,000 engineers, it is practically impossible to hire anywhere near that many good people.

      1: Cisco didn't hire all the people who work for them. They made acquisitions.
      2: How many good engineers do you think there are in the world, and how many of them do you believe is it feasible for Cisco to have hired? Because I'm suspecting a massive dose of arrogance on your part, here.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    16. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      "stuffed to the rafters with dead wood. Not only that, but quite a lot of that dead wood will have made it up to management level" Ayup - and it seems that Panka is one of those, since he clearly has no idea about what engineers do or what their value to the company is.

      Just like Microsoft, it will take Cisco a long time to die.
      (Hey, someone has to put a MS spin on every story - now can I get a prize?)

    17. Re:Engineers have no future. by RobertLTux · · Score: 1

      And given in the field of "Hell Fighter" he basically INVENTED large chunks of the tools and protocols he knoweth of what he speaks.

      --
      Any person using FTFY or editing my postings agrees to a US$50.00 charge
    18. Re:Engineers have no future. by Ol+Olsoc · · Score: 2

      (Hey, someone has to put a MS spin on every story - now can I get a prize?)

      Netcraft confims, you win a Beowulf cluster of internets.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    19. Re:Engineers have no future. by Zontar+The+Mindless · · Score: 3
      --
      Il n'y a pas de Planet B.
    20. Re:Engineers have no future. by BarbaraHudson · · Score: 1

      Which is better? Grow your revenue by an order of magnitude today and destroy your development team, or carefully grow your development team and trust that opportunities will show up when the team is able to handle them? It's a very difficult call. Personally, I can't fault companies who expand quickly (like Cisco did) and who take the opportunities that were presented. That's what the business guys are paid to do.

      Hey, it worked out great for NORTEL.

      (or at least for the stockholders who managed to sell out before they went bankrupt)

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    21. Re:Engineers have no future. by __aaltlg1547 · · Score: 1

      Exactly so. And there's also this to consider:
      Historically, there were two major changes in how people worked, in order to greatly increase productivity. The first was the transition from everybody-must-be-a-generalist (e.g. any subsistence culture) to specialization and trade in goods and services made or performed by experts. The second was industrialization. In the industrial society, most people are not experts at anything, but their work consists of doing one very small task repetitively.

      In the technical workplace, a workgroup consisting entirely of (somewhat replaceable) generalists means that they never work on any one kind of problem long enough to become expert at it, unless it's very broadly defined like "coding a specified routine in Java according to company standards." Such people are replaceable because you can always hire competent Java programmers and teach them to code to company standards and understand how routines are specified in your workflow.

      But you also need experts in defining what routines need to be coded and how they are supposed to interact to achieve big picture goals, and you need creative people to define what big picture goals should be and decide which are most worth pursuing. Those people are hard to develop and hard to replace.

    22. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      You must not invest much. Everybody does this. Its a disease.

    23. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      Going to post anonymously for this one. Cisco had 2 switching/routing teams that took the brunt of this round of cuts. A few years ago, they acquired a start up called Nuova to build datacenter solutions. They made a lot of noise about FCoE but that was likely a smokescreen for the rest of the datacenter products they were developing. FCoE meant they were developing their own switches and while the business unit that Nuova was part of grew at a rate that met or exceeded shareholder expectations, they left it alone. But things slipped a bit (granted, it was company wide, UCS was still profitable though), and that was all the excuse that was needed. The team responsible for the Nexus line has been folded in with the older Cisco switching/routing team. They have continued to ship jobs over to India. If anyone is familiar with UCSM, that engineering is being done in Bangalore, that's coded in San Jose), a lot of QA has been moved over there, but there have been just enough issues with other engineering done there that not too much went that way on this round. Hardware engineers took a number of cuts. I'd say to expect fewer ASICs from Cisco (but consider the networking companies that don't build any silicon at all). They have stated they want to focus on software (considering things like UCS Director and UCS Central, this makes some sense). They are trying to adopt Agile practices, part of that are some work environments have been converted to being totally open, there are some lockers employees can use for the day to secure stuff, but they otherwise have a desk in an open floor plan (it looks like one of the accounting floors from an old movie). I suspect new grads have fewer objections to that environment than experienced engineers closer to the middle of their careers. I expect to see a continued movement of jobs to Bangalore. There are those managers fighting tooth and nail to keep engineering here, but digging around the news for the past 5+ years shows a steady stream of jobs moved over there, done in such a way that they don't trigger the 'outsource shaming' laws in the US. I don't think the new blood will stay at Cisco long, I suspect the smart ones will see how Cisco has behaved in the past and will get in on the next great startup, or create their own. The next tier will follow the leaders that exit. It's pretty much what we would expect from Silicon Valley. I give Cisco a 50/50 chance at this point. Internally, one engineering VP has not said much other than to direct employees to https://www.scribd.com/doc/235309368/Escape-Velocity-Overview/. Is Cisco trying to reinvent itself in the same way as Apple? They have floundered on so many other attempts, their various failures in consumer electronics, video platforms that don't seem to have become a big part of CDN networks, and it seems that VoIP has become stagnate too. "The Internet of Everything" is what thy are publicly talking about, but are there still people at the company with the talent to find a killer app for the idea? Would they want to come forward withing Cisco, or would they be more likely to found their own startup instead?

    24. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      He knows that this will throw the group into chaos, but he also sees a way to grow the revenue of the company by an order of magnitude if we can do some very specific work. Crucially, it doesn't really matter how badly we do it. It just needs to mostly work.

      Do you still interview like you're hiring experienced neurosurgeons who must also be professional ballroom dancers? That was my frustration with the hiring process recently... there are a lot of jobs out there that need someone quick and efficient, not necessarily a master of arcana for whatever trivia your company values, and yet the technical interviewers ask almost entirely facile trivia and fail to probe whether a person can work efficiently the way that they need. I really hope you're not asking the new hires you hope to just crapout-some-crap-ASAP to whiteboard algorithms, and looking for fluency in arcane syntax tor APIs hat can be answered with 30 seconds of searching stackoverflow. I hope you're asking them how they work, and how fast, and how they've handled similar ship-it pressures in the past. How quickly they learn new things and react to change. Etc. the "soft skills" that matter to your engineering organization, because let's face it, this isn't rocket science or brain surgery.

      But no, you probably have them whiteboarding algorithms and worrying about syntax, pretending that what you're doing is actually difficult. Sigh.

    25. Re:Engineers have no future. by Gr8Apes · · Score: 1

      But you also need experts in defining what routines need to be coded and how they are supposed to interact to achieve big picture goals, and you need creative people to define what big picture goals should be and decide which are most worth pursuing. Those people are hard to develop and hard to replace.

      They get even harder to develop and replace when no one wants to invest in the development of such people. They generally don't just pop in fresh from a 4 year program.

      --
      The cesspool just got a check and balance.
    26. Re: Engineers have no future. by davester666 · · Score: 1

      Quote from a tv show?

      --
      Sleep your way to a whiter smile...date a dentist!
    27. Re:Engineers have no future. by myid · · Score: 1

      Just today, I sat in on a lecture that basically said, engineers can expect about 2 years of work and then be put on the chopping block.

      Did the lecturer say anything about jobs that require 5 years experience in order to be hired?

    28. Re: Engineers have no future. by Anonymous Coward · · Score: 0

      Dead wood doesn't grow leaves.

    29. Re:Engineers have no future. by tsotha · · Score: 1

      You don't ask.

    30. Re:Engineers have no future. by Anonymous Coward · · Score: 1

      I'll fill you in on some details. Since I worked (past tense) at Cisco, before they cut me, they had cut about 30% of the people I knew working for them. I was cut about two years ago. Since then, they've cut another 30% or more.

      People aren't leaving Cisco for personal reasons. They are leaving because Cisco is offering them packages to leave, and if you don't take the package, you get to leave without it.

      Considering that this "Cisco" manager seems oblivious to that basic fact, I doubt that anything else he says has any bearing on reality. So there's nothing to see here. Move along.

      In 2009, Cisco cut 2,000 jobs

      In 2011, Cisco cut 16% of it's workforce

      In 2012, Cisco cut 2,000 jobs

      In 2013, Cisco laid off 4,000 jobs

      in 2014, Cisco is cutting 6,000 jobs

      Cisco really doesn't hire anymore. They buy up companies and call the acquired employees "new hires". Then they cut. And cut, and cut.

    31. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      To show the magnitude of missteps. When buying a new company, one typically doesn't lay off the sales people first.

      Then you don't reduce staff in the technical support department.

      Both of these departments are where a company really makes it or not. I'm not a business person by trade, I build the software; however, I've been around the block enough times to know that it's no fun building software that never gets sold. Damaging the connection between you and your customers is just stupid if you intend to sustain a business.

      Cisco doesn't want to sustain their acquisitions, they want to cut them to the bone and maintain pricing while providing minimal service. It's a game of buying a successful company and burning it to the ground as Cisco collects three to five years of checks against products that people think are being backed by "the power of" Cisco. In reality, it's being backed by "the recently laid off power of" Cisco, so you're going to change vendors in five years because they don't have enough staff to make you happy. Sure, they have enough bodies, but all of those bodies are "new", fresh in from the last acquisition (and they have no idea about the product you bought two years ago).

    32. Re:Engineers have no future. by Anonymous Coward · · Score: 0

      with all the tubes plugged

    33. Re:Engineers have no future. by __aaclcg7560 · · Score: 1

      They get even harder to develop and replace when no one wants to invest in the development of such people.

      When I worked at Cisco for nine months on contract, my boss explained to me that he couldn't train me since I'll get certified, leave Cisco and make more money elsewhere. Never mind that a lack of training caused many employees to train themselves, get certified and leave Cisco to make money elsewhere anyway.

    34. Re:Engineers have no future. by __aaclcg7560 · · Score: 1

      I worked for Cisco in 2013. Just so happened that the quarterly renewal of my contract came up during the announced layoff period one year ago this month. My manager wanted to renew my contract but the HR system locked him out from doing that. I was laid off along with 300+ full-time employees from the business unit. My boss lost half of the contractors on his team for that year, forcing more work back on to the full-time employees. A screwy way to run a company.

  3. All the good talent leaves. by Anonymous Coward · · Score: 1

    Anyone who can get another job elsewhere leaves. Anyone who is really good gets head hunted or starts their own business. What are you left with?

    1. Re:All the good talent leaves. by Ol+Olsoc · · Score: 0

      Anyone who can get another job elsewhere leaves. Anyone who is really good gets head hunted or starts their own business. What are you left with?

      You?

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
  4. Might as well be a startup by hawkingradiation · · Score: 1

    So they are down to developing customer centric solutions while leveraging their key synergies. Anything better than riding the corporate wave?

    --
    Society use your Sciences
    1. Re:Might as well be a startup by Anonymous Coward · · Score: 0

      being the CEO/CFO/CTO's idiot child (idealing bearing an MBA)

  5. Karma is by Anonymous Coward · · Score: 0

    When the PHB gets fired^H^H^H^H^H re-organized out and comes looking for a gig at your new company (because you were smart enough to leave when the getting was good), load all torpedo tubes with specific poor behaviors and fire away. So far that has happened for me twice. I am that lucky.

  6. You guys by ADRA · · Score: 4, Interesting

    I may just be interpretting this discussion different than everyone else here, but assuming every developer is happy with company, and company decides to implement a new development philosophy or production model (for strategic / financial / etc..) reasons, wouldn't it be sensible and actually expected that a non-trivial number of developers won't be happy with said changes?

    For example, If my company went from Dev and IT groups to merging them into devops, some people are going to be rocking the idea, and a shit ton may be unhappy about the change and decide to move on. DevOps isn't any more or any less better for an employee, but it means a different set of tasks for that developer to live in. Maybe this change will significantly improve workplace productivity and the change isn't only merited, but essential for the company's survival. Same with, say dropping support for Windows/Linux/Mac/etcc OS's and just supporting a smaller set of OS's. Some would say there are valid reasons to adopt the standard (less IT burdens), and others who use said dropped OS's will be more willing to leave.

    To assume that the company simply doesn't care about its developers walking out is a little bit of an overstatement. Many won't like a change (regardless of what it is), and if you're going to leave, you might as well leave when you perceive a negative change in your job.

    --
    Bye!
    1. Re:You guys by drinkypoo · · Score: 1

      DevOps isn't any more or any less better for an employee, but it means a different set of tasks for that developer to live in.

      Well, here's a statement that's even more better, a different set of tasks will be better or worse (or more better, or less better) for a given employee.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:You guys by Anonymous Coward · · Score: 0

      but assuming every developer is happy with company, and company decides to implement a new development philosophy or production model

      You don't see a problem there?

  7. Personal and business reasons by enriquevagu · · Score: 4, Insightful

    Personal and business reasons are actually opposite. These people are being fired.

    1. Re:Personal and business reasons by Anonymous Coward · · Score: 0

      correct, they are being fired.
      I personally know few of them.

      Some with 10-18 years of experience, suddenly leaving all together on the same week? and not exactly because they are moving to form a new company....

  8. The essence of enterprise by golodh · · Score: 4, Insightful
    I fear that the negative reactions here indicate (once again) that Slashdot readership consists mainly of techies. And such people often have difficulties understanding understanding how society works (even if they tend to have vocal opinions on any subject that comes along). Let me try to bring some perspective into the discussion.

    Lest somebody misunderstand, the very essence of an enterprise (any enterprise) is that it is a bundle of labour and capital whose essential structure and identity is independent of and more persistent than the labour it employs. The identity behind its labour component is no more important than the identity of its capital component.

    It is for this reason that any contemporary HR policy is aimed at (and this is important) divorcing the work from specific individuals.

    What this means is that all and any employees must (and this is essential) be plug-replaceable as a matter of policy. Those that aren't should either be unique individuals like Steve Jobs, Bill Gates, the actual owners of the company, or leaving.

    That is one of the drivers (not the only one of course) behind the desire for standardisation of work procedures and documentation of ideas and knowledge.

    The result of careful execution of such policy is a situation in which personnel really is replaceable. Even when it concerns 10%-30% of the employees. Which is what we are now seeing illustrated at Cisco.

    So there's no need to be surprised. And no need to be disgruntled. It's simply the consequence of a certain feature of our society we collectively decided we want and actively maintain. And it has truly served us well for the past century and a half and its end-result is the envy of our neigbours.

    Unfortunately the current economic tide makes the downsides (for such they are) of this state of affairs more visible: i.e. employees are just another commodity and any successful enterprise will treat them as such. . As a result, employees can get a rough deal (if they get any deal at all, i.e. if they are employed). Let's be clear about this: I don't know how to make those downsides go away without wrecking the competitiveness of enterprises. But I suspect it will involve a realignment in the balance of power between labour and capital.

    One way of achieving this is through the use of force. Also known as "legislation". Fortunately we have a mechanism in place for effecting change. It's called Politics. But what actual policy should be enacted through Politics? If knew (and could prove it) I'd tell you, but I don't.

    One of the problems is the constraints imposed on all of us through competition. I.e. if the policy we adopt is too disadvantagous for enterprises, they will simply take their capital, set up shop elsewhere, and drive the disadvantaged enterprises off the market.

    So it's up for debate really, and this isn't a new debate. It's a debate about a basic balance in our society that needs to be realigned from time to time.

    1. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      You are more deluded than the "techies" that you criticize if you are not aware that NOTHING that is in the interest of normal people can be solved by politics.
      In the whole history of human kind the only way for citizens to achieve something was through revolution (even non-violent ones).
      Another thing you might want to learn about large corporations, is that they are no longer competing like your mom and pop shop that is what people think the private enterprise is. They get handouts from governments, they do all kind of shit not to pay taxes and, more importantly, they don't have to create competitive products. Your shitty start-up cannot compete with Lockheed Martin for a contract with the military.

    2. Re:The essence of enterprise by bkmoore · · Score: 3, Interesting

      ...the very essence of an enterprise (any enterprise) is that it is a bundle of labour and capital whose essential structure and identity is independent of and more persistent than the labour it employs. The identity behind its labour component is no more important than the identity of its capital component...

      Mr. Patel was misquoted in the header, FTA he did not explicitly say "Turnover in Engineering No Problem", but let's assume he did say so in so many words. He is about 33% correct, all engineers are replaceable, and that is the main reason good engineers always document their work. But the question that is often ignored by business school 101-types is how much money and time does it take to replace a competent engineer? Can your enterprise afford the Project disruption and late time-to-market? Will your development still be relevant by the time it finally launches?

      You argue that "capital" and "labor" are essentially equal to the identity of an enterprise. In a lot of enterprises that may be true, where either the labor is totally unskilled (light-bulb turners) and requires no training, or the labor is "certified and trained" and perform a set of narrowly-defined tasks, e.g. truck drivers, shipping, railroad engineers, airline pilots, etc. In product development, this ideal model breaks down. Engineering has no standardised training, and every situation or development situation is a unique learning experience, both for the enterprise and for the labor. That's why we have "project management" and development in the first place. History is full of examples of enterprises that made the mistake of treating their engineers as fungible, interchangeable assets. Products started coming out "a day late and a dollar short". Eventually they reorganised, split, made a splash with some big announcements and then disappeared.

    3. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      What this means is that all and any employees must (and this is essential) be plug-replaceable as a matter of policy.
      Those that aren't should either be unique individuals like Steve Jobs, Bill Gates, the actual owners of the company, or leaving.

      Sure, what do you think happens when you build a company that is relying on those principles?

      What happens is that you end up in the same situation as the manufacturing industry. If your developers are replaceable then all competitors can easily get the same know-how by simply getting the developers.
      The value of a developer is in his or her education and experience. You don't keep that in your company when you replace that worker. Treating them like replaceable goods means that you train them and then hand them over to your competitor. That is a very bad business practice.
      A company with focus on developing can't let the competitor grab the developers cheaply.

    4. Re:The essence of enterprise by rtb61 · · Score: 4, Insightful

      The insane idea that humanity exist to service corporations is, well, insane. Our society exists to service and support us, it has been corrupted by psychopaths to allow them to exploit us to service and support themselves only. The idea that competition is the ideal management solution is a direct measure of that insanity, real fairies at the bottom of the garden stuff. Competition as the solution means failure as a solution. That's was competition versus cooperation is about, competition is about using failure as a normal everyday occurrence and cooperation is about avoiding failure.

      Examples of competition in business. Health insurance where people who paid premiums and when they need them the company fails after feeding huge amount of cash in management pockets now have no coverage. In schools it means failed schools put their students through a year of education for nothing, which now has to be repeated. Hospitals where patients suffer and die until they are shut down. Prison where recidivism is a desirable corporate objective, have to keep those prisoners coming back, until the governments that fund them finally shut them down as failures.

      Competition is not a sound management principle, it is a psychopathic management principle because it is driven by failure. Even winning companies can still be bought out and mismanaged directly into failure, in fact it is historically inevitable.

      --
      Chaos - everything, everywhere, everywhen
    5. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      Funny how your rules never seem to apply to *them*, only to *us*.

    6. Re:The essence of enterprise by drinkypoo · · Score: 3, Insightful

      The identity behind its labour component is no more important than the identity of its capital component.

      Well, let's look at how important the identity of the capital component can be: it can make or break a company. Depending on the identity of known major investors, you can attract or repel other major investors. So clearly you have agreed that the identity behind the labor component is critically important.

      It is for this reason that any contemporary HR policy is aimed at (and this is important) divorcing the work from specific individuals.

      No. The only reason that is the case is because of mindless chasing of the bottom line. In the real world, we know that while individuals can be replaced, no individual is a perfect replacement for another. Even identical twins have their own unique proclivities, and the rest of us are less identical than they except by astounding happenstance which you statistically cannot depend upon.

      The truth is that companies change (and sometimes fail) based on loss of specific talent. You don't tend to see the results instananeously because the failures are gradual and accumulative. Eventually they become too great, and they topple the organization. When you lose specific talent, you lose knowledge you didn't even know you were depending on in most cases, and you lose business-enabling shortcuts in the organizational structure which can take in some cases years to build.

      So it's up for debate really, and this isn't a new debate. It's a debate about a basic balance in our society that needs to be realigned from time to time.

      Well, no. Everyone knows that shitting on employees and causing them to leave (or just firing them when they are necessary) produces inferior results. The actual problem is the chasing of short-term profit. A CEO can do something that they know will harm the company in the long term in order to produce a bump in profits in the short term, and moreover, their interchangeability means that they can do that and get away with it, come out looking like a winner to investors, and then move on and do it to another company. And this in turn is related to the modern idea that a corporation must serve the shareholders' every whim, but this is nonsense. The corporation must serve its charter, and shareholders who don't approve of that charter should invest elsewhere.

      Of course, one way to stop this would be to institute better laws for protection of employees of absorbed corporations. That would make other corps less likely to cannibalize them, since their value in an acquisition falls sharply if you can't simply sack all the employees you don't like in short order.

      A better way to stabilize society might be a COLA/MGI, which would eliminate people's need to go to work for corporations which should be allowed to fail anyway, either because they don't treat workers well or frankly for any other reason. Most corporations shouldn't exist, but in our modern make-work system we must preserve them so as to preserve jobs so as to preserve economic prosperity. Meanwhile, many are stacking up numbers in bank accounts which will remain untapped until their death. You can't take it with you, but you can deprive someone who needs it right now.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:The essence of enterprise by drinkypoo · · Score: 3, Insightful

      Competition is not a sound management principle, it is a psychopathic management principle because it is driven by failure

      Competition from competare, which I am probably misspelling, everyone running together to go faster. Competition is a sound management principle, but only if the penalties for failure do not include incarceration and death. And the risk of that goes way up if you fail in the corporate reality and become homeless. Then you get stigmatized, and society can do anything it likes to you. Ironically, only Utah seems to be figuring out a compassionate solution.

      Competition helps us achieve more and helps us decide on the best solutions. But when you combine it with an artificial scarcity society (which is rapidly leading us down the path to a real one) then it becomes fear-driven, rather than the desire to excel, and fear makes us make poor and short-sighted decisions.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:The essence of enterprise by golodh · · Score: 2

      You argue that "capital" and "labor" are essentially equal to the identity of an enterprise.

      I really didn't: when I said "bundle" I left the relative proportions unspecified. But I agree with you in that the relative importance of people's identity varies sharply with the scarcity of people's skills and that depends on the setting.

      We agree that in a environment where people do routine work, so many people share the required skill that identity of who provides this skill no longer matters. And that's where vast majority of the working population is employed.

      Of course there are settings where individual skills matter to a greater degree. One can think of e.g. professional sportspeople, scientists, lawyers, entrepreneurs, politicians, artists, inventors.

      But their numbers are small compared to "ordinary" workers, so that by and large I think the proposition holds. Yes, there are exceptions, but 99% of the working population is rather un-exceptional.

    9. Re:The essence of enterprise by AmiMoJo · · Score: 1

      Sounds like a good way to ensure mediocrity and low skill levels in your workforce. Successful companies value employees and try to keep them happy and developing, to get the best from them.

      Car analogy: You can get a cheap, generic, replaceable Ford or you can get a high performance model that needs a little more maintenance and care. The Ford isn't going to win any races, but you can drive it into the ground and then dispose of it for an identical replacement any time you like.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    10. Re:The essence of enterprise by Antique+Geekmeister · · Score: 2

      > Let me try to bring some perspective into the discussion. Lest somebody misunderstand, the very essence of an enterprise (any enterprise) is that it is a bundle of labour and capital whose essential structure and identity is independent of and more persistent than the labour it employs. The identity behind its labour component is no more important than the identity of its capital component.

      I'm afraid, sir or madam, that your very opening statements show exactly why engineers will disagree with the entire rest of your statement. You've redefined a common word with a well understood social and legal meaning. Your definition reflects a business school philosophy that does not match either the common or the legal meaning. And it breaks down very, very quickly in the real world.

      > It is for this reason that any contemporary HR policy is aimed at (and this is important) divorcing the work from specific individuals.

      Nonsense. This guarantees failure in the long run for a tech business. It can work for Wal-Mart or even McDonald's or even non-technologically innovative business, such as spam advertising and domain squatting. There are profound evolutionary economic pressures against it for the more interesting or leading edge technologies. Networking tools and hardware, lab instruments, software virtualization, and systems security are examples that require insight and mastery to improve designs and remain effective and profitable..

      > So it's up for debate really, and this isn't a new debate. It's a debate about a basic balance in our society that needs to be realigned from time to time.

      And it's vital to know what the debate is really about. Please do not try to redefine basic terms in ways that obscure the actual debates. It's framing the question in a way that is misleading and helps prevent understanding of the underlying problem.

    11. Re:The essence of enterprise by rtb61 · · Score: 1

      Again you adhere to the fantasy that competition only has winners, the PR=B$ marketing delusion, competition inherently means there must be losers, lots and lots of losers, in fact far more losers than winners and losers as the majority represent a system of continual failure, failure as the majority element of a psychopathic society based upon competition rather than cooperation. So pushing the bullshit of competition with only winners and you never have losers ie repeated failure, just like the standard statistic for failure in small business is 9 out of 10, a 90% failure rate basically in the majority a system based upon failure, hence it's psychopathic insane nature, when applied within a social species meant to be cooperating.

      --
      Chaos - everything, everywhere, everywhen
    12. Re:The essence of enterprise by Ol+Olsoc · · Score: 1

      Lest somebody misunderstand, the very essence of an enterprise (any enterprise) is that it is a bundle of labour and capital whose essential structure and identity is independent of and more persistent than the labour it employs. The identity behind its labour component is no more important than the identity of its capital component. It is for this reason that any contemporary HR policy is aimed at (and this is important) divorcing the work from specific individuals.

      Lest anyone misunderstand, We might as well try to crap gold bricks.

      The problem is that the pluggable employee simply doesn't exist. And it never will for almost any position on the planet above the completely menial.

      Where I worked, we had three employees with the exact same job description as my own, and they all had the appropriate education.

      But through the situation, I had lots of other education due to a longer career. an ability to think fast on my feet, and willingness to do whatever it took to get the job done. The other two performed adequately according to the job description. I could go into my customers, do my job as defined, plus fix their computers, even troubleshoot the electronics they were working on. And I'd stay all night to get any of those done.

      The others performed just fine in their respective fields, but anything I would just step in and fix would take several more people, therefore despite my making a lot more money, a lot of folks were requesting my services rather than my less expensive but fully qualified (in the job description) co workers. Who were not at all pluggable into what I could do

      It was hilarious to watch HR try to quantify my job tasks. They gave up in the end.

      So until all humans have the same outlook, the same abilities, the same career paths, and the same attitude, Plug-in people won't work.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    13. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      Nah. Unless it's completely plagiarized, it's more coherent than you'd expect from a first year MBA student, who hasn't learned the subtle double speak to get board members to buy into the nonsense. I'm guessing that they're the stooge who writes the presentations that get sent to HP stock holders, spinning damage control with the practiced flicking of both wrists that they use to keep their boss thinking that their empire can never crumble because they have the "big picture" because their staff writer agrees with them, ohh baby, yeah, just there, keep those options flowing, you know just how!

    14. Re:The essence of enterprise by tomhath · · Score: 1

      competition inherently means there must be losers, lots and lots of losers

      Competition rewards hard work and innovation. The "losers" learn from the "winners" and everyone ends up better off. In your idealized model of "cooperation" there is no way to know what works best and what is worst: you have nothing to compare against and no motivation to become better.

    15. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      " Of course there are settings where individual skills matter to a greater degree. One can think of e.g. professional sportspeople, scientists, lawyers, entrepreneurs, politicians, artists, inventors.

      But their numbers are small compared to "ordinary" workers, so that by and large I think the proposition holds. Yes, there are exceptions, but 99% of the working population is rather un-exceptional."

      That seems grossly oversimplified. Like most things with humans, it isn't a dichotomy of 'exceptional' and 'ordinary'. Every worker usually has some amount of 'exceptional', and some amount that aligns with what you need them to do, and that amount might be more or less than others performing the same role. And engineering (which is encapsulated by the 'techie' group of Slashdot readers), a field where insight, clarity, work ethic, intelligence, and lateral thinking are major factors of job performance, that 'individual skills' factor matters at least as much as it does with scientists and inventors. Your posts indicate that you might fall into the category of people, as pointed out elsewhere, who don't actually understand what engineers do and instead confuse them with technicians.

      If you are stuck in the mindset that there is 99% cogs and 1% gems, you miss the whole point that given there are some amount of performers that have a skillset/mindset/exceptional abilities that greatly benefit a team or project, even though they might be replaceable, doing so is not trivial. Instead, given the tools of resumes, interviews, degrees, certifications, etc, finding those replacements is nearly impossible, and more likely, one ends up replacing a rough gem with a random factor.

      And even if you do find someone with equivalent technical/mental abilities, there are many other factors (leadership styles, personalities) that could radically change the performance of how the team operates even if that one replacement is functionally equivalent on their own.

      If you were to make a scale of people whose roles are more/less replaceable, probably the top third fall into this category, which is partly why there is so much negative feedback. Engineers actually working on teams see people with mindsets like yours replace people like the ones I described, and then see the projects fail and the teams fall apart for the reasons I gave.

    16. Re:The essence of enterprise by whyAreAllNicksTaken · · Score: 1

      I don't know how to make those downsides go away without wrecking the competitiveness of enterprises. But I suspect it will involve a realignment in the balance of power between labour and capital.

      One way of achieving this is through the use of force. Also known as "legislation". Fortunately we have a mechanism in place for effecting change. It's called Politics. But what actual policy should be enacted through Politics? If knew (and could prove it) I'd tell you, but I don't.

      Good thing our political system doesn't also have a large power imbalance favoring capital!

    17. Re:The essence of enterprise by hambone142 · · Score: 1

      Sounds like the current state of Hewlett Packard.

    18. Re:The essence of enterprise by drinkypoo · · Score: 1

      Again you adhere to the fantasy that competition only has winners

      Nonsense. I adhere to the fantasy that we could be convinced (as a society, species, etc.) to lower the penalty for failure by changing the rules of the game. The truth is that there will always be failure. It's part of attempting to succeed. Some fail, some succeed, some fail and then succeed, some succeed due to learning from the failure of others. That's going to happen. How we handle these situations is up to us.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    19. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      That is all fluffy cotton candy propaganda.

      > and no motivation to become better.

      There are plenty of people in the world that are motivated by ideas/progress/science/etc. for their own sake. If you personally lack motivation and ambition to achieve anything, it doesn't mean the rest of the population does.

    20. Re:The essence of enterprise by TubeSteak · · Score: 1

      We agree that in a environment where people do routine work, so many people share the required skill that identity of who provides this skill no longer matters. And that's where vast majority of the working population is employed.

      You seem to completely ignore the value of institutional knowledge.

      Maybe in your world, everything is documented, but everywhere else, knowledge of certain critical business processes is only retained in the memory of a few employees.

      Slashdot even had a nice conversation about it a few years ago
      http://tech.slashdot.org/story/11/12/04/1742211/institutional-memory-and-reverse-smuggling

      --
      [Fuck Beta]
      o0t!
    21. Re:The essence of enterprise by frank_adrian314159 · · Score: 1

      ... there is no way to know what works best and what is worst: you have nothing to compare against and no motivation to become better.

      You haven't heard of metrics other than dollars?

      --
      That is all.
    22. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      So until all humans have the same outlook, the same abilities, the same career paths, and the same attitude, Plug-in people won't work.

      Very well put. In a way, they can have "plug-in people". But then they have to map skillsets completely in order to produce a true match. And they will discover that skillsets are so complicated, that the vast majority of successful people are truely unique. I guess many of the loosers are too, but a business won't care about those.

    23. Re:The essence of enterprise by ogdenk · · Score: 1

      What this means is that all and any employees must (and this is essential) be plug-replaceable as a matter of policy.
      Those that aren't should either be unique individuals like Steve Jobs, Bill Gates, the actual owners of the company, or leaving.

      Exactly, how else are you supposed to abuse people and crush debate if those people are actually needed and not easy to replace? Engineers are not plug replaceable, never will be and never really have been. Neither are good IT folks. And to suggest someone who's studied their craft their whole life should be "plug replaceable" while some exec whose daddy got him the gig due to family money shouldn't is laughable.

      We are no easier to replace than a good exec. We have had to study just as long for our skillsets and we are tired of being abused and treated like commodity laborers. We aren't. We are white collar professionals and expect to be treated as such. We aren't the type to just shutup and make you money.

    24. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      If you know nothing of the field you are commenting on outside of what you read in Fortune magazine and other useless rags, you need to shut the fuck up before you embarrass yourself.

    25. Re:The essence of enterprise by __aaltlg1547 · · Score: 1

      In my experience, depending on the position, it takes 2 to 6 months to replace a competent engineer. (Incompetents can be replaced in a week.)

      Considering that the AVERAGE engineer's value to the organization necessarily exceeds the cost of employing him, which is something like 150% of salary, that means each engineer you lose (that you didn't intend to lay off), costs 3 to 9 months of an average engineer's salary AT MINIMUM. I'd estimate that the average engineer is worth 3 times his total compensation, so something like 18 months salary is lost with each engineer. If you ballpark the level of the average person lost, it would be an intermediate engineer paid around 77K/yr * 1.5 years salary or about $115K per position.

      But if your intent is to NOT replace the missing people, it's a different equation. You only make this decision after deciding that you don't need so many people because you have more people than you need to do the anticipated work. Then you lay off people until you have the desired number.

    26. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      I fear that the negative reactions here indicate (once again) that Slashdot readership consists mainly of techies. And such people often have difficulties understanding understanding how society works (even if they tend to have vocal opinions on any subject that comes along). Let me try to bring some perspective into the discussion.

      Even being a lowly techie who has no idea how anything works but a computer (fuck even a monkey could use a computer amiright?), I'm at least able to comprehend that you're being a condescending ass.

      Hell, you probably think you're a people person.

    27. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      You can make people plug-replacable as a matter of policy, but that doesn't mean you'll be able to do so as a matter of reality. In commodity fields? Probably can do it to a close enough approximation not to matter.

      However, the group I work for does some very specialized, cutting-edge stuff. Even for a good developer with experience in our general field (network security), it takes 6 to 12 months to get a new one ramped up to full productivity. You simply can't sustain development on these kind of specialized products with a high churn rate.

      The biggest problem we're currently having is that we were bought by a Fortune 50 megacorp a couple years ago. Their commodity sytled management has driven away a significant chunk of the top performers, and will probably finish driving off the experienced employees next year.

      Once that happens, the product will effectively be dead except for the name. Which, sadly, is all they need to continue making money, as far as I can tell. We've looked at competitor's produts, and some of them are pure snake-oil. It's hard for non-experts to test this stuff correctly (and the biggest name third-party test house is nothing but an extortion racket), so few buyers are actually judging on quality.

      And, yes, Cisco is one of the ones in this space, and their product verges on the Snake Oil end of the scale. Seeing this VP's comments, I'm not surprised.

    28. Re:The essence of enterprise by __aaltlg1547 · · Score: 2

      Competition in the workplace disincentivizes teamwork. Watch any one of those competive "reality" shows some time where all the prize money goes to one winner and see what competition does to people's behavior. They cooperate only insofar as it helps them toward winning and then turn on each other at the first opportunity. They'll work together to eliminate a person they think might beat them in the competition.

      You do not want that behavior in the workplace. You want cooperation toward team objectives, and that's what you should reward, and you should discourage behavior that promotes individual success at the expense of team goals, if necessary firing individuals that don't cooperate, even if they are better than average individual performers.

      Competition is a valid inter-business strategy where you are trying to win business among a group of businesses in the same market. Or it can be employed within a business between teams but only if there is no possibility of their influencing the other team's success, because you should want both teams to succeed.

    29. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      Dell Secureworks.

    30. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      It is for this reason that any contemporary HR policy is aimed at (and this is important) divorcing the work from specific individuals.

      What this means is that all and any employees must (and this is essential) be plug-replaceable as a matter of policy.
      Those that aren't should either be unique individuals like Steve Jobs, Bill Gates, the actual owners of the company, or leaving.

      That is one of the drivers (not the only one of course) behind the desire for standardisation of work procedures and documentation of ideas and knowledge.

      And right now I'm working on fixing a very expensive mess at an aerospace subcontractor that has exactly this type of policy. (posting anon to protect the guilty)

      You can't do small quantity, high quality, custom engineering with a policy that treats engineers and technicians as interchangeable parts who just have to follow the process. Somebody has to have the deep understanding to develop and refine the process, and find the stuff that didn't get written down because nobody thought it was special. If you only sell one of a $100M widget every 5 years or so, and each one is customized to a particular application, you need the people who understand the very subtle details of the widget to stick around. You can try to reduce it to a bunch of documented processes, but the first generation of replacement people will struggle to make a new customized copy of the widget, and the second generation will likely just plain fail.

      Essentially, if you treat your technical staff as completely interchangeable and replaceable, you'll be limited to making commodity items that any other company can make just as well (because your staff are rotating among you and your competitors) and you'll get caught in a race to the bottom on selling products that are indistinguishable from your competitors. And your staff will have little investment in making your company do well.

      Keep a bunch of specialists with deep knowledge around and you can make things of much higher quality and originality. It's critical to make sure there are succession plans, so that you get younger specialists to absorb what the older ones know before they retire/die/finally get recruited away.

    31. Re:The essence of enterprise by bitingduck · · Score: 3, Insightful

      That seems grossly oversimplified. Like most things with humans, it isn't a dichotomy of 'exceptional' and 'ordinary'. Every worker usually has some amount of 'exceptional', and some amount that aligns with what you need them to do, and that amount might be more or less than others performing the same role. And engineering (which is encapsulated by the 'techie' group of Slashdot readers), a field where insight, clarity, work ethic, intelligence, and lateral thinking are major factors of job performance, that 'individual skills' factor matters at least as much as it does with scientists and inventors. Your posts indicate that you might fall into the category of people, as pointed out elsewhere, who don't actually understand what engineers do and instead confuse them with technicians.

      Overall an excellent post-- too bad you posted anon so fewer will see it (I don't have mod points).

      To expand on the quoted section-- good management of technical people is finding the areas where people are exceptional and putting them into positions where you can best use those skills, and avoiding forcing them into areas where they aren't particularly special or interested interested in becoming so (which will make them unexceptional).

      I should also point out that there's a very fuzzy line between "engineer", "scientist", and "inventor" (which you sort of imply, but I'll come out and say it). A very substantial part of many science fields is engineering to make the observation that you're trying to make. And anybody can "invent" something that they need, but it usually takes a bunch of engineering to implement it, much of which gets done by the inventor. Even on a small scale, a significant fraction of engineers have to "invent" things on a small scale on a regular basis.

    32. Re:The essence of enterprise by bitingduck · · Score: 1

      Competition rewards hard work and innovation. The "losers" learn from the "winners" and everyone ends up better off. In your idealized model of "cooperation" there is no way to know what works best and what is worst: you have nothing to compare against and no motivation to become better.

      It also rewards lying, cheating, and fraud, which have all increased in science as the competitive pressure (for positions and funding) to publish large volumes of high-impact research in short times has increased.

    33. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      The problems with both approaches is that once you've cut a department by 40%, the remaining engineers are not replaceable; because, there is no extra manpower to train the new ones to replace the old. However, even that is a moot point, as Cisco isn't replacing anyone in a department.

      They're standing up new departments and groups consisting of entirely new people recently acquired from their last business purchase. As such, the understaffed departments are still suffering (just like they always did), and they get cut more and more heavily until they disappear.

      So neither of your theories are the most important divers in what's happening at Cisco today. If you want to know about Cisco, look up "corporate raiders" and realize that Cisco's doing that, but is absorbing the company into it's offerings before it tears it apart.

    34. Re:The essence of enterprise by aralin · · Score: 1

      Whatsapp hired 14 engineers to make the company worth $19B. They were not 14 completely replaceable, run of the mill engineers, they were each unique and probably irreplaceable. The quality of those employees at that concentration, the fact they could be a small agile group, that was the reason they created so much value. If you want to create small predictable progress and run an enterprise with steady churn of cash, you might go the Cisco way, but you will never produce anything great or even just above average.

      --
      If programs would be read like poetry, most programmers would be Vogons.
    35. Re:The essence of enterprise by rtb61 · · Score: 2

      You are just repeating the same stupidity over and over again, as if that idiot right ideology actually means something. Competition just creates failure in the majority, the winners keep their secrets but it does not matter, inevitably as history has proven they 'ALL' in turn fail, so instead of cooperation you have repeated endless failure.

      OHH AHH 'idealised' cooperation, how moronic can you be, without 'idealised' cooperation we would be naked animals screaming in the darkness, which is exactly what you end up with a population of psychopaths, dog eat dog competition, or more accurately rabid dog eat rabid dog because smart dogs actually managed 'idealised' cooperation.

      What way works best, hmm, established measurement metrics the report productivity, safety, resource usage and pollution minimisation. Then simply model and simulate new methods that smart people come up and where they show promise try them out in limited trials and where success is indicated apply them across the wider market. Not idiot psychopaths who have no idea other than 'mwah haha' lets have competition and management by failure where management can take credit for the successes and blame everyone else for the by far majority repeated failures, because in reality psychopathic management has no idea what they are doing, which is basically the current model for corporate management.

      One could just imagine how you would apply you stupid competition model in pharmaceutical applications. Just administer all and every substance in the population and them when people survive and you cure the problem you have a winner, as for the loses 'er' 'um' the ones that survive can learn from the winners.

      Competition is management by failure because that is the majority outcome and success is the minority 'temporary' outcome because success inevitably also leads to failure.

      --
      Chaos - everything, everywhere, everywhen
    36. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      One might relate bonuses to long term profit. E.g. you get a bonus but you get 1/5 part every year, only in years when there is a profit. You may even embed this in the law.

    37. Re:The essence of enterprise by Anonymous Coward · · Score: 0

      I always use the Ford/Ferrari analogy to explain why people with high iq have learning troubles. The real question is: Should you mix Fords and Ferrari's too much in a company?

    38. Re:The essence of enterprise by drinkypoo · · Score: 1

      Or it can be employed within a business between teams but only if there is no possibility of their influencing the other team's success, because you should want both teams to succeed.

      What I want in this hypothetical scenario is to have the best possible product, and if there are two competing means of achieving the goal I might well choose to explore both of them. And the two ideas are competing, so no matter how much pretty language you dress the idea up in, the two teams will be competing. The important thing is to not see a lack of selection as failure, but as an exploration of an idea which didn't pan out but about which you now have more information. Either you'll have an idea of a scenario where it does make sense, or you'll know why it doesn't make sense and you won't waste time exploring it more completely — perhaps in a finished product which would suffer for it.

      Or, maybe it wouldn't make sense to divide your resources like that. It'll depend on your situation. But that's a better use of employees you'll need again one day than firing them and hoping you'll be able to replace them with another unit.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    39. Re:The essence of enterprise by romons · · Score: 1

      Lest somebody misunderstand, the very essence of an enterprise (any enterprise) is that it is a bundle of labour and capital whose essential structure and identity is independent of and more persistent than the labour it employs. The identity behind its labour component is no more important than the identity of its capital component.

      Sigh. This is obviously false. The essence of any enterprise is the information that it encodes, its "DNA". The capital is like the energy that runs the organism. The labor is analogous to the cells, taking the information, and encoding it into products that are exchanged with the environment, and which allow the enterprise to function.

      However, in high tech, the information is somewhat more difficult to encode than in, say, civil engineering, where everything they do is easily codified, and there is a long historical context to draw upon. Software and hardware practice is just not that mature yet. So, the information that is used by the enterprise is, for the most part, encoded within the behaviors and practices of the employees.

      So, this makes the view that an enterprise is simply labor + capital both incorrect and harmful. By flushing employees, the enterprise is flushing its DNA. If enough of the corporate DNA is lost, the enterprise flounders, failing to build whatever keeps it alive, despite more and more urgent injections of both capital and labor. Eventually, it dies.

      --
      Go to Heaven for the climate, Hell for the company -- Mark Twain
    40. Re:The essence of enterprise by romons · · Score: 1

      Evolution is driven by competition. Evolution works in making life take advantage of every possible bit of resource in the world. Sadly, evolution also forces the losers to die out.

      Cooperation is like the activity of an individual body. Cells cooperate with one another, because they all are on board with the program, they understand their place in it, and have an interest in making things work for everyone. It is easy to see that competition within a body is a body dying of cancer.

      Is society a body, or is it a bunch of individuals, competing with each other? It is a bit of both, I think. In fact, the fact that we can both compete and cooperate may be what makes us human.

      --
      Go to Heaven for the climate, Hell for the company -- Mark Twain
    41. Re:The essence of enterprise by rtb61 · · Score: 1

      You do understand the difference between the evolution of a social species versus a species that survives alone. As a social species we evolve 'togethor' and go extinct 'togethor', it is psychopathic to 'write' down that we in any way do it alone. Psychopaths and narcissists only see themselves, it is the nature of their genetic defect, it is normal to see and fully appreciate we do it all together, just as I write and others read.

      --
      Chaos - everything, everywhere, everywhen
  9. Gotta make room . . . for those H1-Bs coming! by Anonymous Coward · · Score: 0

    Because at Cisco outsourcing is just another word for nothing left to lose. Cheap, poorly trained labor is low cost labor. If only they could do it the open source way: NO COST LABOR!

  10. high turnover is not limited to tech by Anonymous Coward · · Score: 0

    it is not uncommon for employers to purposefully keep their turnover high so most workers are are the bottom of their wage scale.

    in tech, it is no different.. new employees, even with years and years of experience, will typically earn less than employees in the same job but with that many years of experience at that same employer... plus, of course for tech industry, h1b's aren't permanent, so expect turnover there, too.

    1. Re:high turnover is not limited to tech by Anonymous Coward · · Score: 0

      At my job, they hate high turn over. Employees have a negative value for the first year on average. By the second year, you're finally making the company a decent profit. A highly technical job that involves understand many systems, their interactions, their designs, and integrating them into customer's systems, while acting as a consultant for the customer, and being able to create custom systems for the customers, extremely quickly.

      The engineering department is used to 6month-12month projects, we *need* projects production ready in weeks or we lose multimillion dollar contracts. And the contracts also have very strict SLAs. We have quality, speed, and feature expandable as requirements. Not to mention future features need to be added to the system, live.

      Don't get me started on feature creep. "We want this feature and we need it in 3 days". Best get coding. Actually, you learn to anticipate customers and you learn to ask good questions during the design phase. If you designed the system well, the design does not change even as god knows how many new features are added.

      You don't just replace people.

    2. Re:high turnover is not limited to tech by __aaclcg7560 · · Score: 1

      new employees, even with years and years of experience, will typically earn less than employees in the same job but with that many years of experience at that same employer

      As a contractor, I found that to be the opposite. I ran into an old coworker while interviewing for a job during the summer. We compared notes. He still has the same job at the same company and making the same amount of money that I did from nine years ago. Since tech companies have an annoying habit of letting me got every so often, I held multiple contract jobs and made 80% more money than he did.

      If you stay at the same company for a long period of time, you're accepting less than 5% raises every year. If you want to make more money, you need to change jobs from time to time. As much as I would love a long-term job (my recent contracts have averaged nine months in duration), I don't want to miss out on making more money.

  11. It's interesting what Cisco is becoming. by tlambert · · Score: 4, Informative

    It's interesting what Cisco is becoming.

    A decade, even half a decade, ago, Cisco was greatly admired for their ability to acquire without attrition. When a company acquired another company, you usually saw 10-12% attrition in the first 6 months, after the pay-for-stay for key personnel expired, and another 8-10% at the end of 12 months. That meant that between 18% and 22% of what you just bought had walked out your door in your first year.

    Cisco's numbers were 2% and 5% for 6 and 12 months, respectively. Cisco knew how to do an "acquihire", and keep the talent that it bought the company for, and in acquisitions which weren't simply talent plays, it knew how to do that too.

    It seems that this expertise has been lost along the way, or that in one of these annual "transformations", something broke. Either way, with the way they are acting like IBM Global Services these days, or perhaps the post acquisition EDA or post-divestiture Agilent, they are unlikely to be able to repeat their past successes in acquisition, since the trust has been lost.

    Which is really a shame, since they were the envy of the entire tech industry for their capability in this regard, not just Silicon Valley. We used to have meetings at IBM about how we could possibly do what they did, with the numbers they got, and thus avoid killing the goose that laid the golden egg. Similar meeting took place at Apple, particularly prior to the acquisition of P.A. Semi (and much of the team deserted Apple for places like Google anyway, after the lockout handcuffs were removed so that the people who were there prior to the acquisition could cash out and skedaddle.

    It's interesting what they are becoming, because it's not the old Cisco; it most resembles, if I had to pick a company and an era, the post Carly Fiorina H.P.; here's hoping it doesn't turn out the same for them, and that they can correct their course before the rudder falls off entirely.

    1. Re:It's interesting what Cisco is becoming. by Anonymous+Brave+Guy · · Score: 1

      It's not as if Cisco's acquisitions have always been completely independent, though -- look at their connections to Insieme Networks for example -- so I'm not sure you're really comparing apples to apples with those figures.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    2. Re:It's interesting what Cisco is becoming. by Anonymous Coward · · Score: 0

      It's interesting what they are becoming, because it's not the old Cisco; it most resembles, if I had to pick a company and an era, the post Carly Fiorina H.P.; here's hoping it doesn't turn out the same for them, and that they can correct their course before the rudder falls off entirely.

      You hit the nail on the head. I work there and have been working there for a long time (more than 14 years), except for a 4 year stint outside working for a couple of startups, one which was acquired. I came back to Cisco via an acquisition almost 10 years ago and stayed back. I've worked both roles a senior engineering manager and as an Engineer, and I always thought Cisco had a leg up on competitors because of their strong engineering focus in product development (many will disagree with me, but, I know that it is true).

      With the re-orgs becoming an annual feature, my worst fear is it might turn out to be another HP :-(

    3. Re:It's interesting what Cisco is becoming. by Anonymous Coward · · Score: 0

      Well, I don't know how they were, I only know what they are now (or were a couple of years ago, actually).

      We were doing well, making between 30 million per year with a crew of about 80 employees. We were growing like a weed, and in three more years might have been making 60 million per year with about 120 employees.

      Cisco laid off our sales, then cut our technical support. Then they never replaced anyone in QA, leaving the company engineer heavy, disconnected from our customers, and having challenges keeping the ones we had happy. But hey, we still had most of the start-up crew and they did what they did best. Engineers flew out to customer sites to do the support-sales-engineer bit (hard to find ones that can do it all, but we had a few). Support calls would sometimes ring straight through to developer's desks. That an a thousand other things (devs doing analyst roles by surveying customer attitudes during support calls, etc). In short, it was a madhouse, but it worked.

      We managed to go from 30 million per year to 36 million per year with a reduction in staff of 20%. Our ex-CEO got sacked. The new guy came in and told us "You're obviously too talented to be doing what you are doing. We need to free you up for other things", without mentioning other needed tasks. We had enough business background to read between the lines, so the bravest one (not me) asked "What are you planning to do with this division over the next two years". The response was "I don't know. Maybe I'll ship the development to India. Indian developers are very cheap these days, but they're getting more expensive. Personally I'd like to send it all to China, as it's easier for me to drive in China".

      To this day, I think he was unaware that he wasn't talking to a group of business people, he was talking to the entire remaining development and QA team. Still, I find my optimistic view of what happened to be somewhat unrealistic; as, he had given and received appropriate development team related information only thirty minutes prior.

      For his trouble, he's now reaping the rewards in another company. Probably landed the job by showing how he could "motivate" our team into making profits, which really meant cutting the 80% that were remaining down to 60% of the original group. Today I still talk to the team occasionally, but not too much. It's too desperate and bleak. They're down to 30% of the team, and when they're getting cut, people are reacting with joy and happiness (and are none too quick to look for their next job). It's burnout. I'm glad I was cut when I was, but looking back at it now, I only wish I was cut sooner.

    4. Re:It's interesting what Cisco is becoming. by romons · · Score: 1

      What a sad story. My friends at cisco talk about having to do more with less. People get layed off, but the work they did still needs to get done. So, more hours, more frantic checkins, less QA. In short, a dreadful mess. My last year there, I was required to be on call (unpaid) during a mandatory company wide 'furlough' over the Christmas holiday. They used to give us a paid week of holiday over Christmas/Newyears. At the end, I was, in effect, forced to give them a paid holiday instead.

      I'm also glad I got out when I did. Early retirement! The other older folks who didn't take it were fired 3 months later. I'm surprised that anybody but H1Bs are still working there. In fact, all my remaining cisco friends ARE H1Bs. Sigh...

      --
      Go to Heaven for the climate, Hell for the company -- Mark Twain
  12. Cisco is completely dysfunctional by Anonymous Coward · · Score: 3, Interesting

    My company is "partnered" with Cisco to develop networking equipment for smart infrastructure. Working with them is impossible, and they are completely dysfunctional as an organization. The result is that their product is total shit and doesn't work, and their attitude is that it's our job to make our product work with it, despite the fact that their stuff does not comply with published networking standards.

    They've been riding on their brand's coat tails for far too long... Hopefully a Ubiquiti or someone like them will step up and fill the hole that Cisco is digging itself into.

    1. Re:Cisco is completely dysfunctional by romons · · Score: 1

      My company is "partnered" with Cisco to develop networking equipment for smart infrastructure. Working with them is impossible, and they are completely dysfunctional as an organization. The result is that their product is total shit and doesn't work, and their attitude is that it's our job to make our product work with it, despite the fact that their stuff does not comply with published networking standards.

      They've been riding on their brand's coat tails for far too long... Hopefully a Ubiquiti or someone like them will step up and fill the hole that Cisco is digging itself into.

      I hate this. Cisco used to be the innovators in the networking space. Now, they are stuck in the mud. Like IBM in the 90s.

      --
      Go to Heaven for the climate, Hell for the company -- Mark Twain
  13. My company by Anonymous Coward · · Score: 1

    I started my company about 20 years ago on a simple principle. Only hire people that are worth keeping, and keep them.

    I have never had anyone resign, and I have never laid anyone off - in 20 years.

    1. Re:My company by Antique+Geekmeister · · Score: 1

      Goodness, are you hiring? I'm doing a lot of partnership consulting with environments that have good people that have been trying to fix things for years. We respect them profoundly for their input and do our best to make sure they get full credit. But there is sometimes political infighting to get the work done and they wind up as sacrificial lambs. I'd love to send some your way: I wish _I_ could hire them, but my team is pretty well staffed and we often have non-poaching agreements.

    2. Re:My company by Anonymous Coward · · Score: 0

      Yeah, but 20 years? Sooner or later you'll sell the company. And the decline will be so fast employees (well, former employees after the new management gets through) will get whiplash.

    3. Re:My company by Anonymous Coward · · Score: 0

      At my employer, we have sub 1% turn over. The median time employed is over 10 years. The average age is in the 35-45 years old range. A lot of our upper management are ex-political people who took hefty wage cuts to work with us, but they do so because they like our company. We had a CEO that was extremely successful and was used to $10m+/year incomes, but was our CEO for a lowly $200k/year. He did an excellent job, about 30% yearly growth, nearly non-existent customer turn over. Many people like him work at our place, just not as high of a wage. People used to $500k/year, working in the $100k ranges.

  14. that's not a big deal by Anonymous Coward · · Score: 0

    As a programmer, my goal is to make sure I am replaceable with good code documentation and written documentation. I get bored easily, so I don't want to work on something forever. If I don't design the code correctly and implement it properly with documentation, others will have a hard time picking it up. In practice, I find that ends up being a huge benefit for me. I get to do new things and people taking over my code have generally been positive. Several former co-workers even praised my work to my former bosses and heard about it a year later.
    so turn over is a natural thing.

  15. Cisco is just like the rest of them by gelfling · · Score: 3, Interesting

    They announced several thousand job cuts at the same time that every job board today lists hundreds and hundreds of 'openings' but when you apply for them you get a response that the job doesn't exist. And tomorrow is the same thing, and so on. Cisco is a half-tarded company like all the rest that doesn't know from one minute to the next what it's doing and none of the stove pipe orgs know what the other stove pipes are up to. Long story short they're going to appease institutional investors by massively cutting the US workforce and moving it to Asia. Quality will suffer and no one will care. Any day now Cisco will turn into IBM which is little more than an investment fund that buys and sells other companies.

    1. Re:Cisco is just like the rest of them by Antique+Geekmeister · · Score: 1

      >but when you apply for them you get a response that the job doesn't exist

      Oh, dear. This is a quite old trick. It's even more fascinating when they say "we already have candidates", but when your colleague with a different age, gender, or citizenship applies with similar credentials at the same time their application is accepted for review. The classic example of this is tuning HR requirements to only hire H1B candidates, as shown at:

                                  https://www.youtube.com/watch?...

    2. Re:Cisco is just like the rest of them by BarbaraHudson · · Score: 1

      There's also the practice of "resume collecting". HR knows they don't need any new bodies, but to justify THEIR jobs, they spend part of their time in the make-work process of keeping a pool of raw talent available. It's even worse for recruiting firms, who collect them so that they can brag to potential customers of how many workers they have access to.

      And of course if there's a real job being offered, either by a company or another recruiting firm, many of the other recruiting firms will basically clone the offer, just because "if company A is looking for this, we'd better have a few candidates already at hand and ask companies B, C, and D if they're looking for similar talent."

      The end result is that you have a plethora of ads all looking for someone for a job that, in most cases, doesn't exist.

      Even worse, people will think that "oh, THIS is need-to-know technology", because all of a sudden you have 50 ads looking for a VB6 programmer.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  16. Folks this is what happens with bad leadership by Virtucon · · Score: 4, Interesting

    Cisco was an innovative company that created huge market value. Now they're becoming "lean, agile" company with no real vision or future. They want to be "market focused" yet they're supposed to push the market to their view of technology and to create markets. When you lead from behind you certainly take on less risk but you sure don't create the profit margins and patent portfolio investors look for. Sell your shares now.

    --
    Harrison's Postulate - "For every action there is an equal and opposite criticism"
    1. Re:Folks this is what happens with bad leadership by AmiMoJo · · Score: 1

      They were suffering from price competition, and then Snowden exposed the NSA bugging their hardware. Now they are floundering.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    2. Re:Folks this is what happens with bad leadership by Virtucon · · Score: 2

      They've been floundering for years. They've gone through reorg after reorg. Their margins were eroded by other companies who came up with more competitive products. Their certifications are practically useless in all but the most die-hard Cisco shop and those are starting to go away as well.

      --
      Harrison's Postulate - "For every action there is an equal and opposite criticism"
    3. Re:Folks this is what happens with bad leadership by gtall · · Score: 1

      Snowden had nothing to do with it. You could Cisco was circling the toilet bowl years ago when their idea of innovation was to buy other companies and attempt to pound whatever they bought into whatever they had.

    4. Re:Folks this is what happens with bad leadership by Antique+Geekmeister · · Score: 1

      > They were suffering from price competition

      Not just price competition: they were also suffering profoundly from fraudulent Cisco hardware.

                http://www.crn.com/news/networ...

      Not only does it cost Cisco profits to lose the legitimate sale, but it costs them profoundly in customer support for the purchasers of fraudulent Cisco hardware. And Cisco support is a very large business cost to Cisco.

    5. Re:Folks this is what happens with bad leadership by Anonymous Coward · · Score: 0

      I would argue they do have vision, and that vision is of network hardware becoming a commodity. There is a reason IBM doesn't build PCs anymore.

      So, while they may not be doing a 'great job', the alternative is to do nothing and die.

    6. Re:Folks this is what happens with bad leadership by TheGratefulNet · · Score: 1

      all datacomm companies are in bed with the spooks. cisco is just like all the others, not special in that regard.

      I joined cisco in the early days, back in the early 90's. I was there a short time, then left, and recently came back; so I see the new cisco and do remember the old 3 building cisco. they are not even close to the same company anymore.

      I enjoy being there but its more about my group than the company. company wise, I see a lot of bad designs and bad decisions and a lot of young kids who have no business writing or supporting routing software. but like all other valley companies, most work is farmed out to india to the lowest price bidder and the results really show this ;( even locally, you won't find many americans working there and the attention to detail has been long gone. its a young employees company and experience is not really valued, again, like most other bay area companies.

      there is a lot of cool stuff going on, but they have lost their ability to stay focused and deliver world-class software like they once did. its now a body shop with very few visionaries left. sad to see that happen.

      --

      --
      "It is now safe to switch off your computer."
  17. NSA opportunity by Anonymous Coward · · Score: 0

    Is this possibly another great opportunity for the NSA to get their filthy little beggars in the door?
    What new backdoor electronics will we see from CISCO in the future?

  18. Move on, it's another junk management by Anonymous Coward · · Score: 0

    Giving a message that the company will streamline "development and delivery" is such an empty statement that none of the employees would ever find it inspiring. It would rather attract clueless engineers.
    This is not an vision, it is mere b-s. The real vision would be actually some really good idea on the networking itself. And what they say, that they will try to make it even they have been failing recently with that.
    So why they would suddenly reorg and start delivering results?
    Such change takes very long years of developing real culture and environment. if anyone believes that radical changes could help in engineering, is just plain incompetent.
    With such a wrong start, one could expect only situation getting worse and one faux-pass after another.

  19. HR idealism vs. the real world by Anonymous+Brave+Guy · · Score: 1

    Lest somebody misunderstand, the very essence of an enterprise (any enterprise) is that it is a bundle of labour and capital whose essential structure and identity is independent of and more persistent than the labour it employs.

    That's a horrible oversimplification, but let's take it as read for the purposes of this discussion.

    It is for this reason that any contemporary HR policy is aimed at (and this is important) divorcing the work from specific individuals.
    What this means is that all and any employees must (and this is essential) be plug-replaceable as a matter of policy.

    Unfortunately, if you adopt that policy, you have immediately and severely restricted your ability both to hire and retain the most effective staff and to build the most productive teams.

    It is obvious that HR would love for employees to be plug-replaceable in such a way, and it is obvious why. However, the reality is that in a creative industry, and particularly in one related to technology, no two employees offer exactly the same potential contributions. If as a matter of policy you won't hire or depend on anyone with unique contributions to offer, then almost by definition you're only going to have staff with typical combinations of widely available skills and no special experience or unique insights to draw upon.

    However, given that the creative component of technology companies is often where much of their value comes from, a business that can't or won't hire the most creative people is always at risk of a competitor disrupting their business model with a new product, service, distribution model...

    Moreover, technology can be a dramatic effectiveness multiplier. A single smart, creative person using the best technologies can sometimes outperform an entire team of mediocre people with average technologies. More importantly, in scalable fields like software and on-line services, a relatively small team of smart, creative people with complementary skill sets and the best technologies has the potential compete with a much larger organisation on raw effectiveness, before you even consider the overheads that the larger organisation must bear.

    Finally, one of the major factors in maintaining productivity and developing existing technological assets and IP is keeping sufficient knowledge and expertise available within the development team. That can be done through good documentation, tools, processes and so on, but in reality this very rarely happens and word-of-mouth advice is a far more efficient and effective way to pass information around. Of course, if you treat everyone as replaceable you not only forego that most efficient mechanism but also incur the very substantial overheads of trying to use other documentation and tools to compensate. In short, high turnover is an efficiency killer in technical teams where shared knowledge is a vital asset.

    If you think all of this is nonsense, you might consider that this is a discussion about Cisco, whose main business model is currently facing an existential threat from modern technologies like SDN. I'm guessing you're a business studies or MBA student, so you might like to consider the commercial relationships between Cisco and the likes of Amazon, Facebook and Google as a case study for what can happen. Cisco's recurring model of spinning out and later buying up side companies to do the R&D for innovative technologies would also make an interesting case study.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  20. DRINKING GAME by Anonymous Coward · · Score: 0

    Take a drink every time you see a parenthesis.

  21. Large project = regression to mean by Anonymous Coward · · Score: 0

    in any sufficiently large company, doing sufficiently large projects, you have to move towards "interchangeable" workers. If it's just you, Mr. Angelo, carving David out of a big block of marble with a couple devoted helpers, sure. But if you're building the pyramid of Khufu, you need thousands and thousands of "rock draggers" and "rock carvers". Even though the average creativity and productivity of that mass of humanity is much lower than Michaelangelo, it still gets the job done.

    This is what big management is all about. And it's the difference between pre-industrial and post-industrial societies.

    You cannot do a big project by relying on a few stars.. much better to plan for average, and lots of them.

  22. Remember when? by Anonymous Coward · · Score: 0

    Remember when Cisco was the largest corporation in the work, as measured by market cap?

  23. Econ 101: Increasing productivity by Anonymous Coward · · Score: 0

    Small companies create jobs. Big companies destroy jobs.

    Big companies improve productivity by laying off 10% of the work force each year.

    Then, to stay a big company, they have to buy more small companies.

  24. Econ 101: Increasing productivity by Anonymous Coward · · Score: 0

    Ah yes, stupid "business metrics". I met this manager who was evaulated on "metrics". An important one was "profits divided by capital". He boosted that one by buying home PCs for his employees. This little for the profits - except that some might do some work at home. But it cut down the capital, so his "metric" got better.

    I pointed out that he could maximize that metric, and keep it up too, by giving away half of the capital every year. Obviously, his department would shrink and profits would plummet - but the profit drop would alway come after a big giveaway, so his "metric" would still be stellar. And give him a promotion after a few years.

  25. Cisco just "Jumped the shark" by Anonymous Coward · · Score: 1

    Wow. Totally reminiscent of Digital in the late 1990s (and I did work for both Digital and Cisco).
    The important thing is not to innovate, but to focus on V.next switches.
    Cisco NEVER had any serious focus/commitment on security (I know - i worked for Okena, which was bought by Cisco, and then slowly killed over a couple of years). The corporate focus @ Cisco boils down to: If it isnt a bigger/faster router, it isn't interesting/relevant.
    Wall St. already knows that Cisco is stagnant; this confession by Cisco execs overwhelmingly supports their lack of interest in much of anything except their own salaries.

  26. Chambers needs to go. by thermowax · · Score: 1

    I've been working with Cisco gear since 1992 or so, and I've seen a continuous drive to crap. Once rock solid products are now feature- and bug- bloated, impregnable silos exist between the product lines, support simply sucks on both an account team and TAC level... and every time Chambers puts forth a quarterly report he doesn't seem to have anything good to say. (Mind you, I appreciate honesty, but sometimes as CEO you have to sell the company a little).

    Perhaps if they spent a little more time preventing the attrition of decent people they'd see some benefits.

  27. Waste by JimSadler · · Score: 1

    That type of thinking drives prices up and makes a company suffer in the end. Most people want far greater pay for jobs that are not permanent in nature and they just might drag their feet or not care about a job that will let them go when a project ends. And it gets around that a company doesn't mind laying off workers. Toyota became a major company by making it next to impossible to get laid off by their company. They had a lot of loyal workers as a consequence and became a major company as a result. It also helps if a firm pays more than any other firm in the business. Frankly misuse of notions of economics points to an ignorant and ill willed management and ownership of a company. In the US we have not reached the point of dealing with the reality that capitalism is a losing notion and sort of evil as well. Wake up people and look at what has been happening. The US is the last industrialized, western nation to offer public health care and it is still too limited in scope. Germany offers to provide free college for US students as well as housing and in some cases food as well. The US has a totally out of control prison population and are sort of singular in applying the death sentence to anyone. The US now has a lower standard of living than many nations and on top of all of that we have lost the respect of the world by allowing torture of POWs. Are we the new N. Korea?

  28. Streamline product realignment? by lippydude · · Score: 1

    "Streamline product development reorganization byproduct realignment transformation" ..

    In other words mass firings, the savings on the wages bill showing up in next years accounts as increased revenue. Followed by the company imploding in the following year. By which time the CEVPaCDO will have took his bonus and moved on elsewhere.

  29. So Cisco is pursuing the vaporware market? by ibsteve2u · · Score: 1
    That is something of an obvious conclusion given excerpts such as

    Instead of a handful of product managers, engineers and marketers working directly with those SVPs on a customer hardware/software solution, engineers are now split off into separate business units, making product development coordination more cumbersome and perhaps elongating development cycles.

    from articles like NetworkWorld's Cisco reorgs trimming SVP ranks .

    Separating engineering from marketing's' "Yes, we can - and by tomorrow night, too!" is far and away the best primer for a vaporware pump.

    But hey...corporate longevity is as nothing compared to the need to provide current senior executives and large shareholders with maximum returns; somebody else can part out the wreckage.

    --
    Orwell: "In a Time of Universal Deceit, telling the Truth is a Revolutionary Act"