To give this a slightly different spin: --> "The best optimization is simply not spinning things up!" At least for local development and testing, as made poss

To give this a slightly different spin: --> "The best optimization is simply not spinning things up!" At least for local development and testing, as made possible by LocalStack (https://localstack.cloud https://localstack.cloud), among other local testing solutions and emulators. We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS". What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place...