The Delivery Newsletter #37
#37 JAN. 8, 2019
The Delivery Newsletter

Happy New Year!

Have experience with Bazel? Email me your thoughts!

Bill - Accelerate Delivery founder

The #1 bug predictor is not technical, it's organizational complexity

Organizational complexity predicts bugs in code better than these other common indicators:

  • Test Coverage
  • Code Complexity
  • Code Churn
The post says that the number of contributing developers, or the distance of the developers from decision-makers, increases the likelihood of bugs. I am curious how this applies to small teams. Is organizational structure the best indicator of bugs on a team with one developer and one decision-maker?

Continuous integration and deployment with Bazel

This post presents a high-level approach to monorepos at Dropbox's scale. Dropbox uses Bazel as a dependency graph between services and their tests. A unique facet at Dropbox is that they build and distribute SquashFS artifacts for deployment.

Inversion of Control

Loosely coupled architectures drive continuous delivery. Develop simpler software that is more flexible and easier to maintain by giving up control.

Resource Guide To The Unicorn Project (Part 1)

If you enjoyed reading The Unicorn Project, Gene Kim released a list of supporting reading material. There are dozens of books and links to read if you want more information about digital transformations.

BeyondProd: How Google moved from perimeter-based to cloud-native security

Google released a whitepaper, BeyondProd, which reveals how they moved beyond perimeter-based security. The paper discusses authentication, code provenance, and runtime sandboxing, to name a few protections.

🎥 Videos

CI and CD in Cloud Native (The Podlets, Ep 11)

Three engineers discuss the merits and difficulties of continuous delivery in cloud-native environments. For the most part, "cloud-native" in the context of this video means "runs on kubernetes".