"The answer is... it depends"
summary
Explores trade-offs in designing maintainable, extensible software by examining common rules, laws and patterns developers use (no specific technologies named). Focuses on risk minimization and maximizing benefits when selecting approaches, and offers guidance for choosing better answers than simply saying “it depends.”
AI-written summary · about
chapters (11)
- 0:00Start
- 4:24CUSTOMERS ARE ALWAYS RIGHT
- 6:30STAKEHOLDERS DOES NOT KNOW WHAT THEY WANT
- 12:11WATERFALL RULEZ!
- 14:35AGILE IS A SILVER BULLET
- 20:20IN-OFFICE WORK IS THE ONLY OPTION
- 21:54REMOTE WORK OR NOTHING
- 25:50REFACTORING - IMPROVEMENT
- 27:51REFACTORING IS A WASTE
- 33:26YOU HAVE TO DO
- 35:08IT TAKES MORE TIME WITH
related talks
45mGeneric or Specific? Making Sensible Software Design Decisions
25mThinking Architecturally
41mBeyond "it depends" - How much architectural work do we need?
51mGeneric or Specific? Making Sensible Software Design Decisions
33mFrom Enterprise Architecture to Software Design - Critical Thinking
44mDeliberate Architecture
55mUnderstanding Modern Trade-off Analysis in Software Architecture
57mSoftware Architecture: The Hard Parts
