I don’t view this ratio as a better/worse thing. Config as code it a good practice already, and once you have that, it’s moving complexity, not creating it.https://twitter.com/springrod/status/1002379190174302208 …
One of the big issues I have with the current setup is your infra dependency graph is prob already split between code and config. Example: dynamo streams -> lambda -> SNS chain. That second edge is expressed in the lambda code. The first one is in CF.
-
-
A tool that unifies application and infra code could understand that. I don't think it exists, but it feels possible.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.