You can't be in the backseat when using those tools. Otherwise you might feel productive by cranking out code but it can't do the essential tasks for you (most notably actual problem solving or architecture thinking). The quality would clearly suffer.

Another way to approach Architecture Decision Records. A different format to try to foster a more collaborative approach.

Friendly reminder that in C++ that case evolved quite a bit all the way to C++23. Please use the more recent constructs in new code. This definitely leads to better patterns.

A quick summary of the different properties you want in tests. In practice you'll likely have to find a tradeoff among them.

Apparently this needs pointing out but there's more than async/await out there. Sometimes what you want is a simple event loop. Here illustrated in the Rust ecosystem.