I've requested that you delete my account in the past, requests which you routinely ignore. Apparently neither one of us is very good at following directions.
Lie with dogs, you get fleas. I have zero sympathy for those who fall prey to closed ecosystem BS like this, including my own wife. People just don't listen.
My mother had a DNR. She contracted meningitis, and died. She was resuscitated, suffered severe brain damage, and lived another 2 years as a semi-vegetable before dying in her sleep after choking on her own vomit.
If I believed in such things, I would hope my stepfather is in Hell.
>You don't want to be working with someone who can't work with other people.
That describes me pretty well, and those with whom I work love me. They just keep me in my little box, leave me alone and let me do my work. But they are also a grown-up company that doesn't make people wear 27 hats. PMs do their job, Infrastructure does theirs, Client Support does theirs, etc. Not every job has the same requirements as every other job.
> naively doing everything your own personal way (including at the team/company level).
You, and my downvoters, all assume (naively) that any in-house standard must somehow be different than "widely-adopted coding standards (that most frameworks probably use)". Obviously, that need not be true, and in my limited 40 years of experience, it rarely is. Not sure how you even got there.
> As someone else pointed out in this thread, a great advantage of established frameworks is that they provide a coding standard for a team.
So it's useful for young, inexperienced developers. Do you kids really not have in-house coding standards anymore, or do you rely on your toolsets to provide that for you?
There is a segment of the populace who feels that every "wrong" must be "punished", and they generally make life miserable for everyone else. Usually no one will speak up for fear of being punished along with the "guilty".
I disagree. A different approach would be to say "Don't know what happened before, but moving forward Ted is accountable for A, Alice is accountable for B, etc". Knowing what happened before serves zero purpose except to shame. All that effectively matters is what happens from this point forward. You put a process in place this time, to monitor what Ted and Alice are doing. Next time, it's your fault when it breaks, because you were forewarned, and you should have known better. Next time, you know what happened, because you put controls in place.
Or just throw someone under the bus and keep repeating the same mistakes.
Fixing begins at "someone screwed up". Blaming delves into who screwed up, which is usually not required to fix the problem (since there may actually be no one to blame).