<?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 Cameron Ratliff on Medium]]></title>
        <description><![CDATA[Stories by Cameron Ratliff on Medium]]></description>
        <link>https://medium.com/@cratliff?source=rss-5a7025076be8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*freAUbg9JJl1AujVGs4-Uw.png</url>
            <title>Stories by Cameron Ratliff on Medium</title>
            <link>https://medium.com/@cratliff?source=rss-5a7025076be8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:42:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cratliff/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[3 Amazing Chrome Extensions]]></title>
            <link>https://medium.com/curious/3-amazing-chrome-extensions-6d2da6ed1aea?source=rss-5a7025076be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d2da6ed1aea</guid>
            <category><![CDATA[chrome]]></category>
            <category><![CDATA[chrome-extension]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[browsers]]></category>
            <category><![CDATA[extension]]></category>
            <dc:creator><![CDATA[Cameron Ratliff]]></dc:creator>
            <pubDate>Tue, 20 Oct 2020 13:05:00 GMT</pubDate>
            <atom:updated>2020-10-21T21:40:15.891Z</atom:updated>
            <content:encoded><![CDATA[<h4>Personalize your browsing experience</h4><figure><img alt="Someone typing on a computer" src="https://cdn-images-1.medium.com/max/1024/0*rgLuYfvlnzhFlHsi" /><figcaption>Photo by <a href="https://unsplash.com/@dadaben_?utm_source=medium&amp;utm_medium=referral">Benjamin Dada</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>1. Clipboard History Pro</h3><p>Stop me if you’ve been here before…You’re doing work and you copy something to your clipboard. You do a few more things, and when you go to paste, you realize that you have inadvertently copied another item! Now you have to find the original item you copied and recopy it.</p><p>You can now avoid this annoying situation with the Clipboard History Pro extension. It keeps track of all of the items you have copied to your clipboard and lets you easily recopy any of them that you need. This tool is extremely easy to use and will save you many headaches down the road.</p><h3>2. The Great Suspender</h3><p>This extension was made for a very particular type of internet-user (which I am one of). If you are known as a “tab-hoarder”, you need to use this extension. Opening large numbers of tabs and windows can slow down your computer considerably. The Great Suspender will automatically sleep your unused tabs after a certain amount of time, sparing your computer from having them all run constantly. You can choose how long The Great Suspender will wait to sleep your tabs, as well as mark certain tabs that should never be slept. If you want to access a tab that has been slept, simply reload the page and continue where you left off. If you’re a tab-hoarder like me, don’t listen to anyone telling you to clean up your browser! Just download this extension and keep opening those tabs.</p><h3>3. Momentum</h3><p>This extension has been around for a while, but it’s worth mentioning. Momentum changes the default new tab page for you, and gives you a visually pleasing page to look at. Every day, it will show you a beautiful picture accompanied with a message to you, the time, an inspirational quote, the weather, and a todo list. After a long day of work, I find it pleasantly surprising to open a new tab and see Momentum’s greeting and photographs. It gives me that little bit extra boost.</p><p>Extensions are a great way to personalize your browsing experience in Chrome. They are a great way to fix small annoyances and make everything a little more pleasant! Let me know your favorite extensions in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d2da6ed1aea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/curious/3-amazing-chrome-extensions-6d2da6ed1aea">3 Amazing Chrome Extensions</a> was originally published in <a href="https://medium.com/curious">Curious</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Tips For Beginner Front End Developers]]></title>
            <link>https://levelup.gitconnected.com/5-tips-for-beginner-front-end-developers-d165a78d3853?source=rss-5a7025076be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d165a78d3853</guid>
            <category><![CDATA[beginner-coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Cameron Ratliff]]></dc:creator>
            <pubDate>Wed, 07 Oct 2020 15:07:59 GMT</pubDate>
            <atom:updated>2020-10-13T12:55:47.687Z</atom:updated>
            <content:encoded><![CDATA[<h4>Start your coding journey the right way</h4><figure><img alt="picture of a laptop" src="https://cdn-images-1.medium.com/max/1024/0*3bDEO8gVsxmxsEZ1" /><figcaption>Photo by <a href="https://unsplash.com/@emilep?utm_source=medium&amp;utm_medium=referral">Emile Perron</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Learning to code is no easy task. At first, it can seem like there’s a sea of information, and you don’t know where to begin. We’ve all been there, and we’ve all made mistakes along the way. I’ve compiled a list of five tips that I wish I knew when I started programming. Hopefully they can save you some headaches along the way!</p><h3>1. Understand The Basics First</h3><p>This sounds obvious, but so many people rush through the basics so they can build cool things. Programming is iterative, and everything builds off of one another. If you want to become a good developer, it is crucial that you actually understand what is happening on the ground floor.</p><p>Start with HTML, CSS, and Vanilla JavaScript. These are the building blocks for all front end frameworks. Don’t just breeze through them in a day. Build a few simple sites, and understand what was easy and what was challenging. Learning their difficulties will help you understand why certain libraries and frameworks are built the way they are. Also, learn the DOM! The DOM (Document Object Model) is incredibly confusing for new developers, but it is truly a vital piece for understanding how frameworks operate. <a href="https://developers.google.com/web/tools/chrome-devtools/dom">Chrome DevTools</a> are a great place to start for this.</p><h3>2. Debug With A Purpose</h3><p>Ah, debugging…It’s the best of times and the worst of times. 95% of the time, it is incredibly frustrating. You spend hours on a bug, only to find that you did something dumb like misspelling a word (get the Code Spell Checker extension for Visual Studio Code. Thank me later). 5% of the time though, you have a revelation where everything clicks. Suddenly, coding makes sense and all is right with the world.</p><p>As tedious as debugging is though, it is unavoidable. However, there is a right way and a wrong way to go about it. We are all guilty of this, but the more you go on to Stack Overflow/Reddit/Github, and plug-and-chug answers into your code until something works, the more you will hinder your progress. Debugging is a chance to connect the dots. You should strive to understand why something wasn’t working, and where the gap in your knowledge was. You’ll spend more time upfront on the issue, but it will benefit you greatly down the line.</p><h3>3. Push Yourself To Learn New Technologies</h3><p>No matter where you are in your journey, there will be a point where you become too comfortable. You will find a way of doing something that you like, and you’ll stick to it. I hate to break it to you, but in the world of programming, there’s usually a better way out there. Programming moves quickly. There are always new libraries and frameworks coming out (some better than others). If you want to be a good developer, you need to be willing to adapt. If you ever find yourself getting stagnant, push yourself outside of your comfort zone. Go learn a new language or library. Even if it’s something you won’t regularly use, you’ll be a more well rounded developer.</p><h3>4. Take A Basic UI/UX Course</h3><p>If you are on the front end, chances are that you will have to make things look nice. I don’t care if you invent the next Facebook, if it looks terrible, no one will use it. User interface is the first thing people will notice and it will be used to judge your entire application, plain and simple. You don’t have to be a design wizard, but do yourself a favor and learn some UI fundamentals. I recommend Gary Simon’s course: <a href="https://scrimba.com/learn/design">Learn UI Design Fundamentals</a>. It’s free and only an hour long. It will benefit you to do more than this one course throughout your career, but this is a good starting point.</p><h3>5. Have Fun</h3><p>Sounds cheesy, right? Burnout is very real among developers though. If you start to lose the passion, it’s a quick downward spiral. Make some time to build something you think is really cool. Don’t worry about making money, or if it’s useful. Just make it for you. Having a side project is really important for developers of all skill levels. There’s a reason you chose this field, make sure you don’t forget it.</p><p>It’s easy to get overwhelmed when you first get started. Don’t be afraid to make mistakes and keep pushing forward. It’s tempting to take shortcuts in the beginning. If you really want to be a good developer, don’t just strive for code that runs error-free, strive for understanding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d165a78d3853" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/5-tips-for-beginner-front-end-developers-d165a78d3853">5 Tips For Beginner Front End Developers</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Use Emmet In Visual Studio Code]]></title>
            <link>https://medium.com/@cratliff/how-to-use-emmet-in-visual-studio-code-27fabea6447f?source=rss-5a7025076be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/27fabea6447f</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[emmet]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[visual-studio]]></category>
            <category><![CDATA[snippet]]></category>
            <dc:creator><![CDATA[Cameron Ratliff]]></dc:creator>
            <pubDate>Wed, 30 Sep 2020 14:01:49 GMT</pubDate>
            <atom:updated>2020-09-30T14:01:49.612Z</atom:updated>
            <content:encoded><![CDATA[<h4>Save time with built-in snippets</h4><figure><img alt="Logo for Emmet" src="https://cdn-images-1.medium.com/max/600/1*UYTzdnLnSiuwEv8h_A0BXA.png" /></figure><p>If you use Visual Studio Code and are not using Emmet, you’re missing out on a fantastic tool. Emmet is a built-in plugin for many text-editors (I will only cover its use in Visual Studio Code). It allows you to write snippets and abbreviations that automatically transform into full code. It can help you write code much more efficiently and save you from doing tedious and repetitive tasks. Emmet works for both HTML and CSS, but for the purposes of this article, I will focus on getting you started with some basic HTML.</p><h3>1. The Exclamation Point</h3><p>If you take nothing else away from this article, remember this one trick. Open a new HTML file, type in !, and hit ‘Enter.’ Boom, a perfectly laid out HTML file just like that.</p><figure><img alt="gif of using exclamation point with Emmet" src="https://cdn-images-1.medium.com/max/1024/1*IkIfU4VpL4OuDvsNWiSH9Q.gif" /></figure><h3>2. Elements</h3><p>Emmet also makes it so you never need to write opening and closing tags. Simply type the name of the element you want, and hit ‘Enter.’</p><figure><img alt="gif showing how to use elements with Emmet" src="https://cdn-images-1.medium.com/max/1024/1*4lxH6RRxE-jApnK3H5DWqA.gif" /></figure><h3>3. Classes and IDs</h3><p>If you want to write a div with a class of main, all you need to type is .main and hit ‘Enter.’ For an ID you can type #main instead. The snippets default to using divs, but if you wanted to use another element instead, such as a paragraph, you would type p.main or p#main.</p><figure><img alt="using Emmet with classes and IDs" src="https://cdn-images-1.medium.com/max/1024/1*TKBiVj_K0EqWtrE_L9C2mw.gif" /></figure><h3>4. Children</h3><p>Emmet makes it very easy to structure a chunk of your HTML with a parent and its children. To give a ul a li child, type ul&gt;li and hit ‘Enter.’ Emmet also allows for chaining, which is when it starts getting really cool. If you want 5 children, you can type ul&gt;li*5. To have 5 children all with a class of ‘item’, you can type ul&gt;li.item*5.</p><figure><img alt="Using Emmet with Children Elements" src="https://cdn-images-1.medium.com/max/1024/1*FAkM4n9WywS-oIgzLuJlTg.gif" /></figure><p>This is just the tip of the iceberg when it comes to using Emmet. For a complete list of snippets, check out their <a href="https://docs.emmet.io/cheat-sheet/">documentation</a>. Emmet is an easy way to start becoming a quicker and more efficient programmer. Let me know your favorite Emmet snippet in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27fabea6447f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 3 Best CSS Resources No One Talks About]]></title>
            <link>https://medium.com/@cratliff/the-3-best-css-resources-no-one-talks-about-7089beeadf6d?source=rss-5a7025076be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/7089beeadf6d</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[flexbox]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Cameron Ratliff]]></dc:creator>
            <pubDate>Fri, 25 Sep 2020 13:08:32 GMT</pubDate>
            <atom:updated>2020-09-25T13:13:44.505Z</atom:updated>
            <content:encoded><![CDATA[<h4>Up your CSS game with these tools</h4><figure><img alt="css logo" src="https://cdn-images-1.medium.com/max/300/1*IXjptV0tMAU47tMpTlIckQ.png" /></figure><p>For both beginners and pros, CSS is a constant source of frustration. There’s probably a strong chance you’ve yelled at your computer at some point when working with CSS. In this article, I am going to share some resources that really helped my skills progress. If you ever want to quickly check how to use a property, MDN and W3Schools are always safe bets. But I’m hoping to give you some extra tools that will up your CSS game fast.</p><h3>1. Flexbox Zombies</h3><p>If you have not yet mastered flexbox, you need to. Flexbox is the first step to moving elements on your page in the ways that you want to. Maybe you’ve heard of Flexbox Froggy before, but I promise you Flexbox Zombies is the way to go. The game is divided into chapters for each flex property. You’ll spend plenty of time on each one, learning how they interact with the other flex properties. Oh, and you learn while fighting zombies along the way. Spend two hours with it, and you’ll be a flexbox pro in no time.</p><p><a href="https://mastery.games/flexboxzombies/">Flexbox Zombies</a></p><h3>2. Traversy Media</h3><p>No, I am not being paid to promote anyone, but if you have a CSS related question, there is a good chance that Brad Traversy has covered it — in depth — on his YouTube channel. CSS Grid, responsive design, collapsable menus, CSS frameworks, animations…you name it, he’s covered it. He has a knack for explaining things in a way that makes sense to beginners, and all of his videos start from scratch. As a new developer, I shied away from learning through videos. Instead I opted for searching through Stack Overflow, Reddit, and GitHub, hoping that someone had asked about my exact issue. It wasn’t until I started watching YouTube videos that I became proficient with CSS. You not only learn the answers to your own questions, but you see how other people code from start to finish. You pick up many things that you didn’t even know you could do. And Traversy Media is a great place to start.</p><p><a href="https://www.youtube.com/user/TechGuyWeb">Traversy Media</a></p><h3>3. Chrome DevTools</h3><p>Chrome DevTools seem intimating for beginners, and truthfully there is a lot going on. But there is no better tool for analyzing the elements on your page. To open the DevTools use the shortcut SHIFT + CTRL + J (or CMD + OPT + J on a Mac). In the the top left of the DevTools, you should see a box with an arrow in it, or as my friend likes to call it, “The Magic Button.”</p><figure><img alt="picture of chrome dev tools" src="https://cdn-images-1.medium.com/max/402/1*7y-MwxUz0J8HrP97T32Rqw.png" /></figure><p>This button will be your CSS savior. Click it and then hover over any item on your page. You can see each individual element as you hover. Click one to bring up the ‘Elements’ tab of the DevTools, where you can explore everything about the selected element. In the top portion (the DOM panel), you can edit its HTML, add attributes, delete the element, and much more. In the lower portion, you can see all of that elements’ CSS properties and modify them in the browser! If you are ever trying to get the margin, padding, or width of something just right, this is the place to do it. Real time feedback of your CSS is the best way to see what works and what doesn’t. The more you use Chrome DevTools, the more you will understand how powerful they can be.</p><p><a href="https://developers.google.com/web/tools/chrome-devtools">More Info On Chrome DevTools</a> (start with the ‘Elements Panel’ section)</p><p>If you are on the front end, interacting with CSS is unavoidable. You can either keep cursing the CSS gods, or finally spend some time learning the basics. These were my favorite resources when I first started to learn. Let me know if you have any others in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7089beeadf6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 5 Best Visual Studio Code Extensions]]></title>
            <link>https://medium.com/swlh/the-5-best-visual-studio-code-extensions-d4541edad882?source=rss-5a7025076be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4541edad882</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[visual-studio-code]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[extension]]></category>
            <dc:creator><![CDATA[Cameron Ratliff]]></dc:creator>
            <pubDate>Wed, 16 Sep 2020 13:50:34 GMT</pubDate>
            <atom:updated>2020-09-17T06:56:34.694Z</atom:updated>
            <content:encoded><![CDATA[<h4>Make your coding experience a little bit easier</h4><figure><img alt="computer" src="https://cdn-images-1.medium.com/max/1024/0*z4U9bb1lpeVHCH9Y" /><figcaption>Photo by <a href="https://unsplash.com/@clemhlrdt?utm_source=medium&amp;utm_medium=referral">Clément H</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>1. Live Server</h3><p>Live Server is a must for any developer. This should be the first extension any beginner downloads. After installing, you will will see a small “Go Live” button on the bottom of your Visual Studio Code window:</p><figure><img alt="Picture of “Go Live” button" src="https://cdn-images-1.medium.com/max/152/1*y2a-p65l1BzalOdNUOjQYg.png" /></figure><p>Write some code in an html file, press this button, and see some magic! (Alternatively, you can right-click within your html file, and select “Open with Live Server”). This will open your current file on your default browser, so you can see what your code outputs. Whenever you save a change in Visual Studio, the change will appear live on your browser.</p><h3>2. Prettier</h3><p>This is by far my favorite extension. Prettier is a code formatter that saves you so many hours of tedious formatting. When I first started coding, I had a misconception that if I wasn’t doing everything myself (indenting, adding semi-colons, etc.), that I was cheating. Wrong. Prettier has not only saved me time, it has taught me better practices for formatting and making my code legible. You can configure settings within Visual Studio (in your settings.json) or make a configuration file for each project. Check out this article for more details on configuration: <a href="https://www.robinwieruch.de/how-to-use-prettier-vscode">https://www.robinwieruch.de/how-to-use-prettier-vscode</a>. However, I encourage EVERYONE to place this piece of code in their settings.json:</p><pre>“editor.formatOnSave”: true</pre><p>This will allow Prettier to automatically format your code every time you save. I promise you will never look back.</p><h3>3. Bracket Pair Colorizer</h3><p>This is an extension that seems mildly helpful at first, but can be a lifesaver when it comes to debugging. All programmers know the struggle of trying to figure out where you went wrong when your brackets, parentheses, and braces don’t match. Bracket Pair Colorizer does exactly as the name suggests, and gives your brackets different colors. Unlike some other extensions, there’s no learning curve or cons with this. So help your future debugging efforts and download it!</p><h3>4. Code Spell Checker</h3><p>Nothing wild here, this is literally just a spell checker for your code. After you spend 30 minutes debugging, only to find you misspelled a word, you’ll wish you had this. Code Spell Checker underlines misspelled words and will save you headaches down the line.</p><h3>5. Turbo Console Log</h3><p>Turbo Console Log is the only extension on this list that I wouldn’t consider necessary, but I do really enjoy it. This is yet another tool to help with debugging (notice a theme here?). If you’re someone that finds yourself writing console logs 50 times trying to locate an error, this extension will help you out. Highlight a variable, press CTRL + ALT + L (or CMD + OPT + L on a Mac) and have a nice console log message with the highlighted variable outputted for you. You can even customize the message in its settings.</p><p>The more I code, the more I find myself wanting extensions to do the dirty work for me. These are my 5 favorite extensions, but I am always on the hunt for more. Let me know if I missed any in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4541edad882" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-5-best-visual-studio-code-extensions-d4541edad882">The 5 Best Visual Studio Code Extensions</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Computers Turn Code into Images and Sound]]></title>
            <link>https://medium.com/@cratliff/how-computers-turn-code-into-images-and-sound-96e07e1ab820?source=rss-5a7025076be8------2</link>
            <guid isPermaLink="false">https://medium.com/p/96e07e1ab820</guid>
            <dc:creator><![CDATA[Cameron Ratliff]]></dc:creator>
            <pubDate>Sat, 23 May 2020 18:25:24 GMT</pubDate>
            <atom:updated>2020-05-28T17:59:12.979Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Computers Transform Code into Images and Sound</h3><p>For the vast majority of us, the only explanation for how a computer works is magic. How can our computer convert our clicks and typing into something that appears on screen? My goal is to make that relationship a little clearer. This article is not meant to be overly technical, and it does not go into the complexities of memory storage. It is meant to provide a general overview of a computer process from start to finish.</p><p>The processes of a computer can be broken down into input and output, where the output is the images and sounds we have become so accustomed to interacting with. But in order to understand the output, we must start with the input. And input starts with code.</p><p><strong>Programming Languages</strong></p><p>Code is an informal word for programming. It is simply a series of instructions for the computer to process. Code can be received from an input device, such as a mouse or keyboard. When someone clicks, scrolls, or moves a mouse, a specified set of code is executed in the background.</p><p>Code can be written in many, many different languages. A main distinction to make between languages is whether they are high-level or low-level. High-level and low-level refer to how far the language is from the language that the computer can understand. The language computers can understand is known as machine-code.</p><p>High-level languages tend to be further from machine code, but easier for humans to understand. They are closer to how humans would actually write and are thus generally easier to learn. They also handle things like memory allocation/cleanup for you. Lower-level languages tend to be more similar to machine code. They give you more power over how your computer functions, which can lead to increased efficiency. However, these languages are generally much more difficult to understand and to learn.</p><p><em>Section Summary: User input (mouse, keyboard, voice command) triggers code to run in the background.</em></p><p><strong>Compilers</strong></p><p>So now we have a series of instructions from hundreds of possible languages. How can we send these instructions to the computer, which only understands machine code? The answer is a compiler. A compiler can take any language of code and convert it into machine code. It parses through the code and strips down every piece into simple logic. This is the essential process of a parse tree*. Take the statement 14 + 2 * 3 - 6 / 2. Below is an example of how this statement’s parse tree would look:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*E2tfAsr98YsL1oU681BU6Q.png" /><figcaption><a href="https://ruslanspivak.com/lsbasi-part7/">https://ruslanspivak.com/lsbasi-part7/</a></figcaption></figure><p>The parser reads through this expression and breaks down each piece further and further until we have the individual components. Once the code is broken down as much as possible, the compiler creates machine code that would represent that same code.</p><p>*Compilers actually use abstract syntax trees, but for the purpose of this article the differences are not important.</p><p><em>Section Summary: All languages can be broken down into the same logic which is then converted into machine code.</em></p><p><strong>Transistors</strong></p><p>Machine code looks like the 1’s and 0’s we are all so accustomed to associating with computers. But how do endless lines of 1’s and 0’s represent logic from our program? This is accomplished with transistors.</p><p>Transistors are devices used to amplify their electrical input. With the case of computers, transistors are equivalent to a light switch, they either allow or prevent an electrical current to flow through. That is, transistors are either open or closed…1 or 0.</p><p>Circuitry in the CPU is set up to take in 1&#39;s and 0&#39;s and have corresponding transistors open or close. A single computer may have hundreds of millions (or even billions) of transistors.</p><p>So, we have a bunch of 1’s and 0’s (machine code) that represent our instructions. Associated transistors then are turned on and off based on these instructions. This first example shows how we can use transistors to represent two booleans using ‘AND’ logic. (Booleans are just true or false statements).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*x65NyCsiVk5DsyzXIfTeIA.png" /></figure><p>Electrical current is sent through the wire, and the flow only continues to the output if both transistors are in the ‘on’ or ‘true’ state. In this current example, the input represented is 00 (representing false AND false), and the output is 0 (false). An input of 01 or 10 would also translate into a 0 output. The only scenario in which the output would be 1 would be if the input was 11.</p><p>Here is an example of boolean OR logic:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*Rq6JoxIk1SQ_gKJFHN3ZfQ.png" /></figure><p>In this case, an input of false-true (01), true-false (10), or true-true (11) would all produce an output of ‘on’ (1). Only an input of false-false (00) produces an output of ‘off’ (0). These are very simple examples for how the logic from our machine code can be translated into turning switches on or off.</p><p><em>Section Summary: Machine code (0’s and 1’s) is passed through transistors. Transistors can either allow or prevent current to flow through. This output of the current is either 1 or 0 (on or off).</em></p><p><strong>Binary into Images and Sound</strong></p><p>We are almost to the end of our process! Our original code is now represented by transistors which have given us a new output of 1’s and 0’s based on their ‘on’ or ‘off’ state. Each output represents one <em>bit</em>. These outputs are stored as <em>bytes</em>, each composed of 8 bits. An example byte could look like 10011001.</p><p>The last piece of the puzzle is to translate these 1’s and 0’s into things like images and sound. As you will see, everything can be encoded with numbers and numbers can be encoded with binary. The general concept is that we can use 1’s and 0’s to represent other numbers or even other ideas!</p><p>In binary, each digit can only be 0 or 1, and represents a power of the number 2. Take this byte for example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*CdVR9j4291VbkdSyHluFuw.png" /></figure><p>Each digit represents a power of 2, and the 1 or 0 simply tells you whether or not that power is ‘on.’ If the digit is ‘on’ you add it together with the other ‘on’ digits. In this case, the only digit that is ‘on’ is 2⁰ and 2⁰ = 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*gsskky3L0dN9OvNcYjr3Qw.png" /></figure><p>Here we have 2¹ and 2⁰ in the ‘on’ state. 2¹ + 2⁰ = 3</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*vzqxYf0fhhRBV3fZPFo7ug.png" /></figure><p>Here we have 2⁴, 2¹, and 2⁰ in the ‘on’ state. 2⁴ + 2¹ + 2⁰ = 19</p><p>The highest number you can represent with one byte (if every digit is ‘on’) is 255. In order to represent even greater numbers, you need to allocate more bytes to store that number. We can also represent other types of numerical information, like negative numbers and fractions, by allocating certain bits to represent this information. One bit of storage is assigned to represent if the number is negative (0) or positive (1). 52 bits are allocated for storing the position of the decimal (this also means that there is a limit for how accurately we can store numbers).</p><p>So now we see that with binary, we can represent all kinds of numbers, but how can we represent other ideas? ASCII (American Standard Code for Information Interchange) is a character coding standard for electronic communication. It maps every letter in the alphabet (as well as punctuation) to a specific binary number. This allows computers to store and communicate with text.</p><p>How about images? Without getting too deep into human anatomy, if you pack the colors red, green, and blue together closely enough, you can represent any color to the human eye. If we assign 3 bytes to a small square on our screen (a pixel), we can represent any color within this pixel. Each color, red/green/blue, is set to a strength of 0–255 (255 again is the limit of one byte). An RGB of (255, 0, 0) would represent red. Yellow’s RGB is (255, 255, 0). The example below shows how these RGB values can be combined to represent colors within pixels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*MH0qdtpPcvAo1H62WLbx4A.png" /><figcaption><a href="https://web.stanford.edu/class/cs101/image-1-introduction.html">https://web.stanford.edu/class/cs101/image-1-introduction.html</a></figcaption></figure><p>A monitor can have millions of pixels, each with its own color. When all are combined together, we have images.</p><p>Lastly, we can use binary to represent audio as well. Sound waves are just levels of where the wave is over time. The image below shows this. In order to represent this wave, we can store a list of binary numbers, each representing a particular value for the wave at that point in time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/1*jPbXEhhaIYfe1NYdtcFNDQ.png" /><figcaption><a href="https://www.quora.com/How-is-sound-represented-using-binary">https://www.quora.com/How-is-sound-represented-using-binary</a></figcaption></figure><p><em>Section Summary: Output from the transistors are saved as bytes of 1’s and 0’s. These bytes are interpreted as binary, which can be used to represent all numbers, images, and sound.</em></p><p>The process is now complete! We have converted our original code into something that we as humans can understand and enjoy. In summary:</p><ul><li>User input (mouse, keyboard, voice command) triggers code to run in the background.</li><li>That code is compiled into machine code (made up of 0’s and 1’s), but still represents the original logic.</li><li>That machine code triggers an electrical current to be passed through transistors, which either prevent or allow the current to continue. The output of on or off is represented by a 1 or a 0.</li><li>Output from the transistors are saved as bytes of 1’s and 0’s. These bytes are interpreted as binary, which can be used to represent all numbers, images, and sound.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96e07e1ab820" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>