The Art of Software Development
summary
Argues software development mixes art and engineering and gives concrete practices: Picnic runs an online groceries stack across NL FR DE, automates style and safety with Google Java Format, SpotBugs/SonarQube and uses Error Prone and OpenRewrite to auto‑fix Java patterns, and runs RFC workshops and a Tech Academy that gives new hires 50% learning time plus a mentor. Notes Alberta bans the title “software engineer,” warns against bike‑shedding, and shows these tools and rituals reduce noise and scale successfully.
AI-written summary · about
chapters (24)
- 0:00Introduction and welcome
- 0:45Software development vs engineering
- 3:58Regulation and accountability in software
- 5:47Computer science vs software development
- 8:18The art of software development
- 10:23Software as creative craft
- 13:34Good code principles
- 17:48Code quality and context
- 20:36Automating code style decisions
- 23:26Focus on impact not tools
- 25:53Balancing value and code quality
- 26:35The art of testing
- 28:22Designing tests for maintainability
- 30:29The lost art of software design
- 33:59Trade-offs in software architecture
- 36:47Simplification in design
- 37:50Communicating design through storytelling
- 39:14Deliberate practice in design
- 39:55Process and team dynamics
- 41:20Team autonomy and trust
- 43:45Learning the craft of software
- 45:30Metis and apprenticeship
- 47:57Mentorship and legacy
- 48:17Working on what matters
related talks
27m'The Art of Software Development'
23mCode and Fear: Talent, Art, and Software Development
22mDo We Need Software Craftsmen?
44mA Plea for More Software Craftsmanship
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture
49mExtreme Professionalism - Software Craftsmanship.
14mThe Art of Programming
48mThe Effective Software Architect - Work Smarter, not Harder