If you focus on increasing engineering quality, retention will follow. > there's still an astounding number of bug reports for a simple app. Why don't you rev

If you focus on increasing engineering quality, retention will follow. > there's still an astounding number of bug reports for a simple app. Why don't you reverse engineer some of these bugs and see how & when they were introduced. What step in your development workflow should have caught those? > The development process is indeed slow and full of fail-safes I have seen engineers who focus on less meaty stuff in code reviews (language semantics, coding conventions, naming etc) and miss out on system design, regression, logical mistakes etc. Former takes less mental effort & is limited in it's usability while latter takes time/energy but is worth the price. See if this is happening in your organisation. > how they actively engage in bickering and in-fighting between their own teams My guess is some of your engineers are less focused on product/features/customers and more on the stack/technology/tools they are using. I don't know how to change this (lead by example maybe?).