This could be the equivalent of the in famous “what happen when you type an address into the browser”, but for terminal which we interact on a daily basis but may forgot or not having a full understand of its architecture.

hexdump is very versatile and allows you to look at the structure inside binary files as you see fit and once you learn how to use it you can apply it quickly to many problems. I think that easily qualifies as cool.

We keep hearing floating point issue and their issue but at a higher or abstraction level. Are there any specific examples that we can practical see how bad it’s

Third article in a series of blog posts about rsync. This posts is about data transfering, split and checksum multi part of the files.

In this post I’ll attempt the fun stunt of designing a system that could serve the full production load of Twitter with most of the features intact on a single (very powerful) machine. I’ll start by showing off a Rust prototype of the core tweet distribution data structure handling 35x full load by fitting the hot set in RAM and parallelizing with atomics, and then do math around how modern high-performance storage and networking might let you serve a close-to-fully-featured Twitter on one machine.

Cross origin request? What is that? Why loading an image work, including a JS from other domain works? but make ajax request won’t or cookie won’t get send? What are all the terms?

Have you ever write this kind of code? copy(from_path, to_path) and accidentally paste the argument in reverse? If we use type we can avoid that? Or even typo, especially when using enum type.

NodeJS/JavaScript runtime run like a giant for loop and check for thing to do, these thing can in turn queue other things. What happen if they throw promise error which we forgot to handle? When that happen the execution halt in node or throw error in browser and stop the execution of JS right there, no more further JS after that point in your code get run. The point is, you want to avoid unhandled rejections.

This article is about configuring a web application, Appsmith in this case, to run correctly behind a firewall that does SSL decryption, as a Docker container. Instead of a firewall, we’ll use a proxy, which, for the purpose of the problem statement, should be the same. We usually don’t include these kind of “how-to” tutorial, but I feel like it helps a lot when debugging or reversing API traffic and that’s a really powerful tool to have in your toolbox