Computer Architecture Diagram

Bits, Bytes, Compilers, and Interpreters

      Every character shown right now on this post is represented by a byte, a form of a computers memory. A byte is made up of 8 bits, which are placeholders of a binary system. The binary system comprises of 0s and 1s representing off and on respectively. The character "z" for example is made up of strings of 0s and 1s like "01001101"(Not actual value). When you press "z" on the keyboard, it sends a message to the computer to display "z" on the screen or monitor. The compiler takes the signal and compiles the value to be whatever it is. An interpreter does the same thing except line by line. Say the value of the character "z" is "01001101"(Once again, probably not real value). When the compiler receives the value "01001101" it is able to send a message to display a certain combination and pattern of pixels on the screen to make up the character "z." All of this happens in milliseconds which is why we are able to type the characters on screen almost instantly after we typed them. It only takes a 16-bit computer to store over 50,000 numbers(65,536 to be exact). Later, languages were invented and the rules of these languages were also established. The computer languages make it easier to interact with the computer.

My Perspective on Computer Architecture

Computer architecture to me seems like the layout, hardware and software, of a computer. In hardware some of the parts of a computer I know of and their functions are:

• Core processor: The chip that processes the binary and interaction between functions in a computer, the fastest I know is an i7 intel core
• RAM: Auxiliary memory in a computer

Computers use the sensors under the keys, binary, screen, and compilers to show the message. The keys give the signal to display a character, which is represented as a binary byte, and the compiler converts the binary into on-screen text made up of pixels

Systems Thinking

(1)A system is a process in which objects interact with each other to complete a certain goal. A subsystem is a system part of a system, but sometimes, by itself, is not a system, since it can't function independently. (2)It interacts with its individual parts or subsystems to complete a certain task. Sometimes the individual parts are made up of groups of people, and sometimes it is machinery.
(3)Computers and programming or coding languages are a system and subsystem respectively. The computer parts work together to function and the languages also function using other subsystems of the computer and of the language itself. All of the computer languages can be facilitated to learn once the dynamics of a system are applied. Overall, the subject of computer science is just learning and applying a system.

Name Card-Reflect

This experience of making name cards has its many values. The most enjoyable part is actually creating the product, because it sparks creativity and artistic capabilities, and you get new ideas along the way. Though, there were this projects ups, there were also their downs, especially the time concern and the define step; it makes you cut down some of the ideas due to time. The main improvement for this project is to add an extra day.

Name Card-Prototype/Test

Name Card-Ideate

The colors of the sky are going to be blue, purple, and orange for favorite colors, and favorite element is represented by purple auroras. Purple auroras only show up when Nitrogen gas is excited. There is a wolf sitting on a rock howling at a moon made of pizza(the favorite microwaveable food) with cotton candy in an ice cream cone, representing my favorite ice cream flavor. There is pepperoni on the pizza, which I chose as my favorite meat

Name Card-Define

The toughest obstacles of making the name card is to implement the meat and some of the other bizarre things that Anthony wants to know about me. Also, choosing between certain options for my favorites will be tough

Name Card-Empathize

Sahil->Anthony
Anthony wants to know:

• favorite:
• native animal
• color when sad
• element
• exotic meat
• microwaveable food
• rock
• color
• plant
• ice cream flavor
• type of computer

Dig Deeper:

• meat
• ice cream
• element
• animal
• color when sad
• microwave

Design Thinking Process

Empathize: Receive a product request from a customer. Take their ideas, requirements, and restrictions.

Define: Find a way to complete the requirements. Maybe, cut down a few less important requirements.

Ideate: Integrate the previous two steps and formulate an idea for the product. Make multiple designs and choose the best.

Empathize: See if the ideas match the requirements and if the requirements that were possibly removed was acceptable. If the idea is not acceptable go back to "Define" and start again, if not move on.

Prototype: Create a test model of the product and integrate the ideas in

Empathize...again: Ask if the product prototype meet the requirements, ideas, and goals of the customer. If the prototype isn't successful, try again, but if it is, move onto the next step.

Test: Give the model to a few people and test if the prototype is fit for others. If it isn't fit try again.

Release: Congratulations, you have launched your product! Probably Alpha or Beta phase for feedback

Final Release: Release to world and have feedback

Hello World

I'm Sahil, 13 years old, and I enjoy meeting up with my friends. I am learning 4 programming languages and have made a 0-player game, and a 3D 1-player game.