Sounds like this person is swallowing and licking up whatever corporate gives them. But as many have or will find out, companies don't love you like that. Lif

Sounds like this person is swallowing and licking up whatever corporate gives them. But as many have or will find out, companies don't love you like that. Lifetime employment at the same company is just about dead too. When that pay raise doesn't happen, when cuts to the staff come down, when that other or junior person get's chosen or promoted over you, when your job get's outsourced, etc... It's about their profits, not you. Somehow this person has got themselves so twisted up in the corporate game, they don't know the difference between "hermit programmer" and "bad programmer". Below is a list of traits of bad programmers. Saying that only an independent or hermit will do one or more is to be blind to reality: 1) they don’t plan 2) never know if they are going to finish a task 3) they don’t document 4) their code is not reusable 5) they don’t test 6) code they write is full of bugs 7) they don’t refactor 8) the software cannot evolve 9) they don’t have good communication skills 10) they don’t diversify their skills 11) powerful AI will take over their workplaces As for AI, corporate is more likely to use such to eliminate jobs internally, to save themselves a few bucks. In addition, corporate environments and teams don't produce bug-free code and management can lead a project "off a cliff" to where it fails. Just because a team of people think they are doing the right things, doesn't mean they actually are nor is there any guarantee of success. Doing things by committee can also be a source of vicious arguments, resentment, and project stagnation. Every team isn't effective or efficient, so can depend on the situation. Bad programmers can exist in corporate environments and teams too, because they are able to abuse the power of their position or fool management for a while or prior to them jumping ship unexpectedly to another company.