I feel like the space moves fast, and I need a way to keep up with it better. In an ideal world I would want to see best practices for different tools, and pipelines so I can evaluate them and adopt what makes sense.
- SRE Weekly (https://sreweekly.com/) - Curation newsletter on interesting links in SRE
- SRE Prodcast (https://sre.google/prodcast/) - Good podcast by Google on SRE. They pick a specific topic and then interview an expert on that so each episode is well focused. They also provide transcripts so you can just read through it instead of listening.
- Resilience in Action (https://podcasts.apple.com/us/podcast/resilience-in-action/i...) - Another good podcast on SRE with interviews.
If you just want a listen of resources, then you should check out the Awesome SRE repo on github - https://github.com/dastergon/awesome-sre
I propose 2 young YT channels that worth watching about reliability and observability
- Slight Reliability (https://www.youtube.com/c/SlightReliability) Podcast from Stephen TOWNSHEND
- Is it Observable (https://www.youtube.com/c/IsitObservable) from Henrik REXED
In the Operations space my favorite writer is Charity Majors, although a lot of what she talks about isn't OPs specific:
Rachel by the Bay is also great:
Totally not related, but Phil Eaton's posts on how databases work are super interesting and lack fluff.
In terms of CI and builds, I try to write some on this topic for the Earthly Blog. My Bazel article was recently on Hn. Here are my posts:
https://earthly.dev/blog/authors/adam/
Warning though, I also write about lots of other stuff. Are there specific CI topics you'd like to see covered?
That is a good read thank you.
- DevOpsLinks (CI/CD, Cloud Computing, SRE, DevOps): https://faun.dev/newsletter/devopslinks
- The Chief I/O (Distributed Systems, Kubernetes, Cloud Native DevOps): https://faun.dev/newsletter/the-chief-io
Disclaimer: I'm the founder.
https://semaphoreci.com/category/engineering
We also have a podcast about engineering that frequently touches CI/CD as a topic:
Disclaimer: I work for Wise
If not, which is what the diagram implies, how do you handle two branches with two PRs trying to get merged in, since there is a chance that they will create conflicts with each other. Do you force branch tests sequentially?
This is a bit of a pain in busy repos
Even just a maintained “start to finish” of what someone thinks is current best practice for project development would be a fantastic resource.
Or Docker images have K, L problems that Podman doesn't have. However Podman has W issue so you have to decide which pain you want to live with.
That kind of stuff.
(Source: I am a Thoughtworker since 2006).
Martin's articles are freely available and are referenced by practitioners around the world.
I've never come across any of these articles, even though I quiet often came upon his programming articles.
Sorry for my ignorance.