I find #3 to be the truest malpractice. I'm getting to the point of becoming an architect at my current company. However, I don't even want the role. Our cur

I find #3 to be the truest malpractice. I'm getting to the point of becoming an architect at my current company. However, I don't even want the role. Our current team manager hasn't participated in software development in over a decade. It's a hindrance and much time is spent making arguments to actually follow commonly accepted good practice. I've led phases of design trade-off analysis where the conclusions were essentially forgone at the start. But to humor the disbelievers, we spent a few months testing alternatives. Even after my team had loads of evidence that one design was more performant and durable (with proper patterns used), people in the engineering peanut gallery questioned our methodology, because the results were contrary to their preconceived notions. These guys were leads and architects, who largely seemed unconvinced because they didn't do the work, so it couldn't possibly be correct. I want to contact my university and tell them to require some sort of "technical rhetoric" class in the curriculum. Appealing to emotion is really the only way to get things done in development when you tackle larger projects. No one believes empirical evidence anymore, nor do they care to follow good practices. It's mostly about leaving a turd behind, cashing out your RSUs after 3 years and letting the next guy worry about it.