Change My View: There is no point in having software quality assurance seperate from software development.

There is nothing a software quality engineer does that should not be done by the developers who write the code.

There is no point in writing code without afterwards validating that the work meets the requirements defined beforehand. It is the responsibility of the developer to meet these requirements and ensure they are met before submitting the work to any non-development branch. If the requirements have been properly met and tested then the role of QA is not to revalidate these requirements, it is simply to collect information about how the application behaves, which once again is the responsibility of all developers to ensure the application behaves as required.

In fact, having this seperation between developers and QA is detrimental to the software development process since it requires developers to context-switch between tasks when defects are revealed after the code has been submitted to testing. If the developer understands that testing and validating their work is completely their responsibility, they will test more thoroughly and include regression testing in their daily tasks to ensure that no defects are revealed farther down the pipeline.

Automated/regression testing can be written and maintained by every developer, it doesnt need to fall under the umbrella of QA. If both developers and QA are capable of writing, maintaining, and assuring that code works and meets business requirements, why have an unnecessary seperation that simply adds another layer, and complexifies the development process.

Change my view.