Better Dev Link

Not a question people generally ponder, and seems fairly straightforward. It’s a number, obviously! But the question turns out to be somewhat hard to answer, and for API designers especially, the answer is really important to know!

Michael share with us how he built his first homelab server rack, a genuine post without affiliate links so we know he wasn’t bias.

If you share laptop for home and work, or doing consultant for clients, you probably know the hassle of using different github account. This short guide help you configure just that, to make your life easiser by having git automatically load the right account based on directory.

Solid State Devices using NAND Flash, how they differ from Hard Drives, and how they affect file deletion and recovery

A PID controller is a way to solve problems with the following formulation:

You can change some input to the system, called the process variable You have a sensor which monitors something about the system You want the sensor measurement to be close to some target value, called the set point

The PID controller is a good way to decide what the input to the system should be without knowing anything about the internal workings of the system, except that the change in output is roughly proportional to the input.

lock is a very powerful primitive. We use lock all the time in thread programming with mutex. Postgres offer locks to work as across server, so application can request lock and use the central Postgres server as a coordinator. This small website is like a flash card to review all different locks in Postgres.

Have you ever wake up with an alert and look into Postgres datadir you notice pg_wal is growing massively in size? Read on to learn about why this happens, whether you should be concerned, and what you can do about it.

SQLite default config is optimized for embeded use case, so most people trying it will encounter poor performances and the dreaded SQLITE_BUSY error. However, you can configure SQLite to reach ~8,300 writes / s and ~168,000 read / s concurrently, with 0 errors, on a ~40€ / m commodity virtual server with 4 vCPUs

This is somewhat a very low level. But recently I found I had not enough knowledge to understand networking at a very fundamental level. What exactly happen when we make a request, how the tcp connection is open, how the package is sent. how it picks which ethernet interface to send to? So I decide to google around and found this. I plan to studying these. I think understand just 50% of this is already put you on top 10% of developers.