Several aspects:
⢠While I would love for all engineers to understand a bit about cloud infrastructure, I keep encountering people that are good at their particular jobs (e.g. payment logic, data science, deep-learning, ...) and generally just want to write code in a single language. It is doable to set up some blueprints and let their CI build their own infrastructure in their team accounts and require limited "hand-holding". I doubt they would be happy to have their code "polluted" by infrastructure details they do not care about.
⢠Infrastructure often relies on specific security hardening needs, connectivity to certain sites, delegation of permissions between systems, passing of ARNs, ... and a lot of those things can be nicely wrapped in e.g. CDK constructs. I would expect the same level of abstraction and sharing of custom modules to be present in an "IfC" tool.
⢠With mature tools come mature 3rd-party tools, such as "IaC-to-diagram", linters, vulnerability-scanners, ... and that is still lacking for something this niche