Every Bay Area company I’ve worked for(except 1) does not have QA. It’s expected by the time the dev merges it it’s been appropriately tested and can go straigh

Every Bay Area company I’ve worked for(except 1) does not have QA. It’s expected by the time the dev merges it it’s been appropriately tested and can go straight to prod, so no need to wait. Fewer, smaller releases is generally better when something does go wrong as well, it’s more obvious which change is the problem. The one that did have qa, the devs were incredibly lazy about testing, relying entirely on someone else to make sure it worked. I’d say the overall product was better with qa but the point at which a developer called it done was way worse.