Sumon Dey shared a short and informative guide on what software tools and technologies you should focus on to become a better Software Development Engineer in Test.
Furthermore, Joe Colantonio wrote a decent piece on what is an SDET.
Frequent deployments to production with an easy rollback feature are a huge boost to the team's productivity. But it will only work when it's well prepared, as explained by Kristin Jackvony.
I found it interesting how BlaBlaCar sorted out their QA process to test their apps more effectively. By Clovis Bernier.
I'm surprised how accurately Chris NeJame described the typical "waterfall in an Agile sprint" process and the challenges it generates for testers and teams in general, followed by a simulation demonstrating why it's so complicated. Great read!
The smoke, sanity and regression testing types might be confusing so this concise explanation by Przemysław Paczoski can help in understanding what they really are and when and how to use them.
It then dawned on me that in the era of true CI/CD (CD being continuous deployment), that the old approach of making sure there are zero bugs before release is not going to work and is in fact redundant.
I agree with Heemeng Foo on the power of Observability that can help testers and teams ship, learn and fix faster.