When I develop new features, I keep forgetting to clean up my code. I'll try out a new workflow or editor, and forget to include all the linters and formatters. Here's how we automatically correct stupid mistakes in CI, even after they've slipped through the cracks on my machine.
Focus on what you can control, never bother with the rest.
Lord Spacington will happily devour your tabs. Lest we forget.
When you migrate a critical data dependency to a new system, how do you know the new system is telling the truth? We recently went through this in Coop's Identity Provider, and this post covers the technique we used to check consistency between the old and new systems during the switchover, and what we learned from it.
Remark: Even though flutter has been the featured framework here, the same solution can easily be recreated in other technologies as there is absolutely no language- or framework-specific code.