Move Fast, Think Big
summary
Focus on delivering only what actually lands in production, using quarterly plans plus OKRs over ad hoc sprint churn, and cut work that repeatedly stalls or lives in dormant branches. Design data systems from requirements (latency, SLA, regulations, upstream/downstream use), prefer battle‑tested platforms to reinventing infrastructure, and track TCO not sticker price. Certify teams on cloud patterns (AWS/GCP/Azure), adopt managed services (AWS Kinesis/Athena/Glue, S3, RDS; Confluent, Spark/Flink, Airflow) and enforce CI/CD, separated envs, monitoring and disaster recovery.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:24Boazs background
- 2:28Development management
- 3:17How in general
- 4:26Agenda
- 5:15Focus
- 5:56Identifying a Focus Problem
- 8:31Scrum
- 10:30Roadmap
- 14:06Quarter
- 21:31Unique Requirements
- 23:56AWS Architectures
- 25:32Starting from the beginning
- 25:49Data engineering evolution
- 26:31Leveraging platforms
- 28:07Example flank 546
- 28:27Platform
- 29:56Cost
- 30:06Cost of Ownership
- 31:08Other Considerations
- 33:14How do you make sure you got the right thing
- 34:43Is there a difference between managing fullstack application or web development
- 36:10Tools for CICD
- 37:08Disaster Recovery
- 38:30Choosing a Platform
- 40:02An Endless Cycle
- 42:37QA
