Slashdot Mirror


Should Workplaces Be Re-Defined To Retain Older Tech Workers? (wired.com)

rgh02 submitted this article from Backchannel which argues companies "need to work harder and more persistently to attract, retain, and recognize talent" -- especially older talent: We "elders" know perfectly well that our workplaces are by and large not about us. We don't drive how roles, functions, advancement, and success are seen. Career development options and the hierarchical career ladders everyone is expected to climb are designed for the majority: younger workers. What can be done? There has to be a systems overhaul...
The article suggests restructuring workplaces with "individual contributor tracks" which reward people who don't go on to become managers, as well as things like paid mentoring positions and "phased retirement" programs that create part-time positions to allow a more gradual transition into retirement.

39 of 312 comments (clear)

  1. Re:No by Applehu+Akbar · · Score: 4, Funny

    Older workers should adapt with the times, not vice versa. That's the only way progress will be made.

    AC because I have a feeling the downmod from some pissed off old geyser is coming...

    This is what happens to an old geyser that was famous for years but is now past its prime:
    https://en.wikipedia.org/wiki/...

    His kid Strokkur gets all the attention now.

  2. I've been making this argument for 20 years by bfwebster · · Score: 4, Insightful

    As noted, the problem with most organizations is that there is no technical advancement track. I actually proposed back in the late 90s at one organization that we establish a full technical track that went from entry-level coder all the way up to CTO (with a layer of 'senior technical officers' below the CTO level).

    Other organizations -- such as Bell Labs in its heyday -- simply had everyone as 'Member of Technical Staff', with ad hoc organization around research and technical projects.

    Sadly, though, most organizations do, in fact, force technical people to become managers to advance, regardless of whether they want to or are suited for it. It's one of the reasons IT remains so dysfunctional throughout most organizations.

    --
    Bruce F. Webster (brucefwebster.com)
    1. Re: I've been making this argument for 20 years by Anonymous Coward · · Score: 2, Interesting

      This is why I overwhelmingly prefer to work for companies whose reason for existence is the development of software or hardware. If you work for a bank, there's exactly one track for advancement: management. If you work for a company like Google or AMD, you can advance as a non-management subject-matter expert.

      The HARD part about being a SME is REMAINING a SME. N
      Seven years ago, I was a fairly experienced Android developer, but ended up taking a side-trip into ethical hacking for a couple of years. Eventually, I decided I was happier creating cool new shit than tearing shit apart & destroying it, so I went back into Android development... and got my ass totally *kicked* for almost two years before I felt competent again.

      When I dropped out of Android development, ICS existed... but *depending* on it would have literally eliminated ~94% of existing devices as a market. So I had to get up to speed on things like Fragments. Then there was this "ActionBar" thing, which somehow involved AppCompat-v4. And learning how to use Android Studio instead of Eclipse. Plus, there were lots of things related to threads & IPC that you could get away with in older versions of Android (e.g, using Java's TimerTask instead of Android's AlarmManager, or abusing BroadcastReceivers instead of using Loopers & Handlers).

      And... right around the time I started feeling competent again, Google threw Gradle & Marshmallow at us. Gradle was the worst one, because it single-handedly broke pretty much every older project on GitHub & SourceForge that wasn't being actively maintained (making learning by interactively playing with existing code ENORMOUSLY harder, because Android Studio deprecated non-Gradle projects at a point when its ability to autoconvert old non-Gradle projects was still badly broken). For a formerly-experienced developer still getting back up to speed with modern Android, Gradle was a *major* roadblock. Marshmallow compounded the barriers by making radical changes to the old permissions model... especially if you'd formerly danced around it by just storing everything on /sdcard or /sdcard-ext.

      Meanwhile, elsewhere in the development universe, Java 8 pulled Lambda expressions seemingly out of nowhere (thank sweet black baby JESUS Android didn't support them until I'd gotten back to the point where I'd already gotten back up to speed with Android... being forced to deal with lambdas simultaneously with Android 4 & 5, Android Studio, and Gradle would have probably pushed me over the edge & ended my career in Android development.

      At the web-dev end, I just had to concede defeat & scale back by professed skills to "web services". CSS-1 existed and was used 15 years ago, but CSS 2 & 3 were something that largely existed only on paper... not even Firefox supported more than a meaningless, tiny subset of CSS 2. CSS 3? You're dreaming. Ajax went from something used in exotic, niche apps to something a fucking blog page was expected to use (and IMHO, was generally used excessively & inappropriately... but try telling that to employers who only know "it's the new big thing"). Struts 2 was killed dead by intractable security problems, and Struts 3 got shoved aside by Spring (god HELP anyone trying to newly get into J2EE & Spring NOW... it makes Microsoft MFC circa 2006 look tame & approachable by comparison).

      That said... the changes to PHP were pretty nice. It's a proper OO language now, and MVC doesn't feel like something awkwardly tacked on with staples & duct tape.

      My point is to illustrate just how easy it is to fall off the cart, and go from "expert" (or at least, "tolerably-competent") to "commerciably-unemployable without major, wholesale re-learning" in just a few years... especially in areas (web development, in my case) where you're more marginal to begin with.

      Once you fall off the cart, it's REALLY hard to get back on. When you're a junior programmer, you tend to pick projects that are within

    2. Re:I've been making this argument for 20 years by pauljlucas · · Score: 2

      Bell Labs also had Distinguished Member of Technical Staff.

      --
      If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
  3. Agree in some part by sunking2 · · Score: 5, Insightful

    Most of this is garbage, however the phased retirement is something I've always believed in. I work in at an engineering space orientated firm that has been doing this since pre Apollo days. More often then not people work until the day they retire and 6 months later are back as contractors because they don't know how to do the transition to non working and more importantly the transfer of knowledge didn't happen because nobody wants to pay to have it done. A slower transition both lets people start to enjoy a bit of retirement earlier while they are a year or two younger and allows companies to see where the knowledge is actually lost and adjust.

    the problem with is is your hours worked doesn't really show your salary. It becomes a mess from an insurance and overall compensation perspective to institute such a thing. Things that are hard for HR and financial planny typically don't happen. They don't like things that are hard.

  4. Young people? What young people? by __aaclcg7560 · · Score: 3, Informative

    When Social Security was created in the 1930's, there was 19 workers for every retiree. In 2030, there will be two workers per every retiree. It's going to get really hard to find enough under 30 people to support an aging society. The IT industry alone will have a 1.5M+ shortage of skilled workers as older workers retire and foreign workers go home.

    1. Re:Young people? What young people? by Maxo-Texas · · Score: 2

      Adjusted for inflation, GDP and productivity growth is up just under 1000% from 1930 to 2007.

      We are down to about 2% the number of farmers and they are struggling financially because their productivity is too high (ironically, President Trump killing the TPP is doing huge damage to farmers who suddenly have no place to sell their excess product).

      With trends in automation and robotics, by 2040 we'll literally have too many people compared to jobs.

      So sure.. it took 19 workers to support 1 worker when social security started.

      But it doesn't take that many now.

      This entire social security crisis could have been fixed by a 2% increase in rates and inflation adjust the cap from $106k to $250k back in 2000. It could still be fixed with a little means testing (which they are already doing in a back door way).

      When we have a productivity 50x what we had back in 1900, it means 1 person can support 49 others as well as they supported themselves back then.

      Having fewer workers is a problem but the main problem is a failure of realistic actions by both parties when it would have been much less painful. And plundering funds that could have balanced social security for bridges to nowhere and tanks we parked in the desert indefinitely right after they were built.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    2. Re:Young people? What young people? by WhiplashII · · Score: 2

      Why does no one else see this?

      Personally, I think we should not condone "illegal immigration" because it sweep the issue under the rug, and enables abuse of people designated illegal immigrants.

      We should let everyone in that is not a criminal, and change the laws to make that not be a problem. For example, you can't vote until you are cash flow positive. (Most immigrants would immediately be voters...)

      --
      while (sig==sig) sig=!sig;
    3. Re:Young people? What young people? by Lordpidey · · Score: 2, Insightful

      It's going to get really hard to find enough under 30

      Bullshit.

      What's gonna be hard is to find people under 30 without the 50 required years of experience for an entry level position.

      --
      Some people encrypt by using rot-13 twice. I prefer the more secure method of using rot-1 a total of twenty six times.
    4. Re:Young people? What young people? by ShanghaiBill · · Score: 2

      When Social Security was created in the 1930's, there was 19 workers for every retiree.

      ... and the amount paid to those retirees was ZERO. SS was not available to existing retirees. Only to new retirees that had paid into the system when they were still working. Plus you had to pay in for a certain number of years before being eligible for benefits. The taxes were collected in the 1930s, but the first benefits were paid in 1940.

      Because of these very restricted eligibility requirements, SS ran HUGE surpluses for decades. This had deleterious effects in the long run, because bad policies were hidden by the surpluses, and are now politically impossible to fix.

      It's going to get really hard to find enough under 30 people to support an aging society.

      Yet every time Slashdot has a story on AI or robotics, the consensus is that all the jobs are going to disappear. So how can there be a shortage of both workers and jobs?

    5. Re:Young people? What young people? by AmiMoJo · · Score: 2

      So how can there be a shortage of both workers and jobs?

      There is a shortage of workers to pay taxes. There is a shortage of jobs to employ workers to pay taxes.

      It's from society/the government's point of view, not the corporations.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  5. Re:No by ZecretZquirrel · · Score: 2, Funny

    Eating them, and maybe even spelling a few correctly.

  6. Re:No by mikael · · Score: 2

    Companies working on embedded systems for aircraft, cars and other road vehicles really care a lot about performance, especially when there are so many different CPU and GPU's on the market, all priced by the core, clock speed and pixel draw rate. If they can maintain interactivity while being able to use a cheaper CPU/GPU combo, they will.

    --
    Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
  7. Been there back in 1999 by Anonymous Coward · · Score: 5, Insightful

    When I was working for a big consulting firm in 1999 there was a big push at the time to create multiple tracks of "advancement" specifically for the people that had no desire to be anywhere near the line of management.

    It worked to a degree, where the "Subject Matter Expert" in their field would be brought in as a tech resource - but like many initiatives it got bogged down by more and more layers of people trying to get a "piece of the pie" and hang on to the billable hours. The loudest people and the ones closest to where the money flows will always be more successful.

    The only way us "old farts" can compete is be just as nimble as the younger people and adapt to the game. Anyone who says we can't learn a new language, a new tech or whatever passes as "employably hot" never met one of us who are more than happy to come in and do what needs to be done - and we have the knowledge to Make Shit Happen. I don't need "corporate love" to keep me trained. I am a fucking geek all the way - and when I'm not writing medical interface code, I'm building/flying/racing drones, building robots, taking a plasma torch to metal sheets and building dragons for yard art, to messing with all flavors of IoT boards just for shits and giggles. It's all about attitude and a willingness to learn on your own. If there is a new language or tech I need to know to stay marketable? Then I do it. I don't wait for some employer to train me because sure as fuck if they get a client that has a need? They're not going to pay me to try and learn it - they'll hire someone else with that skill.

    Just be adaptable and open to change and you'll always have people wanting to work with you and hire you to do tasks that need to be done. The only thing that is permanent in life is change - and the sooner everyone embraces that instead of whining about it the better off we'll be.

    Is ageism a thing? Sure. But know your shit and be willing to eat the occasional effluvia from some corporate suit turd-hammer? You'll always make it work.

    I don't bitch. I laugh about it - all the way to the bank.

  8. IT is not unique by Bruce66423 · · Score: 4, Interesting

    There are many professions that make little provision for people who don't want to become 'managers'. The classic examples are police, nurses and social workers; if you want to carry on engaging with people, you can't accept promotion. In IT being a contractor often offers the opportunity to stay coding - though at the cost of long term stability in employment. Large organisations may have the space and sense to recognise that the geek over there knows stuff that they need to have on tap, but sadly the temptation is to assume that modern technology renders the knowledge obsolete; outsourcing is an experiment based on this hypothesis...

    1. Re:IT is not unique by ubrgeek · · Score: 2

      > So manager types who worked their way up into this system assume that everyone else should want to do the same thing.

      I've got a lot of years of management experience and through it all I've maintained that if I'm not providing opportunities for the folks who work for me to be prepared for their next job, I'm failing in my role. If they want to move into management, I'll work with them to get them into management courses. If staying in positions that provide more opportunities to be hands-on with the technology, I'll help them find courses they feel will help them up those skills (whichever ones they find most interesting).

      I never understood the mindset of "If we train them, they'll go elsewhere." It generally takes more than just a single factor for a coworker to go to another job. Providing training isn't any of them.

      --
      Bark less. Wag more.
  9. Re:No by nospam007 · · Score: 4, Insightful

    "AC because I have a feeling the downmod from some pissed off old geyser is coming..."

    At least we old geezers know what a geyser is, you young whippersnapper obviously don't.

  10. Re:No by ShanghaiBill · · Score: 4, Interesting

    companies have moved from offices and cubicles to giving everyone one or two meters of desk space sitting face to face and side to side of each other

    Can you cite any actual evidence that open offices are more prevalent today?

    My experience has been the exact opposite. I worked as a programmer in a bullpen in the 1970s, a cubicle in the 1980s, and a real office ever since. Apple is famously moving in the wrong direction, but I don't think that is typical. I am aware of several companies that switched to quiet offices with walls.

    Also, as an old geezer, I have never felt discriminated against, and I have never felt that my age or experience was a handicap. I am open to learning new skills, and often start using new tech before the younglings, but I love it when a 20-something learns about an elegant tool from a more civilized age.

  11. unlink health care from jobs by Joe_Dragon · · Score: 4, Insightful

    unlink health care from jobs.

    That can free up people who are just there for the health care

  12. Re:No by Anonymous+Brave+Guy · · Score: 5, Insightful

    Older workers should adapt with the times, not vice versa.

    Older workers are experienced enough to know that not all change is for the better.

    Also, it's tough to make progress if you keep throwing out all the people who learned lessons already, and then spend the next generation of staff learning all the same lessons again.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  13. Re:No by PPH · · Score: 4, Interesting

    adapt with the times

    Been there. Seen too many instances of Language Du Jour come and go. I don't want to split the office into the tabs vs spaces warring camps. I don't want to incorporate some state of the art 3D gaming graphics engine into our simple engineering app interface. And I don't need every inter-office communication in PowerPoint.

    --
    Have gnu, will travel.
  14. Re:No by Pig+Hogger · · Score: 5, Insightful

    Older workers should adapt with the times, not vice versa. That's the only way progress will be made.

    As an old fart (look at my #), yes, old farts should adapt, but young squirts need to listen to old farts’ experience.

  15. Retaining older workers is easy by ErichTheRed · · Score: 5, Interesting

    I'm 42, so I think I officially qualify as old. Yet, here I am still doing senior-level engineering work. I'm not a DevOps ninja (yet...) and don't code 16 hours a day, but I really enjoy my job. I'm hoping for the day that more employers will see that older workers who are still contributing aren't a drag on the company they work for -- they're the adults that are needed to redirect some of the "bright ideas" and temper them with reality and experience. Unfortunately, we're a society that worships Silicon Valley wunderkinds and 24-year-old CEOs, and even boring old school companies are trying to behave like web startups. So here's my suggestions -- companies shouldn't try too hard; if they do even some of these things they will retain talented older workers:

    • Like the article says, have a technical track people can move along. Before my company implemented an "official" parallel career track for skilled technical people, lots of older people were "promoted" into management. It was the only place to go if you wanted to continue up the career ladder. This works great in traditional paper-shuffling corporate work, but IT, science, R&D, etc. is work that people actually don't mind doing and some of us would rather continue doing so. Traditional corporate jobs tend to promote people out of work, and most people are happy for this because who wants to shuffle paper? But, technical work and managerial work are _not_ related, not even close. The alternative for promotion on the technical track (at least for me) is being trusted with greater responsibility and helping with developing our junior staff. This (IMO) is a much better use of my skills than a management job would be.
    • Understand that older workers can't live at work. It's not a sign of disloyalty or laziness to put in a reasonable amount of hours. Most older workers don't want to continue their college dorm days and live at an office with their co-workers. The way I manage it (with a huge volume of work) is to stay reasonably productive during the actual workday so I don't have to spend 13 hours a day at the office. Many older workers have kids and families, but it's also not the 1950s anymore where the husband was the sole breadwinner and would do anything the company told them to keep their job.
    • Be flexible! This is one that gets major flak from the vocally child-free crowd and the younger set who have fewer out-of-work responsibilities. I have 2 kids, and the shorter work commute between my wife and I, so I do a lot of school activity appearances and other things during the day. But, I also regularly do the odd task for an hour or two after the house goes to bed. The company I work for gets plenty of work out of me; it's just not all in contiguous blocks.
    • Lay off the preschool workplace furniture a little bit. Most older workers can be trusted with a little personal space. Most of us also don't want to attend meetings sitting on orange and blue beanbag chairs against a bright white wall. Have a mix of traditional office space and Millenial preschool office space -- our company does because we tend to skew older. Not everyone is happy with open plan offices and for some people (like me) they can be productivity killers.
    • Appoint older workers as informal trainers. This is part of my job, and I'm actually someone who enjoys doing it. If you can convince your older workers that there aren't a bunch of MBAs waiting to lay them off as soon as the younglings' training is complete, this is a great way to pass on institutional knowledge. For this to work though, you have to provide...
    • Job security. I'm not talking union-level or tenure-level "we can't fire you for any reason", I'm just talking about dialing back the outsourcing/offshoring/layoff drama a little bit. I would (and have!) taken a lower salary to work somewhere that is more stable than your average web startup. Older workers with families want an income they can count on. Part of that is up to us (by keeping o
    1. Re:Retaining older workers is easy by Teun · · Score: 3, Interesting

      Spot on, when I turned 60 I became a full time mentor and instructor for the newly hired engineers.
      It's a win-win for all, the new guys don't have to repeat the stupidities of the past, I get exposed to some of the new tech they bring out of university and the company keeps the good parts of its proven production methods yet advances with the new hires.
      The older workers can be an effective glue between existing products, future developments and management.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
  16. Re: Muslims are a danger to the world by ShanghaiBill · · Score: 2

    You would be fighting back too if bombs were ripping through your village for no fucking reason.

    This is not supported by evidence. American drone strikes are widely unpopular in the muslim world. But the drone strikes are supported in the villages actually getting bombed.

    It is easy to oppose the drones when you live in safe suburb of Karachi or Islamabad. It is much different if you live in Waziristan, where the Taliban forces girls out of school and boys into war. Most people there see the drones as a benefit.

  17. Re: manifesto by PopeRatzo · · Score: 3, Funny

    Back when I decided to lose 50 pounds I discovered that the key is to find something you really enjoy. For me that was trail hiking.

    For me, it was hiking the block and a half to the Italian beef stand. Had to take an Uber home, though.

    --
    You are welcome on my lawn.
  18. Re:I have never understood by Tablizer · · Score: 2

    You can pay young people way less and work them to death because they don't know any better.

    Indeed! Our young architect shoved every possible layer and service he could into our MVC stack. He's either a feature pack-rat, and/or trying to pad his resume with every buzzword he can.

    Most the devs are young and don't know the difference and probably want to pad their resumes also with the gizmos. Thus, development is turned into a typing contest, and young fingers will probably win that one.

    My only hope is to convince the suits it's bloat and bullshit, but the architect has so far been out brown-nosing me. I probably lost this round. The suits may realize its bloat a few years down the road, but that may be too late.

    I suspect the architect is intentionally trying to get rid of the old people because we know enough to question his judgement. He's using buzzwords to paint us as outdated and using a bloated stack to make it a typing contest between young fingers and old fingers. Clever bastard. He'll probably trim the stack once we are gone.

  19. Wrong problem by rsilvergun · · Score: 4, Insightful

    with automation and productivity improvements it's going to get hard to find enough work to go around. For example, with Trump & co blocking farm immigration farmers are finally implementing the kinds of labor saving practices (like growing food at waist height so it's easier to pick) that Europe's had for 20 years.

    That IT shortage is a lie. I've got a guy at my job with a CS degree from a public University who's doing crap IT work instead of programming for a living. 20 years ago he would have been snapped up a day after graduation. But 20 years ago the H1-B program was in it's infancy.

    There's plenty of money to go around. You're being lied to so a small group of lucky assholes can take everything. Not that I know what to do about it.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  20. Re:No by Anonymous+Brave+Guy · · Score: 2

    More often than not in this context, we're not talking about management issues but technical ones. The way you (successfully) institutionalize those lessons is by having people on your staff who have worked with technology for more than five minutes and seen the problems before, so that when they come up again, you can avoid the mistake and educate the less experienced staff about what you're doing and why.

    So many times in the past few years, I've looked at failures, sometimes serious ones, in software projects and thought that the only way you could possibly wind up in that position is if your most experienced technical employee was a 26-year-old CTO who thought that moving fast and breaking stuff was a good idea...

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  21. Re:No by thinkwaitfast · · Score: 3, Insightful
    I've worked with old engineers who were still stuck in the mainframe mindset and totally unaware of the raw computing power of a generic garage assembled PC. OTOH, they had deep hardware experience for which they earned $5000/day consulting on problems that teams of younger engineers couldn't solve in a month - because they had already solved the same problem 30 years before. This is the black magic that made Intel what it is.

    Old engineering joke:

    Henry Ford once balked at paying $10,000 to General Electric for work done troubleshooting a generator, and asked for an itemized bill. The engineer who performed the work, Charles Steinmetz, sent this: "Making chalk mark on generator, $1. Knowing where to make mark, $9,999." Ford paid the bill.

  22. I saw the writing on the wall by Hasaf · · Score: 2

    I looked around and realized that there were no older workers in my position. There are always ways to push people out the door, and they were being used. I even looked at other companies and saw the same.

    I decided to get my teachers license (I already had a Masters; so it was a pretty easy process). Yes, I have to deal with middle school kids; but I look at my friends who tried to stick it out and they are doing things like delivering pizzas.

  23. Personal responsibility by Snufu · · Score: 4, Funny

    These people chose to be old. Nobody forced them. Hold people responsible for their decisions.

    Damn nanny state.

  24. Re:No by Anonymous+Brave+Guy · · Score: 3, Interesting

    I am open to learning new skills, and often start using new tech before the younglings, but I love it when a 20-something learns about an elegant tool from a more civilized age.

    Interesting. I'd say the biggest difference between 20-year-old me and 30-year-old me was probably was that 20-year-old me wanted to learn All The Things, while 30-year-old me was a lot more choosey about where limited time was spent.

    I find bleeding edge technologies interesting, but I only rarely spend much time on something that is still in its early adopter phase any more. Consequently, I often am a little behind the enthusiastic youngsters in adopting new tech.

    However, if you look at how effectively I use the new skills and technologies that I do adopt, or the proportion of the new skills and technologies I adopt that remains useful in the long term rather than quickly becoming obsolete, older me does much, much better than younger me.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  25. The problem is obvious by MpVpRb · · Score: 2

    Older workers aren't obsolete, they're just more expensive

    Managers need to re-calibrate their measurements

    Young managers who fail to do this, or who care more about culture than results, are missing out on a vast talent pool

    1. Re:The problem is obvious by zifn4b · · Score: 3, Insightful

      Older workers aren't obsolete, they're just more expensive

      Managers need to re-calibrate their measurements

      Young managers who fail to do this, or who care more about culture than results, are missing out on a vast talent pool

      You get what you pay for. I've seen quite a few companies go under with software platforms written almost exclusively by recent college grads and H1B visas. As soon as they put any real load on the system, it buckles. When this situation occurs, the people who created the problem due to incompetence and inexperience just jump ship and go do it all over again somewhere else.

      --
      We'll make great pets
  26. Re: No by Ol+Olsoc · · Score: 2

    Shut up. Every generation says the same crap about the next generation (accept for their own spawn who are somehow angels). No generation in America has done more to destroy this country than the Baby Boomers. They will be the first generation to leave this country in worse shape than it was when they inherited it.

    Want cheese and breadsticks to go with that fine whine?

    --
    The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
  27. Re:No by dcw3 · · Score: 2

    Interesting. I'd say the biggest difference between 20-year-old me and 30-year-old me was probably was that 20-year-old me wanted to learn All The Things, while 30-year-old me was a lot more choosey about where limited time was spent.

    And IMO, this is a good thing because it gives the 20-something exposure and lets them see what they're really interested in, and eventually the realization that they don't know what they don't know, and never will actually know it all.

    --
    Just another day in Paradise
  28. Re:No by dcw3 · · Score: 2

    Older workers should adapt with the times, not vice versa.

    Older workers are experienced enough to know that not all change is for the better.

    Also, it's tough to make progress if you keep throwing out all the people who learned lessons already, and then spend the next generation of staff learning all the same lessons again.

    You can't stand on the shoulders of giants if you keep pushing them out the door.

    --
    Just another day in Paradise
  29. Sounds like a plan by whitroth · · Score: 2

    I've been in my current job for twice as long as any other job I've had in my life. However, when I was interviewing, one of the things I always said was, "if you have a tech track and a management track, I'm on the tech track."

    Not everyone should, or wants to be a manager. There are far toom many people who REALLY, REALLY SHOULD NOT BE A MANAGER. On the other hand, those folks may be really good at what they do.

    Do you *really* want the manager who really knows the systems in an "emergency" meeting that runs on for hours, while a new hire who doesn't have anywhere near the experience as the manager, never mind they don't know the systems deeply yet, try to deal with the disaster?

    If you think it should work that way, congratulations, here's your MBA, now get out there and destroy your company, too.