How to empower software engineers to act & improve cloud efficiency
summary
FinOps teams face getting engineers to act: a FinOps Foundation survey of 1,000 respondents covering $30B of spend ranks that as the top challenge, and roughly one third of cloud spend is often waste. Practical approach: do homework to find hot spots (example: ASGs running r5.24xlarge -> 4xlarge where metrics show no CPU/memory above 4xlarge), reduce friction with IaC/Terraform or automation, provide representative test environments and feedback loops, and run migrate to Kubernetes pilots—six apps in three months cut spend, sped deployments, and reduced outages.
AI-written summary · about
chapters (5)
- 0:00Intro
- 0:57What is Finops
- 1:49Cloud spend forecasts
- 2:16Separating signal from noise
- 7:05How to provide feedback
related talks
29mFinOps: Principles and cloud cost observability
20mPlatform-First Cloud Transformation
25mFrom Ops to Impact: Scaling Engineering Velocity
47mThe Resource Conscious CTO Building More with Less
32mUnlocking high-velocity engineering through automation, self-service, and Terraform
28mSupport and Tools to Help You Accelerate Toward DevOps
07mFrom Scaling APIs to Scaling Data to Scaling Your Team
44mEnhancing the Performance of Engineering Teams