Code Quality and Infrastructure as Code
summary
Explains that Infrastructure as Code prevents environmental drift by declaring resources (examples: Pulumi with C# emitting AMIs, JSON/YAML CloudFormation, AWS CDK) and recommends a reusable golden construct per component plus audits and governance. Advocates automated testing strategies: unit and post-deploy integration tests, plus a UI smoke that added about 15–20 minute smoke test to biweekly releases. Recommends static analysis (SonarQube, editorconfig) and treating IaC with the same rigor as application code.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:02Definition
- 4:12Environmental Drift
- 9:21What is Code Quality?
- 12:10What Does Code Quality Affect?
- 13:58Footprint of effect
- 17:16Complexity of testing
- 20:00Arguments Against it Being Different
- 21:59Additional Considerations
- 23:18Audits and Governance
- 26:18Automated Testing
- 28:18Code Quality Tools
related talks
46mImplementing Infrastructure as Code
28mFrom Infrastructure as Code to Environment as Code: Challenges scaling IaC
28mInfrastructure as Code in the Real World
42mInfrastructure as Code - Lessons learned from Dev to Ops
36mInfrastructure as Code Done Right: Discovering and Fixing Common Missteps
34mIaC – Improving and Securing Infrastructure Provisioning in the Cloud
19mInfrastructure as Code: A Must Know Skill for Today's Developers
21mPitfalls of Infrastructure as Code (And how to avoid them!)