MrTechCurious @MrTechCurious

The actual problem: dev teams rarely audit deep dependency trees. Importing third-party packages for tiny tasks creates single points of failure you don't even know exist in your stack.

To stop the global blackout, npm broke its own policy. They forcibly un-deleted left-pad and handed it to a new maintainer. It was the first time npm overrode an author's deletion rights on their platform.

In March 2016, Facebook, Netflix, and Spotify suddenly failed to build. The cause? One developer deleted an 11-line code package over a naming dispute. Here is how modern code dependencies made the web this fragile: 🧵

Next, your browser asks your operating system. Windows, macOS and Linux all keep their own DNS cache. Think of it as a small address book. If the address isn’t there either… Your computer has to ask someone else.

So where does your browser look first? Surprisingly… It asks itself. “Do I already know this address?” If you’ve visited Google recently, your browser may already have the answer stored in memory. If it doesn’t… The real search begins.

Your browser has absolutely no idea where Google is. Seriously. The internet doesn’t understand names like google.com. It only understands numbers So every time you visit a website, your browser has to find its address before it can even ask for the page. How? 🧵

That’s exactly why file recovery software sometimes works. It isn’t performing magic. It’s looking for data that’s still physically present even though the operating system has stopped keeping track of it. No map doesn’t always mean no data.

The actual photos, videos or documents can remain on the storage device for quite a while. They only disappear when the operating system needs that space for something new and writes fresh data over it. Until then, the old data may still be sitting there.

You delete a photo. Empty the Recycle Bin. It’s gone… Right? Not exactly. In many cases, your computer didn’t erase the photo at all. It simply pretended it no longer existed. Let’s investigate. 🧵

So where did your battery go? Nowhere. The battery is still there. What’s disappeared is its ability to store and deliver energy efficiently. Your phone didn’t wake up one day and decide to have a bad battery. Chemistry has been quietly rewriting it since the day it was made

Eventually, the battery reaches a point where it simply can’t store enough energy to keep up with the phone’s demands. That’s when you notice the changes. It dies faster. It charges more often. Sometimes it even shuts down unexpectedly. The ageing has finally become visible.

Your phone was brand new. You charged it in the morning and forgot about it until night. Now, two years later, you’re carrying a power bank everywhere. Same phone. Same battery. So… where did the battery go? 🧵