I want to start this week's issue with Milosz Danczak's, "Do Something Different for a Week." Being a technologist means an everchanging world of tools and processes. It's easy to get into habits or lean on "best practices". By creating low risk mini experiments, we can avoid getting too set in our ways.
Most of the articles that follow provide an opportunity for such experiments. Try relying on your tracing tools locally instead of your debugger. Experiments with alternative ways to organize and manage your source control repos. Do some chaos engineering around your service dependencies. You may only learn what not to do, but at least you'll learn something.