I don't think you examined the code in full. main spawns 10 go routines that are constantly sending player scores to the game. That means 10 different players are sending their scores concurrently until someone reaches score of 100.
This and also when you newly join a team it is more productive to start using the tooling what they are using and move to preferred tooling once familiar with the API endpoints.
Isn't politics any part of human activity where number of people involved is greater than a critical mass (of say 5) ? I think even the best run, successful orgs have their share of politics. I used to think politics as a bad thing, but now I have accepted that it is an inevitable part of work life and one needs to also learn how to navigate it atleast to the extent that doesn't affect one's well-being or doesn't make one feel that they are being shortchanged, not that I am always successful with it.
"Politics" are inevitable, but the stuff that the parent is describing is a particular type of politics that comes with hierarchical power (and possibly bad/immature leadership?)
General pattern is that certain people in the level(s) above you are fighting for influence to impress the levels above, and critically, are willing to use the levels below in order to achieve their personal goals (organizational goals are secondary, at best). Unless leadership is unusually adept at punishing the first signs of this behavior, it quickly becomes pathological. Every level gets infected, and before long your org has all of the backstabbing drama one might associate with an imperial court. In times of growth it's painful enough, but in times of limited resources, it's pure bloodsport.
There are people who can effectively detect and push back on the behavior, but they seem to be rare, and even more rarely make it into positions of influence. My theory is that it's so exhausting to be sensitive to the drama that you can only make it to the top if you combine it with a big dose of sociopathy. You also see it a lot at startups, because the founders are typically young, arrogant and have no experience managing anyone. By the time they realize they've hired a toxic exec layer, it's too late.
>> If there is an IDE available that works well out of the box, I'll certainly use whatever automation is available. But often it is broken, incomplete, slow, inaccurate, etc. ...
I think you are unduly harsh here. As a longtime emacs user and who switched to IDE recently (ones that come from JetBrains) my experience hasn't been what you mention. Yes there is a bit of time (not huge) to get adjusted to the shortcuts and efficiently navigate the code, but post that the IDE ecosystem is not as broken as you allude to.
If I'm working on a small hobby project by myself, or some open-source stuff, sure! I agree the Jetbrains stuff is great, I've been using them since 2001 with IntelliJ IDEA.
But most of the large industrial codebases I've worked on at FAANG companies break IDEs one way or another - either because of the build process, or the size of the codebase, etc.
Sure. And if someone showed up here with a story about how they got attacked and ransomwared enterprise-wide in the however many several hours that they were waiting for their turn to rollout, what do you think HN response would be?
Hmm, maybe you could have companies pay more to be in the first rollout group? That'd go over well too.
True, there will be comments blaming CS for not doing faster rollout. But there would be some comments empathizing with CS viewpoint and pointing out the conflicting compromise between velocity, and correctness. Even now I think the comments wouldn't have been unequivocally critical, of CS, if the hosts affected were a variant of windows (say issue was seen on version of windows 10 which was two update behind),there would have been some emphasizing the thorniness of the problem and sympathetic of CS.
It doesn't matter what kind of update it was: signature, content,etc. Only thing that matters is does the update has a potential to disrupt the user's normal activity (leave alone bricking the host), if yes ensure it either works or have a staged rollout with a remediation plan.
