AWS CDK dos and don'ts with Matthew Bonig

Поділитися
Вставка
  • Опубліковано 8 лис 2024

КОМЕНТАРІ • 10

  • @davemeech
    @davemeech 11 місяців тому +2

    Oh man, so many fantastic takeaways. I've not seen any other source on UA-cam 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
      @theburningmonk  11 місяців тому

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

    • @davemeech
      @davemeech 11 місяців тому +1

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

    • @kristopherbowles1625
      @kristopherbowles1625 3 місяці тому

      ​@@theburningmonkwondering if you still had thoughts here

  • @mikeyinger4204
    @mikeyinger4204 Рік тому +1

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

    • @theburningmonk
      @theburningmonk  Рік тому

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

  • @MuratKeremOzcan
    @MuratKeremOzcan Рік тому +1

    Snapshot tests made sense, until temporary stacks with cdk

    • @MatthewBonig
      @MatthewBonig Рік тому

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

    • @MuratKeremOzcan
      @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 UA-cam hates links and seems to be removing comments.

    • @theburningmonk
      @theburningmonk  Рік тому

      Temporary stacks as in, temporary/ephemeral environments you create for the duration of a feature work ua-cam.com/video/JO0arpbkh5w/v-deo.html
      In most tools, an environment is loosely mapped to a stack, for CDK, it's more or less mapped to a CDK app.