The anatomy of a perfect pull request

#267 – June 10, 2018

this week's favorite

The anatomy of a perfect pull request

Writing clean code is just one of the many factors to care about when creating a pull request. Large pull requests cause a big overhead during the code review and facilitate bugs introduction in the codebase.   That's why you need to care about the pull request itself. It should be short, must have a good title and description and should do just one thing.

Mainframe on the Macbook

The first challenge when trying to teach yourself COBOL is figuring out how to install a language designed for mainframes on a modern machine. It could not be as easy as brew install cobol could it?

Why Uber Engineering Switched from Postgres to MySQL

The early architecture of Uber consisted of a monolithic backend application written in Python that used Postgres for data persistence. Since that time, the architecture of Uber has changed significantly, to a model of microservices and new data platforms. Specifically, in many of the cases where we previously used Postgres, we now use Schemaless, a novel database sharding layer built on top of MySQL. 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.

CSS Is So Overpowered It Can Deanonymize Facebook Users

Some of the recent additions to the Cascading Style Sheets (CSS) web standard are so powerful that a security researcher has abused them to deanonymize visitors to a demo site and reveal their Facebook usernames, avatars, and if they liked a particular web page of Facebook.

A cartoon intro to DNS over HTTPS

Threats to users’ privacy and security are growing. At Mozilla, we closely track these threats. We believe we have a duty to do everything we can to protect Firefox users and their data.

newsletters