[gitgud]

> When I suggest we find consensus on an architecture or coding practices or even commit conventions, I get blank faces that seem to ask "what are you talking about". I feel gaslighted about tech debt.

Depends on the size of the company, if you're frantically finding product-market fit, then this is fine. However, if you have an established product, then you might be correct in explaining the benefits of solidifying an architecture and best-practices...

TLDR: YOLO dev until the product resonates with customers

[jimbomins]

I don't think size of company is as relevant as the market sector. My employer is a 40-50k work force globally and it's bash stuff out. But similar size companies doing medical or CNC, etc, where errors kill write to best practice.