AWS CDK dos and don'ts with Matthew Bonig

[@mikeyinger4204]

At 50:00 into the talk Projgen(?) is talked about. Can you provide a link to it.

[@theburningmonk]

Good shout. I've added it to the video description. The link is here: github.com/projen/projen

[@davemeech]

Oh man, so many fantastic takeaways. I've not seen any other source on KZbin describe what kinds of tests are appropriate for different scenarios let alone provide rationale and the underlying context. I'd be interested in knowing what, if anything with cloud infrastructure can or should be done using TDD? Is there a recommended model for representing acceptance criteria for the work such that they can be translated into BDD style given when then tests that can be written in advance of the implementation?

[@theburningmonk]

I have my own views on this, but I'll let @MatthewBonig chime in with his take on it first

[@davemeech]

Hey there! I just remembered this conversation and wanted to follow up.

[@kristopherbowles1625]

​@@theburningmonkwondering if you still had thoughts here

[@MuratKeremOzcan]

Snapshot tests made sense, until temporary stacks with cdk

[@MatthewBonig]

Temporary stacks? I'm not familiar with those...

[@MuratKeremOzcan]

Yan has a blog post about it Tried to link that, my GitHub repo with cdk example, and a video on my channel explaining it, but KZbin hates links and seems to be removing comments.

[@theburningmonk]

Temporary stacks as in, temporary/ephemeral environments you create for the duration of a feature work kzbin.info/www/bejne/gICTkqWml9Cba9k In most tools, an environment is loosely mapped to a stack, for CDK, it's more or less mapped to a CDK app.