Helping To Build Cloudflare, Part 3: Audacity, Diversity and Change

In this blog post, John Graham-Cumming discusses the evolution of Cloudflare after the Cloudbleed incident. He highlights how they moved away from memory-unsafe languages like C and C++ to more secure ones such as Go and Rust. The author also talks about the successful launch of their public DNS resolver, 1.1.1.1, which was a result of audacity, good relationships with various groups around the world, and a diverse workforce. Graham-Cumming emphasizes the importance of having a simple architecture that can scale easily and be updated quickly. He also discusses how rewrites are necessary as software use grows exponentially, making it difficult to anticipate future needs accurately. The post concludes with an overview of his role as Cloudflare's CTO and the various challenges he has faced while working there.