It’s August and after summer holidays it’s time to get back to monthly notes. If you read only one note, check the “Some important things to keep in mind when you work remotely” which has good tips also in general. Happy reading :)
Issue 51: 2020-08-07
How to gracefully shut down Pods without dropping production traffic in Kubernetes?
If you’ve ever noticed dropped connection after a rolling upgrade, read Daniele Polencic Twitter thread which digs into the details with detailed pictures.
Prevent Info leaks and enable powerful features: COOP and COEP
“Cross-Origin Embedder Policy (COEP) and Cross-Origin Opener Policy (COOP) isolate your origin and enable powerful features.” The video by @agektmr helps you understand how it works and why this is important. Unlock access to new perf API’s to help you identify JS bottlenecks, memory leaks, and more. (from @igrigorik)
Some important things to keep in mind when you work remotely
Check the Twitter thread for 10 great tips for working remotely. They are also good tips also in general. I’ve also found the tip 8. be great. Writing notes and making (public) blog posts of them helps you to process new information better and also help other developers. Documentation is often undervalued and it takes time to do it correctly.
It’s probably time to stop recommending Clean Code
“There is a growing movement against Rob Martin’s books (e.g., Clean Code). After reading the article, I have to agree with a lot of it, but I also hope that this movement doesn’t push too far to the other side.” (from @maybeFrederick) My take is that don’t believe everything you read be it on a book or nowadays in the Internet. Use your own thinking and reasoning. “Clean Code” has good points and suggestions but also goes a bit overboard with how “clean” things should look.
“Boop is a place to paste text, and transform it using basic operations. The goal is to allow quick experimentation and avoid using random websites to do that stuff. It’s super useful when working with logs, JSON data, etc.” (from @OKatBest). This is what I’ve always needed. No more searching for online tool for a specific task (or looking it from tiny-helpers.dev which is a great collection).
Fully embedded bug-tracker in git: you only need your git repository to have a bug tracker.