Sifting Technologies - Separating the Wheat From the Chaff
summary
Argues for a concrete evaluation process: use architectural briefings to list problems, documentation, community and costs; follow with hands-on spikes against actual use cases and only trial in a non–mission-critical project. Cites concrete failures and wins — a team that landed four different UI frameworks, an org that destroys and recreates app instances hourly for security, the pain of Angular 1→2 upgrades and Equifax running unpatched Struts — and recommends filters like docs, tests, update history and hiring availability.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:10Evaluate New Technologies
- 12:54How Do We Know Where Not To Use the Technology
- 24:48Hackers Radar
- 28:54Innovation Fridays
- 29:30Architectural Briefings
- 33:48Key Use Cases
- 43:16Community Values
- 44:49Codebase
- 47:47Technologies Are Changing Rapidly
- 50:22Extensibility
- 50:51Support
- 51:52Stack Overflow
- 56:33Which Technology Should You Choose
related talks
43mThinking Architecturally
25mThinking Architecturally
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
57mSoftware Architecture: The Hard Parts
19mChoosing tech for the enterprise, like you work on The Enterprise
47mHow To Build Future Proofed Applications
41mThe monolith must die! - How to convince managers
29mFrom big to small and back again