Better Dev Link

This article is an attempt at explaining the Git version control system from the bottom up, that is, starting at the most fundamental level moving up from there. This does not sound too easy, and has been attempted multiple times with questionable success. But there’s an easy way: all it takes to understand Git internals is to reimplement Git from scratch.

Whilst this post discusses a choice made in the design of Rust; and uses examples in Rust; the principles discussed here apply to other languages for the most part

Modern computers have the ability to perform multiple operations at the same time. Supported by hardware advancements and smarter operating systems, this feature makes your programs run faster, both in terms of speed of execution and responsiveness.

Real life experience sharing a MySQL fleet. You got to know how they store pins, users, board and comment.

Rewriting the Sharding Layer of Uber’s Schemaless Datastore

Out with the old, in with the new! They broke down API into its key functional areas and then began moving this functionality to brand new components. This allowed them to avoid breaking production code paths and instead reduce the risk whilst they introduced these over time.

An open-ended idea about REST. Instead of model the API in term of resources, we model it after business flow of an action in real life.

Or why you need to normalize Unicode strings

One of the great features of PostgreSQL is Common Table Expressions, or CTEs, otherwise known as “WITH queries”. These are simply chained SQL expressions that allow you to pass the result of one query into another, functional style

How to build a free, privacy-focused alternative to Google Analytics with AWS Lambda and a spreadsheet