Uber Visualization Nights: deck.gl

During the first “Uber Visualization Night” on June 20, 2017, Nicolas Belmonte from Uber’s Data Visualization team gave a nice introduction to the aforementioned deck.gl:

Reflecting On One Very, Very Strange Year At Uber

Susan J. Fowler, whom left Uber after about a year of employment there:

I joined Uber as a site reliability engineer (SRE) back in November 2015, and it was a great time to join as an engineer […] After the first couple of weeks of training, I chose to join the team that worked on my area of expertise, and this is where things started getting weird. On my first official day rotating on the team, my new manager sent me a string of messages over company chat. He was in an open relationship, he said, and his girlfriend was having an easy time finding new partners but he wasn’t. He was trying to stay out of trouble at work, he said, but he couldn’t help getting in trouble, because he was looking for women to have sex with. It was clear that he was trying to get me to have sex with him, and it was so clearly out of line that I immediately took screenshots of these chat messages and reported him to HR.

And that’s just the tip of the iceberg. Unbelievable that this kind of of stuff is still possible. Even worse is that HR neglected all of her complaints, and even protected the offender.

Reflecting On One Very, Very Strange Year At Uber →

Crafting Data-Driven Maps

At Uber, we use maps for everything — visualizing millions of geo data points, monitoring road conditions, and advocating for policy change in cities around the world.

Over the last few years we have experienced immense growth. As a result, we have many teams across the organization producing map visualizations for a wide range of needs. We saw a need to create a unified system to guide the creation of consistent, high-quality, data-driven maps.

Crafting Data-Driven Maps →

Why Uber Engineering Switched from Postgres to MySQL

MySQL_Index_Property_Header_

Postgres served us well in the early days of Uber, but we ran into significant problems scaling Postgres with our growth. In this article, we’ll explore some of the drawbacks we found with Postgres and explain the decision to build Schemaless and other backend services on top of MySQL.

Why Uber Engineering Switched from Postgres to MySQL →

The mailinglist post “Why we lost Uber as a user” that came as a response is also worth a read.