<story><title>A PostgreSQL response to Uber [pdf]</title><url>http://thebuild.com/presentations/uber-perconalive-2017.pdf</url></story><parent_chain></parent_chain><comment><author>lucasmullens</author><text>Title should be changed to &amp;quot;A PostgreSQL consultancy&amp;#x27;s response to Uber [pdf]&amp;quot;. Many people in this thread, including myself, assumed this was an official response by PostgreSQL.</text></comment>
<story><title>A PostgreSQL response to Uber [pdf]</title><url>http://thebuild.com/presentations/uber-perconalive-2017.pdf</url></story><parent_chain></parent_chain><comment><author>mamurphy</author><text>The use of graphics in this PDF&amp;#x2F;slideshow was incredibly effective, more so than most articles I read.&lt;p&gt;The PDF lays out Uber&amp;#x27;s statements, and either lay it over a real-world analogy (a road on a sinkhole for database corruption) or lay it over a picture that primes their response (like a picture of apples and oranges when they plan to respond that Uber is comparing different features of mysql to postgresql).&lt;p&gt;The use of the elephant picture to give &amp;quot;elefacts&amp;quot; (sort of a parody on politifacts, where they evaluate the truth of uber&amp;#x27;s statements) is also great.&lt;p&gt;The images add humor and reinforce the content - great use of graphics!</text></comment>