Software Craftsmanship
summary
Claims that almost 99% human-factor causes project failure and that one software engineer was jailed after Dieselgate underscore moral and legal risk as systems control physical devices. Recommends concrete practices: post-code culture (small continuous refactors), TDD = design tool (write tiny classes and tests), strict clean code rules, regular knowledge sharing and feedback, avoid hype, and carve out roughly 10 hours/week learning to keep skills current and reduce technical debt.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker background
- 1:13Why projects fail and human factor
- 3:30Company culture and engineer empowerment
- 6:51IT as idea generator in companies
- 8:51Personal professionalism and happiness
- 11:46Reputation and moral responsibility
- 13:15Moral reasoning in engineering
- 16:49Future risks and ethical dilemmas
- 18:58Software craftsmanship origins
- 20:04Practice of code crafting
- 21:52Test-Driven Development explained
- 24:22Clean code and maintainability
- 26:57Team knowledge sharing
- 28:46Engineer initiatives and feedback
- 30:29Continuous learning and growth
- 31:55Conclusion and Q&A
related talks
49mExtreme Professionalism - Software Craftsmanship.
17mThe Way of The Software Craftsman
41mComputer Science, Software Engineering, and the Scientific Method
13mCraftsmanship unraveled
20mCraft, TDD, DDD... Should I Feel Guilty for Not Doing Them?
59mTechniques for writing high-quality code
55mThe Art of Software Development
57mCore Software Design Principles for Programmers