<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Study on Muhammad Nuh</title><link>https://hexrogue.github.io/tags/study/</link><description>Recent content in Study on Muhammad Nuh</description><generator>Hugo</generator><language>en-us</language><managingEditor>ikanlemas0@gmail.com (Muhammad Nuh)</managingEditor><webMaster>ikanlemas0@gmail.com (Muhammad Nuh)</webMaster><lastBuildDate>Tue, 11 Oct 2022 00:00:00 +0800</lastBuildDate><atom:link href="https://hexrogue.github.io/tags/study/index.xml" rel="self" type="application/rss+xml"/><item><title>OOP Clicked When I Stopped Memorizing</title><link>https://hexrogue.github.io/blog/oop-clicked-kitchen-version/</link><pubDate>Tue, 11 Oct 2022 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/oop-clicked-kitchen-version/</guid><description>&lt;p&gt;Object oriented programming confused me exactly as long as I tried to memorize definitions. Encapsulation, inheritance, polymorphism. Words to chant before exams, and also the name of a band that would never get a record deal. Then someone explained it with a kitchen, and it clicked in a minute. Passing that on.&lt;/p&gt;&#10;&lt;h2 id="classes-are-cookie-cutters-objects-are-cookies"&gt;Classes are cookie cutters, objects are cookies&lt;/h2&gt;&#10;&lt;p&gt;A class is a blueprint. It describes what a thing has (data) and what it can do (methods), but it is not the thing. An object is one actual thing stamped from the blueprint. One User class, thousands of user objects. The cutter is not a cookie. Say it with me.&lt;/p&gt;</description></item><item><title>How Your CPU Reads Code</title><link>https://hexrogue.github.io/blog/cpu-how-it-reads-code/</link><pubDate>Tue, 21 Sep 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/cpu-how-it-reads-code/</guid><description>&lt;p&gt;Computer organization sounded dry until week two, when I realized it answers the best question in computing: how do words I type become electricity doing math. My notebook version, short enough to read without a degree and long enough to sound smart at a dinner party you were not invited to:&lt;/p&gt;&#10;&lt;h2 id="everything-is-switches"&gt;Everything is switches&lt;/h2&gt;&#10;&lt;p&gt;A CPU understands exactly two things: on and off. Every photo, song, and game is patterns of ons and offs, ones and zeros. Eight of them make a byte, enough for one character. Billions of them make everything else. It feels absurd until you realize all of human language is also just patterns of a few dozen sounds. Same trick, different medium.&lt;/p&gt;</description></item><item><title>What an Operating System Actually Does</title><link>https://hexrogue.github.io/blog/os-what-it-actually-does/</link><pubDate>Tue, 03 Aug 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/os-what-it-actually-does/</guid><description>&lt;p&gt;I am taking operating systems this semester, and the textbook reads like it was written by the scheduler itself: efficient, joyless, technically correct. So these are my notes, translated into human. Same facts, fewer footnotes, one joke per page.&lt;/p&gt;&#10;&lt;h2 id="your-os-is-a-middle-manager"&gt;Your OS is a middle manager&lt;/h2&gt;&#10;&lt;p&gt;Every program on your computer believes it owns the machine. Chrome thinks the CPU is its CPU. Your game thinks the memory is its memory. Both are wrong. The operating system sits between lying programs and finite hardware, handing out slices of CPU time so fast that everyone believes the lie. That illusion is the entire job.&lt;/p&gt;</description></item><item><title>Electrical Engineering Fundamentals, Without the Headache</title><link>https://hexrogue.github.io/blog/electrical-engineering-fundamentals/</link><pubDate>Wed, 09 Jun 2021 00:00:00 +0800</pubDate><author>ikanlemas0@gmail.com (Muhammad Nuh)</author><guid>https://hexrogue.github.io/blog/electrical-engineering-fundamentals/</guid><description>&lt;p&gt;I am a software guy. My world is if-else and semicolons. Then I touched electrical engineering and realized all my code runs on literal lightning we bullied into doing math. I have never trusted a semicolon since. So I learned the basics. Here is my notebook, translated into human.&lt;/p&gt;&#10;&lt;h2 id="voltage-is-pressure-current-is-flow"&gt;Voltage is pressure, current is flow&lt;/h2&gt;&#10;&lt;p&gt;Forget definitions for a sec. Picture a water pipe.&lt;/p&gt;&#10;&lt;p&gt;Voltage is how hard the water wants to move. Current is how much actually moves. Resistance is the narrow bit that says no. That mapping is the whole subject. Every confusing circuit I have hit turned into &amp;ldquo;wait, which part of the pipe is this.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>