Understanding 'X as Code': A Clarification by Mitchell Hashimoto
Mitchell Hashimoto clarifies his interpretation of the term "X as Code," which he defines as a "system of principles or rules," rather than the common view of it as merely programming. His aim is to transfer knowledge from individuals into a structured format that can be shared and improved upon. While he acknowledges that codified knowledge is often computer-readable, he emphasizes that this does not mean all programming requirements apply to "as code" systems. Hashimoto also reflects on his past contributions, particularly to Terraform and the Tao of HashiCorp, and stresses that his intent should not be seen as criticism of programming ideals or a definitive definition of "as code."
What does "X as Code" mean according to Mitchell Hashimoto?
"X as Code" refers to a system of principles or rules meant to codify knowledge and processes, rather than simply being a reference to programming.
Why does Hashimoto feel the need to clarify his intent with "as code"?
He often faces misunderstandings about his interpretation of "as code," especially due to his association with Terraform, and wants to ensure his perspective is accurately communicated.
Is Hashimoto critical of the programming aspect of "as code"?
No, he clarifies that he does not intend to criticize the programming ideals or claim that "as code" is perfect; he simply wishes to express his historical intent behind the term.