5 ms·
Doesn't mention the benefits of attrition. A network can be robust since none of the pieces leaves, but what is even more robust is a network that constantly re
by Jensson 5y ago
Doesn't mention the benefits of attrition. A network can be robust since none of the pieces leaves, but what is even more robust is a network that constantly renews itself and gracefully handles the process of swapping out parts. Constant attrition means that your company never starts relying on individuals, instead the process survives and thrives on its own, hiring new people who then hire new people before they leave etc. Such a process isn't very attractive to individuals, of course, but they are very attractive to the owners.
- tangjurine 5y agoThink about having a robust network like being able to fly. You don't develop the ability to fly by placing yourself in positions that require flying... Most companies that have lots of attrition have bad processes in place and are suffering due to attrition, although I think there are some companies that are developed enough to benefit from attrition like you described.
- jackblemming 5y agoDo you have any evidence to your claim? It’s possible to ad hoc rationalize pretty much anything. A real statistic against your claim is one of the highest predictors of defects in a code base is whether or not the original team is still working on it.
- bncy 5y agoNot to mention vision that will change due to new ideas or influence that new staff brings to the team. It's not always beneficial for the project. It can go wrong in so many ways that it ends up being dead. Don't get me wrong, change is good but too much change is just too much to handle sometimes.
- Jensson 5y ago> highest predictors of defects in a code base is whether or not the original team is still working on it. Defects is a metric businesses doesn't care much about. If you have a good team that can create products customers wants, then it is better to have them keep making new products rather than maintain what they already have, then you can have less productive engineers perform maintenance, defects might go up but this way you will have way more products which businesses seems to care more about. You would have a point if maintenance was something companies cared deeply about, but they don't. They want new products, and company specific knowledge doesn't seem to be very valuable there.
- bdavis__ 5y agofrom a different angle: "non original team" might have higher defects, but i propose that "non original team" without process or time to understand the code base would be more accurate. changing people requires a time investment. and the learning curve is steep at the beginning
- enord 5y ago>Defects is a metric businesses doesn't care much about. This depends on both the defect and the business. Just because critical regressions and recurring denial of service has become normalized as somehow par for the course in our line of business does not mean it comes without cost. It's all situational and subject to calculated tradeoffs but every shop i've worked with/in has classes of defects on the "Never Again" list, and sometimes on the "NEVER EVER EVER AT ANY COST" list.
- gostsamo 5y agoIn order for a part to be entirely interchangible, you should choose the smallest common denominator of all parts to rely on as the highest value that you can get from one. I think that one must find an equilibrium but it requires active management and careful thinking to be executed properly.
- laurent92 5y agoOr to have great onboarding, people learn a lot, are effective quickly, and leave after learning enough. The know-how is then embedded in the process not in people, which guarantees stability, while people are guaranteed to change.
- gostsamo 5y agoIf you can embed all of your organization's knowledge in a few weeks of a single person's study, then you don't have much knowledge to begin with. Such stuff might be good for a small factory, but for nothing more complex than that.
- Melkman 5y agoI don't think it works like that. Constant attrition does not prevent your company from relying on individuals. You don't fire you good employees and they won't leave if it's a worthwhile job. With constant attrition you get a core group you rely on. However that group is not as productive as they could be because they spend a lot of time training and integrating new employees that don't stay.
- ikr678 5y agoThat sort of anti-fragility isnt a guaranteed outcome of attrition though. You can just as easily be left with a pool of under-performers that can't/won't leave, while talent moves to organisations that invest more in staff vs processes.
- nindalf 5y ago> very attractive to the owners And yet I’ve worked at software companies that will go to great lengths to avoid attrition. For exactly the reasons mentioned in the post, they encourage people to move to other teams to build up the inter connectedness of teams while keeping employees motivated and engaged. In fact, even if you weren’t looking HR would reach out and ask if you were interested in looking at other teams within the company because you had been in your current team for 18 months. Side note I don’t know if I’ve just been lucky but I can’t relate to this talk of “companies are evil and act maliciously against their employees at every opportunity”. That hasn’t been true in my experience.
- Jensson 5y ago> For exactly the reasons mentioned in the post, they encourage people to move to other teams to build up the inter connectedness of teams while keeping employees motivated and engaged. That isn't to avoid churn, that is to have more people around in general. If you leave your old team it means you no longer use your knowledge, the important part is to have engineers around, not to have the same engineers working on the same tasks. For example, Google encourages churn by making it really easy to move to other teams in other areas. You don't talk to your old team again, so that is effectively the same thing as you leaving the company and them getting a new engineer, ie for the teams it is equivalent to churn.
- enord 5y agoMilitary veterans of some theater of war are desired exactly because they will perform well in the next theater of war. I don't think i can fully appreciate how mind-bogglingly huge a company like Google is, so it might well be the case that tacit knowledge, skills and relations acquired in one team don't transfer meaningfully to another. I would have to see it to be convinced however, even more so to make me believe this kind of transfer was the norm.
- michaelt 5y ago> If you leave your old team it means you no longer use your knowledge, If you move from Team A to Team B, you may not use your knowledge of the details of their codebase. But you know precisely how to sort out the problems caused by the company's weird internal certificate authority, and their weird internal deployment tools, their weird internal inter-service auth system, and their weird internal multi-cloud system. That 'secure' way of managing secrets in production that makes 'unauthorized' errors almost impossible to debug? You know how to debug it. You know how to operate the purchasing system so your orders go through right the first time. You know precisely what the criteria are to get your subordinates promoted, and how to coach them to meet the criteria. That can be worth a lot, when it comes to getting things done.
- enord 5y agoI mean, for assembly-line production this might ring true (I wouldn't know, never did it). But for what one might reasonably categorize as "knowledge work", my experience is that knowledge reigns supreme. Some of that knowledge is shared by a whole community of practitioners, other parts of it is local and contextualized. This part probably makes up a sizable proportion of an organizations competitive advantage. To make workers replaceable is to rely mostly on the knowledge you can reasonably expect to regain on rehire. Remember: Management (up to owner-management) are also workers, so running some kind of special culture-and-knowledge preserving über-organization is predicated on somehow retaining the structures that support and maintain this secret sauce. Military services around the world have researched this extensively (for obvious reasons), then again, we refer to a well-seasoned and experienced practitioner as a veteran. Veterans are invaluable in military service, as they are in any other endeavor. Trade them off against ease-of-management at your own peril.
- rightbyte 5y ago> I mean, for assembly-line production this might ring true Not there either. You mess up more in the beginning. Experienced workers have better flow.
- enord 5y agoI would assume this as well, when i think about it. I guess learning about the industrial revolution in school kind of messed up my preconceptions. Anyhow, this military comparison just keeps sprouting thoughts in my head. Isn't an owner-management almost perfectly comparable to aristocratic officership? Is GGP's theory of defensible churn basically a modern incarnation of feudalism and aristocratic privelege?
- jack_riminton 5y agoIn the military attrition is even worse because you can't fill gaps by hiring from any competitors!
- odiroot 5y ago
- rightbyte 5y agoSounds like wasted effort. Relying on individuals are good, since it means they are somebody to rely on. Anyways, hand over in high turnover places is shitty anyways, since they are shitty places to work at.
- mooreds 5y agoThis is very true. Attrition helps with cross pollination as well as enforcing process and knowledge sharing. However, I'd submit that it doesn't matter how good the docs and process are, you're going to lose a lot when an engineer who has been at a company for, say, 3+ years leaves: * historical knowledge * personal relationships * intuition about the systems Some things you can't get except by putting in the time.
- anyonecancode 5y agoI think the rate of attrition matters. Too little change and you get stagnation -- you do need that ongoing renewal you call out, and the incentive to create good processes. There is a tipping point though, where attrition isn't renewal, it's erosion. It's the difference between "small fires that clear out the undergrowth and a few large trees" vs "large fires that denude a hillside that then destabilizes into a mudslide."
- datavirtue 5y agoHmmm...I and a few other top developers on a corporate team just left a project and company because we were being mindlessly driven by management. Management really tried to be accommodating, transparent, and woke in their treatment of employees but the work load was just too much. One sprint into the next without any breath in between. Tenure averaged about one year on the team. The project has been going without release for three or four years. The only people left are juniors (college grads basically) who don't realize how bad it is wrecking their health. The only thing keeping their main SME dev is the generous PTO. She is always out sick, randomly. A lot of it was obviously the stress. She would always let out this lengthy loud exhale on calls and in grooming sessions. When I started doing that I began the exit.
- spaetzleesser 5y agoThat’s a management pipe dream. The software verification teams at my company have very high attrition rates and it’s getting really tiring to deal with newbies who don’t understand the product or why things are the way they are. You can’t really replace experience with process. It works well only in very simple and well understood cases.