It's the same with TDD, in that thinking about tests up front is a design tool that shapes how you think about your systems before writing that first conditional statement. The value is in the thought process, not the artefact it produces.

I think that gets lost when we automate these away entirely. We lose the frameworks that help us understand our systems

Thanks for writing this
While the thought of automated incident response is super appealing, especially during those 3am pages, it's important to remember that processes like incident response, specifically retrospectives like postmortems, are intended to facilitate human thinking and learning.

I couldn't fit it all in. But I'm excited. It's the Pleias 1.0 models.

What if it could test its guesses? Clone the production environment, confirm the issue, try a rollback or fix forward, and validate automatically.

Looks good 👀
Thanks for the suggestion. I've never had a problem with Pipenv, but I'll take a look.

I completely agree with you, Joel. I also really like the idea of starter packs. It helps newbies get set up quickly and follow communities that have been built up over many years on the platform we dare not speak. Mastodon may seem like a scary jump-off point.

… and change one variable to make it look original 😝