Who would benefit from watching this presentation?

This presentation is ideal for infrastructure engineers, DevOps practitioners, and architects who are involved in writing, maintaining, or scaling infrastructure-as-code. It is particularly useful for those managing large or complex infrastructure projects.

How does this presentation's advice differ from typical infrastructure-as-code best practices?

The presentation offers insights derived from a very specific, large-scale, production-hardened codebase of 300,000 lines, providing a more empirical and practical perspective than general best practice guides. It focuses on lessons learned from real-world challenges encountered over many years.

When should I apply the lessons from this presentation?

These lessons are most applicable when designing new infrastructure systems, refactoring existing large-scale infrastructure codebases, or when encountering challenges in maintaining the scalability and reliability of your infrastructure-as-code. It helps in anticipating future complexities.

What is a key technical takeaway for managing large infrastructure codebases from this talk?

A key technical takeaway emphasizes the importance of treating infrastructure code like application code, advocating for robust testing strategies, clear modularization, and version control practices to ensure maintainability and reliability over extensive codebases.

hashicorp.com · 31 DEC '21

5 Lessons Learned From Writing Over 300,000 Lines of Infrastructure Code

Item: 5 Lessons Learned From Writing Over 300,000 Lines of Infrastructure Code
Rating: 5
Author: Simon Frey

This presentation offers valuable insights from Yevgeniy Brikman on managing large-scale infrastructure-as-code projects. I found the practical lessons on developing and maintaining substantial infrastructure libraries particularly relevant.

Visit hashicorp.com →

Questions & Answers

What is "5 Lessons Learned From Writing Over 300,000 Lines of Infrastructure Code"?: This resource is a presentation by Yevgeniy (Jim) Brikman from HashiCorp that outlines key lessons derived from developing and maintaining a library of over 300,000 lines of infrastructure code at Gruntwork. It serves as a masterclass on effective infrastructure coding practices.
Who would benefit from watching this presentation?: This presentation is ideal for infrastructure engineers, DevOps practitioners, and architects who are involved in writing, maintaining, or scaling infrastructure-as-code. It is particularly useful for those managing large or complex infrastructure projects.
How does this presentation's advice differ from typical infrastructure-as-code best practices?: The presentation offers insights derived from a very specific, large-scale, production-hardened codebase of 300,000 lines, providing a more empirical and practical perspective than general best practice guides. It focuses on lessons learned from real-world challenges encountered over many years.
When should I apply the lessons from this presentation?: These lessons are most applicable when designing new infrastructure systems, refactoring existing large-scale infrastructure codebases, or when encountering challenges in maintaining the scalability and reliability of your infrastructure-as-code. It helps in anticipating future complexities.
What is a key technical takeaway for managing large infrastructure codebases from this talk?: A key technical takeaway emphasizes the importance of treating infrastructure code like application code, advocating for robust testing strategies, clear modularization, and version control practices to ensure maintainability and reliability over extensive codebases.