12 Debugging tools I wish I knew earlier 
– it describes more debugging strategies than debugging tools (i.e. minimal reproduction is not a tool). One strategy I missed in this post is adding breakpoints. If I were to write this post, I would order it in an escalation order. For example, reading the error message would be in a higher place. However, it is an important post, especially for junior developers.
https://careercutler.substack.com/p/12-debugging-tools-i-wish-i-knew
Consistency Patterns – This post explains the different common consistency patterns – strong, eventual consistency, and weak consistency and the trade-offs. It also mentions the idea of causal consistency, which I find very interesting.
https://systemdesign.one/consistency-patterns/
Remote work requires communicating more, less frequently – he had me at “Think of it like gzip compression, but for human-to-human communication. Yes, there’s slightly more processing overhead at the start, but it allows greater communications throughput using fewer “packets” (communicate more using less)”. Seriously, once your organization grows above ten people and you start having clients, you will have people remote (colleagues or clients), and you will have to optimize your communication to pass your message.
https://ben.balter.com/2023/08/04/remote-work-communicate-more-with-less/
Git log customization – I’m setting a new computer now for development and looking for a format that would be easy for me to use so this post came exactly on time
https://www.justinjoyce.dev/customizing-git-log-format/
Structuring your Infrastructure as Code – I like the layers approach of this post and the examples from all 3 public cloud providers. I would like to give more thought to the exact layers and order. Note that this post is written by Pulumi, a solution engineer, so it might not work well with other IaC tools.
Tom Ron 