Putting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.

For those who want to understand color spaces, transform videos from one color space to another, or read how I almost went crazy working out why my Canva-generated videos looked slightly off, color-wise

iMessage is slow and clunky when searching message. At the end, it’s just text store in a SQLIte database. If we can reverse engineer it, we can yield better search result

A very detail write up on how to generate enough power for the OP usage on his equipment. Fun experiment and I think it feeling great when knowing the blog is powered by Solar energy :)

In this post we’re going to focus on the ways that a single load balancer might distribute HTTP requests to a set of servers. We’ll start from the bottom and work our way up to modern load balancing algorithms.

Someone asked if I could write about the rise of AI and Large Language Models (LLMs) and what I think that means for the future of people, technology, society, and so on. Although that’s a fun topic, it left me with two problems: I know approximately nothing about AI, and predicting the future is hard even for people who know what they’re talking about. Instead, I’ll tell you a bunch of things I do know that are somehow related to the topic, and then you can predict the future yourself.

Slack is a very complicated system with complicated rule. Mute channel, when to send notification, where(email or device), did user see this notification in email already? Debugging notification is complicated at Slack scale, so they build a system to trace the notification across the system.

Challenge of Microservice is they call each others, one client request turns into many internal RPC call, and amplify the failure rate when making these requests due to nature of network. Retrying is often use, but if the service is completeley failed, how can we skip it immediately. This is DoorDash strategy for that

help beginners understand and set up server replication in PostgreSQL using failover and failback. Postgres evolve fast and process to setup Postgres replication is way simpler than in Postgres 10 or 12 for example.

Storing time ranges in a database is easy, but you must also prevent overlapping rows for some applications. Accomplishing this requirement can be challenging because of race conditions.

A tip to monitor the progress of certain operations in PostgreSQL? Yes, we can monitor the progress of these operations in PostgreSQL: index creation, re-index, vacuum, and more