I worked in a QA role for 19 yrs and here are my comments:
1. Yes, the primary QA role is to find software bugs
2. Automation testing will not help with finding software bugs may with some minor exceptions. Automation is more used for doing a quick functionality check.
3. For large systems, it is not always possible or reasonable to automate all test cases.
4. Software developers should be testing their code aka doing unit testing. Software developers usually don't have the time to do good unit testing.
5. Yes, software developers can do automation UI testing if time permits and software developers know how to use a software program from an accountant's point, for example.
6. When bugs are going into production, it is not always the developers' fault. This is more BA issue unless the QA team is not very mature and missed key tests.
7. If a QA reports a false positive issue, then the QA needs to become more experienced
8. Developers and BAs should not be worried about the QA team slowing down the release cycle b/c the software should be working as expected no matter how many developers and how many changes the developers put into the software program. It is not just one functionality, but all functionalities should be working as expected.
9. There should be a QA judgment decision what to check and what to skip for a particular functionality. The QA should know how fast it will take to check. The QA should not just start checking everything.
10. For very large and complex systems, it takes a lot of time to think about what test cases to setup, how to setup them up, and all the necessary test cases that cover the most common test combinations. Developers don't have time to do this thinking, planning, setup, and checking. Developers should be looking at the code changes.
11. It does not matter whether a software bug is new or outdated when a software does not do what it is supposed to do. Some bugs or behavior make a user's life a nightmare. Therefore, software developers should address most bugs reported unless it is not reasonable.
12. The Devops rule should be done by a DevOps engineer.