Good practices — why are they good?
summary
The talk examines which software development “best practices” are actually appropriate at different stages of a project, contrasting needs for an MVP versus a mature product and for forming versus mature teams. It reviews concrete agile practices—automated tests, continuous integration, continuous delivery/deployment, Git Flow, refactoring, collective code ownership, and pair programming—and discusses when and how to apply them, illustrated with over 20 years of industry experience and examples from Sherpa.ai.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:52What is a good practice?
- 2:08Business + Technology
- 17:2825.000 pruebas automáticas 15.000 pruebas interpretación 12.000 e2e metalingua 300 e2e sdk
- 26:40Collective ownership of the code
related talks
27m'The Art of Software Development'
54mANTIDOGMA
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
54mAPI team characteristics and best practices
46mIt’s XP Stupid!
33mSoftware development practices for companies that want to make an impact
09mSoftware engineering practices to improve management
