Sometimes you have to re-evaluate decisions you made 5 years (or 5 months!) ago in your codebase

[00:00] reasons why we should like write [00:01] automated tests to some degree is for [00:04] ourselves so we can get it out of our [00:06] head. We can document our requirements [00:07] and but also sometimes we need to expose [00:10] ourselves to bad things happening [00:13] because that's how we learn to do things [00:15] and come up with better solutions on how [00:16] to manage these things. Maybe some of [00:18] the decisions on how to some of those [00:20] guardrails that we had made five years [00:22] ago were the best ideas we had at the [00:24] time. There might be new ways of dealing [00:25] with those types of guardrails now. [00:26] Maybe we don't need to have this really [00:29] laborious human workflow because now [00:32] there's some instrumentation or [00:33] observability or some AI assisted [00:35] tooling that could help us reheal things [00:37] a little bit quicker. Now, wouldn't it [00:39] be amazing if a deploy took always like [00:42] less than 3 minutes, less than versus 30 [00:44] minutes