Better Dev Link

Understanding of the internal mechanism is crucial for both administration and integration. This free book has 11 chapers of process and memory, query processing, vacuum, Heap Only Tuple (HOT), Index-Only Scans, Write Ahead Logging, Point-In-Time Recovery…

A free book give you a thorough introduction to competitive programming. It covers a handful algorithm of sorting, search, data structure, time complexity and graph.

These are super tricky mathematical problem. They also include solution. I don’t know where I can applied these knowledge yet but it’s interesting to read.

To understand memory leaks, we need to identify them. The author divide into three broad categories, provide tools and techniques for figuring out both which type we’re dealing with, and how to find the leak.

Figma rewrite multiplayer server in Rust. They explains the issue with NodeJS single threaded: a single slow operation would lock up the entire worker until it was complete. The Rust backend is 10x faster, 3.8x smaller in term of memory.

Everyone uses %CPU to measure performance, but everyone is wrong, says Netflix’s Brendan Gregg in his UpSCALE Lightning Talk.

Even you don’t use or need C now, some knowledge on it can be very valuable.

With the recent incident from Github and Twitter for a bug that log password in plaintext, how can we implement a process to log securely? This is in Go but you can extract the technique.

Learn what Python bytecode is, how Python uses it to execute your code. What is in a .pyc file? and look into Python virtual machine.