| > why would you not allow them to specialize in that? Because it requires pre-hashed work. It requires someone else to do the politics for them. But we may be unclear on the definition of office politics. In this situation, the politics is simply drawing on a whiteboard an architecture with or without Kubernetes, taking note of who cringes and who is unhappy, and extracting the technical reasonings which a very real and legitimate for the future of our app. “I’ll be hella expensive”, “Will be awesome because every dev wants Kubernetes exposure” “Will be a hell because no-one know K8s”, all those concerns are not “playing office politics” but “finding and addressing the technical hurdles”. Once we know we want K8s, sure, any remoter worker can do it, but this is not the difficult part in that process. It’s like the chain factory was already set up, and here’s your seat. In a chain factory, the genius is not in the chain worker, but in the engineers who split the work. Remote people can participate in office politics, but the fact that during 3-days-remote-per-week, office politics only happen on the remaining 2 days, it shows it’s much more smooth in face-to-face. Perhaps with Apple’s VR… |