Under the red flag: how an engineer can tell something is wrong in a project
summary
Describes how an engineer can detect signs that a software project is going wrong due to poor technical decisions by management or the team. Covers practical indicators to watch for in high-load system projects and how to recognize systemic technical mistakes early.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:55What is a project fail
- 7:49Example 1: No automation
- 11:02Example 2: Bad server upgrades
- 14:37Example 3: High performance
- 18:12Example 4: Agile methodology
- 21:28Example 5: Encryption protocol
- 26:28Example 6: Language choice
- 30:22Example 7: Social fail
- 31:27Example 8: Business fail
- 35:02Summary
- 36:08Q&A
related talks
59mDesign mistakes in high-load projects
01h 01mBecoming an Engineering Manager Without Losing Your Technical Soul
51mCommon pitfalls in engineering teams and how to avoid them
34mWhy Good Software Goes Bad
42mHow engineering managers can lead with visibility
55mArchitecture Blindspots, Biases, and Blunders: Avoiding Common Pitfalls in System Design
12mSS & BR: 10 pitfalls on the path from engineer to technical manager
41mFeature Flags: A Boon or a Brake for a Team