Better Dev Link

Testing in production is a superpower. It’s our inability to acknowledge it that’s the trouble.

It’s been said that we don’t really understand a system until we understand how it fails. These puzzlers assume some basic knowledge about working with TCP on Unix-like systems, but you don’t have to have mastered any of this before diving in/

I always love real world practice/tuning instead of silly benchmark. Squarespace see many errors and warnings were related to database operations: connection timeouts, high query response latencies, etc. This blog post is a summary of the work they did to improve our data layer performance and reduce errors and warnings coming from the database.

Before you rage quit or call in your DBA, check these things aren’t slowing things down. A few tweaks could be all you need to get things moving again.

This post describes the challenges while working with such high notification volumes, and the solutions we developed to solve them

What documentation options do we have that can express the whole application building blocks and how it works?!

we look at four design patterns that can be used for distributed apps and microservices: CQRS, Two-Phase Commit, Saga and Sidecar.

How to write an application that do certain things(instead of spin up a shell and let they do anything) via SSH.

You need a SAT solver when defining your dependencies such as python requirement.txt, node package json or rubygem.

Adding garbage collection to our non-garbage collector: wait, what?