<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Conway's Law on Brave New Geek</title><link>https://bravenewgeek.com/tag/conways-law/</link><description>Recent content in Conway's Law on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 18 Jul 2018 10:01:34 -0500</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/conways-law/index.xml" rel="self" type="application/rss+xml"/><item><title>GCP and AWS: What’s the Difference?</title><link>https://bravenewgeek.com/gcp-and-aws-whats-the-difference/</link><pubDate>Tue, 17 Jul 2018 11:58:21 -0500</pubDate><guid>https://bravenewgeek.com/gcp-and-aws-whats-the-difference/</guid><description>&lt;p&gt;AWS has long been leading the charge when it comes to public cloud providers. I believe this is largely attributed to &lt;a href="https://gist.github.com/chitchcock/1281611"&gt;Bezos’ mandate of “APIs everywhere”&lt;/a&gt; in the early days of Amazon, which in turn allowed them to be one of the first major players in the space. Google, on the other hand, has a very different DNA. In contrast to Amazon’s laser-focused product mindset, their approach to cloud has broadly been to spin out services based on internal systems backing Google’s core business. When put in the context of the very different leadership styles and cultures of the two companies, this actually starts to make a lot of sense. But which approach is better, and what does this mean for those trying to settle on a cloud provider?&lt;/p&gt;</description></item></channel></rss>