Better Dev Link

A 18K$ bug bounty for a critical Amazon Kindle vulnerability. Leverage mail to kindle feature. brute force the kindle address, spoof the from header, reverse engineer rendering engine for Vulnerability to access to shell code, gain root and own Kindle device. An impressive, smart and creative kindle hack.

Author of OpenLDAP shared their hard-won knowledge about caching. highlight: don’t use LRU, use CLOCK, getting data model right is important.

Just a refresher of some good Postgres tip and trick for you to learn/use this year.

This is the original title of this post but I don’t see how simple it’s at all :-). It’s too complex I must say to use. But I think the author mean simple in term that you can understand it and break it down and even build your own container network with your own hand, use standarize linux command without writing a single line of code. Still a good post to understand how network is setup and configure between containers, you will learn tool like netns for network namespace, nsenter to interact with linux namespaces.

I don’t think we need to do this in 2021. But what is the different between them that affect their performance characteristics.

I’ll introduce databases as an abstract concept and then we’ll work through a real-world example to explore how databases leverage sorting and filters to lookup information quickly. By the end, I hope to show you how these information architecture concepts are immensely powerful and totally approachable for non-technical people.

A recap of using modern feature of browser to replace JavaScript and make your site faster: like scrolling, lazy image loader…

we’ll take a close look at some of the changes we made on this very site — running on JAMStack with React — to optimize the web performance and improve the Core Web Vitals metrics. With some of the mistakes we’ve made, and some of the unexpected changes that helped boost all the metrics across the board.

There are a whole bunch of popular interview questions that can be solved in one of two ways: Either using common data structures and algorithms in a sensible manner, or by using some properties of XOR in a seemingly hard to understand why. While it seems unreasonable to expect the XOR solutions in interviews, it is quite fun to figure out how they work

on every single software project or product I’ve worked on, JSON serialization has been a endless source of pain and bugs. It’s a push stream of trouble. Why is that so? What is so inherently complicated in the problem of JSON serialization that we always, by necessity, struggle with it?