<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Induwari Senewirathne on Medium]]></title>
        <description><![CDATA[Stories by Induwari Senewirathne on Medium]]></description>
        <link>https://medium.com/@senewirathneinduwari?source=rss-fd83e4fc2fd0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rltTb_EyYXBZRe0x</url>
            <title>Stories by Induwari Senewirathne on Medium</title>
            <link>https://medium.com/@senewirathneinduwari?source=rss-fd83e4fc2fd0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:51:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@senewirathneinduwari/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From Cloud Concepts to Real-World Software: How My Thinking Changed.]]></title>
            <link>https://medium.com/@senewirathneinduwari/from-cloud-concepts-to-real-world-software-how-my-thinking-changed-27a500b0e42b?source=rss-fd83e4fc2fd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/27a500b0e42b</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Induwari Senewirathne]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 12:28:33 GMT</pubDate>
            <atom:updated>2026-09-20T12:28:33.659Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_BrwU-obTd01KQVaTGAl4w.jpeg" /></figure><p>When I first started learning software development, I usually thought about an application in a simple way:</p><p><strong>Frontend → Backend → Database</strong></p><p>Build the interface.<br>Write the backend.<br>Connect the database.<br>Deploy the application.</p><p>That mental model worked well enough for my early projects.</p><p>But as I started learning more about software engineering, I kept running into questions that my usual development workflow didn’t fully answer.</p><p>Where does the application actually run?</p><p>How does it communicate with other components?</p><p>What happens when the number of users grows?</p><p>Where should files and data be stored?</p><p>How do we control access?</p><p>How do we monitor a system after deployment?</p><p>And perhaps most importantly:</p><p><strong>What makes an application reliable beyond simply making it work?</strong></p><p>Those questions led me to cloud computing.</p><p>I recently completed <strong>AWS Cloud Practitioner Essentials</strong>, covering 13 modules ranging from cloud fundamentals and compute to networking, storage, databases, security, monitoring, migration, and well-architected solutions.</p><p>But rather than writing another article listing cloud services, I wanted to share the four ideas that changed the way I think about building software.</p><h3>The first shift: an application is bigger than its code</h3><p>The biggest change in my thinking was realizing that the application I write is only one part of a much larger system.</p><p>Before learning cloud fundamentals, I mostly saw:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*_xFpGuCECS05vPX0cwG6Dw.png" /></figure><p>Now I see something closer to:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*i7Q-qnu7xQ4NnuIrf_FlGw.png" /></figure><p>This was probably the most important lesson for me.</p><p>A system doesn’t become production-ready simply because the code works.</p><p>It also needs an environment in which it can <strong>run, communicate, store information, remain secure, be monitored, and adapt to changing requirements</strong>.</p><p>That is where cloud architecture starts becoming interesting.</p><h3>A. Compute taught me that “running an application” has different meanings</h3><p>One thing I found interesting was learning that there isn’t just one way to run an application.</p><p>Virtual machines, containers, and serverless approaches provide different levels of control and responsibility.</p><p>That made me rethink a question I had previously asked too simply:</p><blockquote><em>“Which technology should I use?”</em></blockquote><p>A better question is:</p><blockquote><strong><em>“What does this application actually need?”</em></strong></blockquote><p>Does it need complete control over the environment?</p><p>Does it need portability?</p><p>Does it need automatic scaling?</p><p>How much infrastructure do I actually want to manage?</p><p>These questions are more useful than simply choosing a technology because it is familiar.</p><p>And this is something I want to apply to my own projects rather than keeping it as theoretical knowledge.</p><h3>B. Networking, storage and databases made the architecture feel real</h3><p>The next realization was that all the components of an application need to communicate somehow.</p><p>Learning about networking introduced concepts such as virtual networks, subnets, routing, gateways, IP addresses, and access controls.</p><p>At the same time, storage and databases made me think more carefully about <strong>what kind of data I am actually working with</strong>.</p><p>A document, an image, a user record, and a transaction don’t necessarily belong in the same kind of storage.</p><p>That sounds obvious when written down.</p><p>But learning the infrastructure perspective helped me understand why these decisions matter at the architecture level.</p><p>Instead of thinking:</p><blockquote><em>“Where can I save this data?”</em></blockquote><p>I started thinking:</p><blockquote><strong><em>“What is this data, how will it be accessed, and what does the system require from its storage?”</em></strong></blockquote><p>That is a much more useful question for a software engineer.</p><h3>C. Security and monitoring changed what “finished” means</h3><p>Another important shift was understanding that deployment isn’t the end of development.</p><p>Imagine building an application, deploying it, and then walking away.</p><p>How would you know whether something is failing?</p><p>How would you know who is accessing your resources?</p><p>How would you investigate unexpected behavior?</p><p>How would you know whether the application is consuming more resources than expected?</p><p>This introduced me to a broader operational mindset involving <strong>security, monitoring, compliance, and governance</strong>.</p><p>The Shared Responsibility Model was also an important concept for me.</p><p>Cloud providers manage part of the security of the infrastructure, but customers still have responsibilities depending on the services and architecture they use.</p><p>That reinforced something I have already encountered in software development:</p><p><strong>Security isn’t a feature you add at the very end. It is part of system design.</strong></p><h3>D. The part that brought everything together</h3><p>The final concept that really connected these ideas for me was <strong>well-architected systems</strong>.</p><p>Until this point, I was mostly asking:</p><blockquote><em>“Does the application work?”</em></blockquote><p>But a better system-level question is:</p><blockquote><em>“Does it work well?”</em></blockquote><p>That means thinking about things such as:</p><ul><li>Reliability</li><li>Security</li><li>Performance</li><li>Scalability</li><li>Operations</li><li>Cost</li><li>Sustainability</li></ul><p>A system can work perfectly for 10 users and struggle with 10,000.</p><p>It can be fast but poorly secured.</p><p>It can be reliable but unnecessarily expensive.</p><p>It can solve today’s problem while creating tomorrow’s maintenance problem.</p><p>So architecture isn’t about finding one “perfect” design.</p><p>It’s about making appropriate decisions based on the system’s requirements and constraints.</p><p>The application is no longer just the code I write.</p><p>It is an interconnected system.</p><p>And that is probably the most valuable thing I took away from this learning experience.</p><h3>What’s next?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42Q_fLMNjQOObXpzS7Ybwg.png" /></figure><p>This learning journey gave me a foundation, but I see it as a starting point rather than an endpoint.</p><p>Now, I want to move from <strong>understanding cloud concepts to applying them</strong>.</p><p>I want to take the projects I build and gradually explore what happens beyond development:</p><p><strong>Build → Deploy → Secure → Monitor → Scale → Improve</strong></p><p>I also want to connect cloud concepts with the areas I’m already learning — full-stack development, APIs, databases, software engineering, and DevOps.</p><p>The more I learn, the more I see that these areas are not separate pieces. They come together when building software for real-world use.</p><p>For me, the next step is simple:</p><p><strong>Learn the concept. Build with it. See what happens. Learn from it.</strong></p><p>And keep repeating that process.</p><p><strong>One project, one concept, one lesson at a time.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27a500b0e42b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Computers Understand 0s and 1s: The Language of Binary]]></title>
            <link>https://medium.com/@senewirathneinduwari/how-computers-understand-0s-and-1s-the-language-of-binary-ff46581d0f57?source=rss-fd83e4fc2fd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff46581d0f57</guid>
            <dc:creator><![CDATA[Induwari Senewirathne]]></dc:creator>
            <pubDate>Thu, 02 Apr 2026 06:54:31 GMT</pubDate>
            <atom:updated>2026-04-02T06:57:39.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mJPRX_f0o61mWwt4aVRI6g.png" /></figure><p>Think about what you do on a computer every day typing a message, opening a photo, playing a song. It all feels natural. But here’s something interesting: the computer has no idea what a letter or an image actually <em>is</em>.</p><p>Everything inside a computer comes down to just two things on and off. That’s it. Two states. And from those two states, computers build everything we see on screen.</p><p>In my earlier articles, I wrote about how computers process information and what happens the moment you press a key. Now I want to go one step deeper into binary, the actual language computers use to understand anything at all.</p><h3>What Even Is Binary?</h3><p>We humans count using ten digits: 0 through 9. That’s the decimal system.</p><p>Computers don’t do that. They use only two digits <strong>0 and 1</strong> because that’s how their circuits are built. Every tiny component inside a computer can be either switched on or switched off. Nothing in between.</p><p>So we say:</p><ul><li><strong>1</strong> = On</li><li><strong>0</strong> = Off</li></ul><p>String enough of these together, and suddenly you can represent anything.</p><h3>Bits and Bytes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0v9lAcaKQJhr_ek1hlC4Dg.png" /></figure><p>A single 0 or 1 is called a <strong>bit</strong> the smallest piece of data a computer works with. One bit alone doesn’t tell you much. But group <strong>eight bits together</strong>, and you get a <strong>byte</strong>.</p><p>Like this: 01000001</p><p>That’s one byte and as you’ll see in a moment, it means something specific.</p><h3>How Does a Letter Become Binary?</h3><p>When you press the letter <strong>A</strong> on your keyboard, the computer doesn’t store the letter A. It stores a number in binary.</p><p>There’s a system called <strong>ASCII</strong> (American Standard Code for Information Interchange) that gives every character its own unique binary code. Think of it as a dictionary between human writing and computer language.</p><p>Character Binary Code A -01000001 , B - 01000010 , C - 01000011</p><p>So when you type A, the computer quietly stores 01000001. When it needs to show it back to you, it looks up that code and displays A again. You never see any of this happening but it&#39;s going on the whole time.</p><h3>Numbers Work the Same Way</h3><p>Binary handles numbers too, not just letters.</p><p>Decimal Binary 1 0001 2 0010 3 0011 4 0100</p><p>The part of the CPU called the <strong>ALU (Arithmetic Logic Unit)</strong> does all the math addition, subtraction, comparisons using exactly these binary values.</p><h3>It’s Not Just Text and Numbers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4DXdIVw2Nz5IwMvNSvW_g.png" /></figure><p>Here’s where it gets wild. Binary isn’t just for letters and math. <em>Everything</em> on your computer is binary underneath.</p><ul><li>A photo? Each pixel has a color, and that color is stored as a binary value.</li><li>A song? The sound waves are converted into binary data.</li><li>A video? It’s just a long sequence of images and audio all binary.</li></ul><p>Even the apps you use every day are, at their core, enormous strings of 0s and 1s.</p><h3>Why Not Use More Than Two States?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ld3IKR85v-8ByOv-DwMzng.png" /></figure><p>It’s a fair question. Why not use 0, 1, and 2 three states? Wouldn’t that be faster?</p><p>The reason computers stick with two states is reliability. Electronic circuits can very clearly tell the difference between “on” and “off.” The moment you add more states, things get harder to distinguish, and errors creep in.</p><p>Two states keeps things:</p><ul><li>Simple</li><li>Accurate</li><li>Consistent across billions of operations per second</li></ul><h3>Wrapping Up</h3><p>Computers can do incredibly complex things but they’re all built on the simplest possible foundation. Just 0 and 1. On and off.</p><p>Every letter you type, every video you watch, every game you play it’s all flowing through hardware as patterns of binary signals. What looks complicated from the outside is often something surprisingly elegant underneath.</p><p>Understanding this has genuinely changed the way I think about computers. When you know what’s happening at this level, everything else starts to make more sense.</p><p><em>This is part of my ongoing series on how computers work from the inside out. If you missed the earlier articles, feel free to start from the beginning!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff46581d0f57" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Think Pressing a Key is Simple? Here’s What’s Really Happening Inside]]></title>
            <link>https://medium.com/@senewirathneinduwari/think-pressing-a-key-is-simple-heres-what-s-really-happening-inside-e513e58f686a?source=rss-fd83e4fc2fd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e513e58f686a</guid>
            <dc:creator><![CDATA[Induwari Senewirathne]]></dc:creator>
            <pubDate>Fri, 13 Mar 2026 19:40:46 GMT</pubDate>
            <atom:updated>2026-03-14T10:43:53.141Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bka1YQ2Ew3CXNIbSZx-IAA.png" /></figure><p>Every day, we press hundreds of keys on our keyboards typing messages, writing assignments, searching the web. Most of the time, we don’t think twice about it. We press a key, and a letter instantly appears on the screen. Easy. Automatic. Almost boring.</p><p>Before I started my IT degree, I just assumed computers were simply “smart”, that they somehow figured things out on their own. But after studying Computer Organization and Architecture? That assumption didn’t last long. Even something as trivial as pressing a single key turns out to involve a carefully coordinated interaction between hardware and software.</p><p>In my previous blog, I walked through how computers process information from input to output. This time, I want to zoom in on just <em>one</em> input a single keypress and pull back the curtain on what’s really happening. If you’re a beginner, stick around. By the end, you’ll have a clearer picture of how the keyboard, CPU, memory, and operating system all work together to put that one character on your screen.</p><h3>The Keyboard Doesn’t Know What “A” Means</h3><p>Here’s something that surprised me early on: when you press a key, the keyboard doesn’t transmit a letter. Not at first.</p><p>What it does send is a <strong>scan code</strong> essentially a unique identifier for that physical key. An electrical signal fires, gets converted into binary (zeroes and ones), and gets passed along. At this stage, the computer has no idea you pressed “A.” It only knows <em>which key moved</em>. The meaning comes later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gv0gxjSscdNnvtSA1VsDVQ.png" /></figure><h3>An Interrupt? Yes, That’s the Actual Term.</h3><p>Now, here’s where it gets interesting. A lot of people assume the CPU is constantly watching the keyboard, waiting for input. It isn’t. That would be an enormous waste of processing power like leaving someone standing at your door all day just in case a visitor shows up.</p><p>Instead, the keyboard fires off something called an <strong>interrupt</strong> a hardware signal that basically tells the CPU: <em>“Hey. Something just happened. Pay attention for a second.”</em></p><p>The CPU obliges. It pauses whatever it was doing, handles the keyboard input, then picks right back up where it left off. Clean. Efficient. No wasted cycles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GdMgqYq5p7wed54n1O-6tw.png" /></figure><h3>The OS Steps In</h3><p>Once the interrupt lands, the CPU hands things off to the <strong>operating system</strong> and this is where raw signal becomes meaning.</p><p>The OS translates that scan code into an actual character. It also figures out <em>where</em> the input should go. Are you typing in a browser? The character goes to the search bar. Working in a text editor? It lands in your document. The OS is essentially the traffic controller sitting between your hardware and your apps, making sure everything ends up in the right place.</p><h3>Fetch, Decode, Execute Three Steps, Unbelievably Fast</h3><p>After the OS does its job, the CPU gets to work through what’s called the <strong>Fetch–Decode–Execute cycle</strong>. Every instruction runs through this loop:</p><ol><li><strong>Fetch</strong> — grab the relevant instruction from memory</li><li><strong>Decode</strong> — figure out what it’s asking for</li><li><strong>Execute — </strong>carry it out</li></ol><p>While this is happening, <strong>registers</strong> inside the CPU hold tiny chunks of data for immediate use, and <strong>RAM</strong> keeps the broader program and input data within reach. The whole thing takes a fraction of a millisecond. Then it happens again. And again. Millions of times per second.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohWgno9GyNQV7Vfp6gob8w.png" /></figure><h3>The Letter Shows Up</h3><p>Eventually, the processed data reaches the display system. Binary gets converted into pixels, pixels form a character, and the letter appears on screen. From your perspective? Instant. From the computer’s perspective? A carefully coordinated relay race involving multiple components all hitting their marks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XOhqjFTDR2PAJ-MP-BKlpw.png" /></figure><h3>So Why Does It Feel Effortless?</h3><p>Modern CPUs run at billions of cycles per second. Frequently accessed data sits in cache memory much faster than RAM. Operating systems have been refined over decades to handle input with minimal delay. All of that stacks up, and the result is a system that makes extraordinary complexity feel like nothing at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L2tTcK4E2VGcLaxUMk5_qw.png" /></figure><p>The thing is, I pressed <em>a lot</em> of keys before I had any idea what was happening underneath. Understanding this process didn’t make typing faster or slower but it did change how I think about the machines I use every day. There’s a whole, intricate world running beneath every keystroke. Most of us just never stop to notice it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e513e58f686a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Input to Output: How Computers Understand and Respond]]></title>
            <link>https://medium.com/@senewirathneinduwari/from-input-to-output-how-computers-understand-and-respond-78e419182450?source=rss-fd83e4fc2fd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/78e419182450</guid>
            <dc:creator><![CDATA[Induwari Senewirathne]]></dc:creator>
            <pubDate>Fri, 11 Jul 2025 04:50:48 GMT</pubDate>
            <atom:updated>2025-07-11T04:50:48.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E9zhJWFb1OrpbzkU" /><figcaption>Photo by <a href="https://unsplash.com/@glenncarstenspeters?utm_source=medium&amp;utm_medium=referral">Glenn Carstens-Peters</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Introduction</strong></p><p>Before I began my IT degree, I thought computers were just smart boxes that somehow “knew what to do” when I typed something or clicked a button. But once I started learning about <strong>Computer Organization and Architecture</strong>, I realized that every response a computer gives is the result of a carefully coordinated system.</p><p>In this blog, I’ll take you through the journey of how a computer processes information — from the moment you give an input to the moment you see the output. If you’re a beginner, this simple guide will help you understand how different parts like the <strong>CPU</strong>, <strong>memory</strong>, <strong>buses</strong>, and <strong>I/O devices</strong> work together inside a computer.</p><p><strong>What Is Computer Organization and Architecture?</strong></p><p>Let’s break it down:</p><ul><li><strong>Computer Architecture</strong> is the logical design or <strong>blueprint</strong> of a computer system. It defines how the CPU, memory, and input/output devices are organized and how they interact.</li><li><strong>Computer Organization</strong> explains the <strong>physical implementation</strong> — how data actually flows between these components, how instructions are executed, and how the hardware is built.</li></ul><p><strong>In short:</strong></p><p>· <em>Architecture</em> is about what a computer does</p><p>· <em>Organization</em> is about how it does it</p><p>Together, they give us a deeper understanding of how computers process information internally.</p><p><strong>Main Components of a Computer System</strong></p><p>Let’s explore the key units that work together to make a computer respond to our input.</p><ol><li><strong>Input Unit</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VcxH3wKfPRsRae-M" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Input devices let users give instructions to the computer. These include keyboards, mice, touchscreens, microphones, and scanners.</p><p>For example, when you press the letter “A” on your keyboard, the device sends a <strong>binary signal</strong> (made up of 0s and 1s) to the computer’s processor for interpretation.</p><p><strong>2. Central Processing Unit (CPU)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tvfIIcdd0emoyH35" /><figcaption>Photo by <a href="https://unsplash.com/@christianw?utm_source=medium&amp;utm_medium=referral">Christian Wiediger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The <strong>CPU</strong>, often called the <strong>brain</strong> of the computer, is responsible for processing all instructions. It consists of three major parts:</p><ul><li><strong>Control Unit (CU):</strong> Manages and directs operations inside the computer</li><li><strong>Arithmetic Logic Unit (ALU):</strong> Performs arithmetic and logic operations</li><li><strong>Registers:</strong> Small, fast storage inside the CPU used for temporary data during execution</li></ul><p>The CPU works in a loop called the <strong>Fetch-Decode-Execute Cycle</strong>:</p><ol><li><strong>Fetch</strong> the instruction from memory</li><li><strong>Decode</strong> the instruction to understand it</li><li><strong>Execute</strong> the instruction (e.g., perform a calculation or move data)</li></ol><p>This cycle happens millions of times per second, making everything you do on your computer feel instant.</p><p><strong>3. Memory Unit</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rCRgrXK5Vby_QA1t" /><figcaption>Photo by <a href="https://unsplash.com/@tylerdaviaux?utm_source=medium&amp;utm_medium=referral">Tyler Daviaux</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The <strong>memory unit</strong> stores data and instructions temporarily or permanently, depending on the type.</p><p>Here’s a simple breakdown:</p><ul><li><strong>Registers</strong> are the smallest and fastest type of memory, built right into the CPU, used for immediate data processing.</li><li><strong>Cache Memory</strong> is slightly larger and stores frequently accessed data close to the CPU for quick retrieval.</li><li><strong>RAM (Random Access Memory)</strong> acts as the computer’s short-term memory. It stores data for running programs and is cleared when the computer shuts down.</li><li><strong>ROM (Read-Only Memory)</strong> holds permanent data, like boot-up instructions, that stay even when power is off.</li><li><strong>Secondary Storage</strong> includes hard drives and SSDs where data and programs are saved long-term.</li></ul><p>These different types of memory work together in a <strong>hierarchy</strong>, balancing speed, size, and cost to keep the system running smoothly.</p><p><strong>4. System Buses</strong></p><p>Inside the computer, information flows through communication pathways called <strong>buses</strong>:</p><ul><li><strong>Data Bus:</strong> Carries actual data</li><li><strong>Address Bus:</strong> Carries memory addresses</li><li><strong>Control Bus:</strong> Carries signals for operations like read/write</li></ul><p>Think of them as highways connecting the CPU, memory, and I/O devices, ensuring smooth and organized traffic of data.</p><p><strong>5. Output Unit</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HnHz860xnX2-agOJ" /><figcaption>Photo by <a href="https://unsplash.com/@goshua13?utm_source=medium&amp;utm_medium=referral">Joshua Aragon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>After processing, the final results are sent to output devices such as:</p><ul><li><strong>Monitors</strong> — to display text or visuals</li><li><strong>Printers</strong> — to produce hard copies</li><li><strong>Speakers</strong> — to play audio output</li></ul><p>The output unit converts binary data into a human-readable or audible format.</p><p><strong>From Input to Output: Real Example</strong></p><p>Let’s take a real example: typing the letter <strong>“A”</strong>.</p><ol><li><strong>Input:</strong> You press the “A” key on your keyboard.</li><li><strong>Conversion:</strong> The keyboard sends a binary signal for the letter “A” to the CPU.</li><li><strong>Processing:</strong> The CPU fetches, decodes, and executes the instruction.</li><li><strong>Memory Access:</strong> The instruction is temporarily stored in RAM and registers.</li><li><strong>Output:</strong> The processed result is sent to your monitor, and you see the letter “A” appear.</li></ol><p><strong>RISC vs. CISC</strong></p><ul><li><strong>RISC (Reduced Instruction Set Computing):</strong><br> Uses fewer and simpler instructions that execute quickly. Common in smartphones and tablets.</li><li><strong>CISC (Complex Instruction Set Computing):</strong><br> Uses more complex instructions that can do more in one step. Common in PCs and laptops.</li></ul><p><em>RISC = fast &amp; efficient | CISC = powerful &amp; flexible</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*-wW7nNnsb1a77KfZW6zOcQ.png" /></figure><p><strong>Conclusion</strong></p><p>Computers are no longer mysterious black boxes to me. Through studying <strong>Computer Organization and Architecture</strong>, I now understand how each part — from the input unit to memory to the CPU and output — plays a role in processing and responding to instructions.</p><p>This is just the beginning of my IT journey, and writing this blog has helped me reflect on how much I’ve already learned. I hope this article helps other beginners get started too — one step closer to understanding what really happens inside the machine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78e419182450" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>