Yes, I think this could be the crux: maintenance oriented vs prototype oriented practices
It reminds me of the testing versus debugging: some folks are great at testing code so it never breaks, others are better at churning out code and debugging it as they go.
Yes what drives me crazy is not that we're racking up tech debt (which is appropriate in some contexts), but rather that it seems I'm the only one with that healthy sense of guilt/shame, that foresight that our shortcuts now will pay off in headaches later. There's this unblinking straightfaced attitude of "why would we do it any other way?"
I feel super unproductive at work. Looking back at my career I've hit peak productivity when I could manage a codebase, the culture around the codebase, and external visibility. But the culture of my current group is: heroic hacking. Other team members seem able to work in this environment but I feel paralyzed in this atmosphere of slapdash jupyter notebooks, untested undocumented sprawling ML...