RRashindu TharindaJun 2 · 6 min readVariables and Memory: What a Variable Actually IsEvery beginner thinks a variable is a box that holds a value. That model is comfortable, intuitive, and wrong in ways that will eventually cost you hours. The Name Is Not the Value Here is a better mrash522.hashnode.dev
RRashindu TharindaMay 26 · 7 min readFrom Code to Execution: How a Program Actually RunsYou have written thousands of lines of code. You have never once told a CPU what to do. What you have done is write instructions for a translator. Several translators, actually, stacked on top of eachrash522.hashnode.dev
RRashindu TharindaMay 19 · 6 min readYour code never actually touches the hardwareEvery line of Python, Go, or C you write runs inside a box. A carefully constructed, permission-enforced box. The hardware underneath, the disk, the network card, the RAM, none of it is yours to accesrash522.hashnode.dev
RRashindu TharindaMay 12 · 7 min readStorage: How Data Persists and Why Durability Is Not FreeEvery time your database survives a power cut, someone made a deliberate engineering decision to pay for that survival. That payment is not always money. Sometimes it is latency. Sometimes it is complrash522.hashnode.dev
RRashindu TharindaMay 5 · 6 min readHow RAM Works: Volatile Memory and Why It MattersYour program crashes, your machine survives. That is RAM doing exactly what it was designed to do. The Workbench, Not the Filing Cabinet Think of your computer's storage as a filing cabinet: everythinrash522.hashnode.dev
RRashindu TharindaApr 28 · 6 min readCache Memory: The Layer That Makes Modern Computing PossibleYour CPU can perform billions of operations per second. Without cache, it would spend most of that time waiting. That is not an exaggeration. A modern CPU can execute an instruction in under a nanosecrash522.hashnode.dev
RRashindu TharindaApr 22 · 7 min readMemory: From Registers to SSDs, Why the Hierarchy ExistsYour program runs ten times faster on some days than others. You changed nothing. The difference is almost always memory. The Workspace Analogy Picture a carpenter. On the workbench in front of them:rash522.hashnode.dev
RRashindu TharindaApr 11 · 6 min readHow a CPU Works: The Engine Underneath Every ProgramEvery line of code you have ever written eventually becomes a sequence of instructions a piece of silicon executes one at a time, billions of times per second, and most engineers have no idea what tharash522.hashnode.dev
RRashindu TharindaApr 8 · 5 min readBinary and Number Systems: Why Computers Think in 0s and 1sEvery number you have ever typed into a computer was silently converted into something unrecognizable before anything happened with it. The Switch That Started Everything Picture a row of eight lightrash522.hashnode.dev
RRashindu TharindaApr 6 · 7 min readMental Models for Engineers: How Experienced Developers Actually ThinkEvery senior engineer you admire is not smarter than you. They just carry a set of lenses they reach for automatically, and nobody told you the lenses existed. That gap, between the engineer who starerash522.hashnode.dev
