How to kill software quality in five steps
0 likes•332 views
The document outlines five steps to intentionally undermine software quality. These steps include disregarding design patterns, avoiding testing and refactoring, neglecting continuous integration, and ignoring user feedback. Following these guidelines will effectively sabotage the quality of a software project.
How to kill software quality in five steps
- 1. How to kill software quality in five steps @walmyrlimaesilv
- 2. The origin of this talk
- 3. About me
- 5. Step 1 - Don’t care about design patterns and clean code
- 6. Instead, write as much spaghetti code as possible
- 7. Also, refuse linting tools. They will block your creativity.
- 8. Step 2 - Do not test your application
- 9. But if you want to test, don’t do it in an automated way. This is a waste of time.
- 10. Test manually instead, and just what you changed/added
- 11. Step 3 - Avoid refactoring
- 12. Instead, leave the campground dirtier than you found it
- 13. Step 4 - Don’t use continuous integration (CI)
- 14. Instead, make the feedback loop as difficult as possible
- 15. This way, no one can blame you when you break something
- 16. Step 5 - Never listen to user’s feedback
- 17. In the end, they never know what they want anyway
- 18. Recapping 1. Do not care about design patterns and clean code 2. Do not test your code 3. Avoid refactoring 4. Don’t use CI 5. Never listen to the users
- 19. If you follow these five steps I guarantee that you will be able to sabotage and kill the quality of your software project.
- 20. The End.