Ten Commandments of a Software Engineer
summary
Ten concrete rules: write unit tests no matter the deadline, keep the build green, commit often with meaningful messages. Recommends git over CVS/Subversion, CI, Selenium and Behat for automation, PHPDocumentor, PHP Copy Paste Detector and Sonar for quality. Gives a real refactor: a WordPress‑sized legacy rewrite by 3–4 developers over ~4 months that extracts business logic and replaces the application tier. Notes an extreme claim of ~200 commits/day and urges hourly commits and small, test-covered changes.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:00Who is Sebastian
- 3:20What I want to do today
- 4:28Software Craftsmanship
- 7:33Development Cycle
- 8:02Project Initiation
- 8:30Legacy Systems
- 9:40Refactoring
- 11:13Documentation
- 15:43External
- 16:03Communication
- 18:45Complexity
- 19:02Overengineering
- 22:03Simplicity
- 22:15Frameworks
- 25:34Commit often
- 26:02Use the right tool
- 28:28Cold commit logs
- 31:25Code
- 36:48Testing
- 39:39Closure
- 41:35Conclusion
- 43:33Recommended reading
related talks
48mEnding Keynote: 7 Principles of Productive Software Developers
33mWhat it takes to become a great developer!
50mThe Effective Developer - Work Smarter, Not Harder
25mCode Review of Senior Python Engineers
01h 02mAll Things Open 2020 Keynote (Speakers Only) Day #2
22mDo We Need Software Craftsmen?
27m'The Art of Software Development'
31mThe Effective Developer - Work Smarter, Not Harder