Pratica di Shadowing: 100+ Computer Science Concepts Explained - Impara a parlare inglese con i video

What's the first thing you should do when your code throws an error?

Obviously, you should change nothing and try to run it again a few times.

If that doesn't work, you're gonna need a computer science degree.

The awesome thing about software engineering is that you can learn to code

and get a high-paying job while literally having no idea how anything actually works.

It all just feels like magic, like a pilot driving a giant metal tube in the sky while knowing nothing about aerodynamics.

Welcome to Computer Science 101.

In today's video, you'll learn the science behind the garbage code you've been writing by learning 101 different computer science terms and concepts.

This is a computer.

It's just a piece of tape that holds ones and zeros, along with a device that can read and write to it.

It's called a Turing machine, and in theory, it can compute anything, like the graphics in this video or the algorithm that recommended that you watch it.

At the core of modern computers, we have the central processing unit.

If we crack it open, we find a piece of silicon that contains billions of tiny transistors, which are like microscopic on-off switches.

The value at one of these switches is called a bit, and is the smallest piece of information a computer can use.

However, one bit by itself is not very useful, so they come in a package of 8 called a byte.

One byte can represent 256 different values, like all the characters that you type on your keyboard.

In fact, when you type into your keyboard, the character produced is actually mapped to a binary value in a character encoding like ASCII or UTF-8.

Binary is just a system for counting, like the base 10 system you normally use when counting on your fingers.

But it only has two characters, 1 and 0.

Humans have a hard time reading binary, so most often it's represented in a hexadecimal base 16 format,

where 10 numbers and 6 letters can represent a 4-bit group called a nibble.

As a developer, when you write code in a programming language, it will eventually be converted into machine code, which is a binary format that can be decoded and executed by the CPU.

What it doesn't do, though, is store data for your applications.

For that, computers have random access memory, or RAM.

It's like a neighborhood, and inside of every house lives a byte.

Every location has a memory address, which the CPU can read and write to.

You can think of the CPU and RAM as the brain of the computer.

But in order for a computer to be useful, it needs to handle input and output.

An input device might be the keyboard and mouse, while an output device might be your monitor.

Luckily, most developers don't need to worry about how this hardware fits together, because we have operating system kernels, like Linux, Mac, and Windows, that control all hardware resources via device drivers.

Now, to start hacking on the operating system, your first entry point is the shell, which is a program that exposes the operating system to the end user.

It's called a shell because it wraps the kernel.

It takes a line of text as input and produces an output.

This is called a command line interface.

Not only can it connect to your own computer, but with the secure shell protocol, it can also connect to remote computers over a network.

Now that you have access to the mainframe, it's time to pick a programming language, which is a tool

that uses the abstraction principle to make computers practical to work with for humans by simplifying different systems layer by layer.

Some languages, like Python, are interpreted.

That means there's a program called an interpreter that will execute each line of code one by one.

Other languages, like C++, are compiled.

They use a compiler to convert the entire program into machine

code in advance before the CPU attempts to execute it this results in an executable file

that can be run by the operating system without any extra dependencies.

Now, every programming language has a variety of built-in data types to represent the data we're working with in our code.

Instead of bytes, we work with more human-friendly things like characters and numbers.

Now, the most fundamental way to use data in your application is to declare a variable.

This attaches a name to a data point, allowing you to reuse it somewhere else in your code.

Python is a dynamically typed language, which means we don't need to tell the program exactly which data type is assigned to a variable.

It just figures it out automatically.

However, other languages like C are statically typed, and that means you need to specify the data type of a variable in your code.

When you define a variable, its value is stored somewhere in memory on the hardware, and you may need to allocate and free up memory throughout the program.

A pointer is a variable whose value is the memory address of another variable, which can be used for low-level memory control.

Many languages don't want to deal with low-level memory management and instead implement a garbage collector,

which automatically allocates and deallocates memory when an object is no longer referenced in the program.

Carpet's day!

Huh?

No!

Ah!

Now, the data types available are different in every programming language, but typically you'll find int to represent whole numbers,

which may or may not be signed or unsigned to represent negative numbers as well.

When numbers require a decimal point, they typically use the floating point type.

It's called a float because there's only enough memory to represent a certain range of numbers at a certain precision, and is basically a form of scientific notation to make computers faster.

If you need more range or precision, many languages also have a double that doubles the amount of memory used for the number.

Now when it comes to characters, you'll typically find the char data type to represent a single character, or more commonly, a string to represent multiple characters together.

Ultimately, these characters get stored in a memory address somewhere, but they need to be stored in a certain order.

When the order starts with the most significant byte in the smallest memory address, it's called Big Endian, or vice versa, if the least significant byte is stored in the smallest address, it's called Little Endian.

When it comes to practical software engineering, one of the most fundamental things we do is organize data into data structures.

The most useful data structure is probably the array, or list.

Just like a shopping list, it organizes multiple data points in order.

However, it also maintains an index of integers that starts at zero and goes up for every new item in the list.

That can be useful, but you don't actually need an index to create a list of items.

Another option is a link list, where each item has a pointer to the next item in front of it.

Another option is a stack that follows the last in first out principle.

It's like stacking a set of plates, then when you want to access the data, you pop the last one off the top.

The inverse option is a queue, which is first in first out.

Just like when you get into the breadline, the first person there is the first one to be fed.

Now another extremely useful data structure is the hash, which might also be called a map or dictionary.

It's like an array, but instead of an index of integers, you define the keys that point to each individual item, giving you a collection of key value pairs.

In many cases, though, it's not efficient to organize data in a linear way.

To address that problem, we have trees, which organize nodes together in a hierarchy that can often be traversed more quickly.

This can sometimes be too rigid of a data structure, though, so instead a graph can be created to connect multiple nodes together in a virtually unlimited number of ways.

A graph has a node for the data and an edge for the relationship between data points.

Data structures are essential, but they don't do anything by themselves.

To do something useful, you'll need to code up an algorithm, which is just code that solves a problem.

I took the initiative in creating the internet.

In our code, we have several mechanisms for implementing algorithms, the most fundamental of which is a function, which is a block of code that takes an input, then does something, and returns an output.

Like a variable, a function has a name, and it can be called from other parts of your code with different input parameters called arguments.

One thing you might do in the function body is compare one value to another.

Every language has a variety of built-in operators like equality, greater than, and less than that you can use to compare two values.

If A is greater than B, then it forms a value of true.

But if B is greater than A, then the value is false.

True false is what's known as a Boolean data type.

And whenever your code produces a value like this, it's known as an expression.

But not all code will produce a value.

Sometimes your code will simply do something, which is known as a statement.

A good example is the if statement, which handles conditional logic.

For example, if the condition is true, it will execute this code, otherwise it will short-circuit and run the code inside of the else block.

Another very common type of statement is a loop.

A while loop will run this block of code over and over again until the condition in the parentheses becomes false.

100

That can be useful, but more often than not, you'll want to loop over an iterable data type like an array.

101

Most languages have a for loop that can run some code for every object in the array or iterable data structure.

102

Now, in some cases, a function may not have an output, which is generally called a void function.

103

An interesting thing about functions is that they can call themselves.

104

When a function calls itself, it's called recursion, because when done like this, by default, it will recurse forever, creating an infinite loop.

105

That happens because when you call a function, the programming language will put it into memory on what's known as the call stack, which is a short-term chunk of memory for executing your code.

106

When a function keeps calling itself, the language will keep pushing frames onto the call stack until you get a stack overflow error.

107

To avoid this, your algorithm needs a base condition, so it knows when to terminate the loop.

108

Now, when you write an algorithm, you'll need to determine if it's any good, and the system for doing that is called Big O Notation.

109

It's a standard format for approximating the performance of an algorithm at scale.

110

It may reference time complexity, which is how fast your algorithm will run, and space complexity, which deals with how much memory is required to run it.

111

Developers have many different algorithm types at their disposal.

112

The most crude option is brute force, where you might loop over every possible combination to hack somebody's credit card pin.

113

A more sophisticated approach might be divide and conquer, like binary search where you cut the problem in half multiple times until you find what you're looking for.

114

Another option is dynamic programming algorithms, where a problem is broken down into multiple smaller subproblems, and the result of each computation is stored for later use,

115

using a technique called memoization.

116

That means if a function has already been called, it will use the existing value instead of recomputing it again from scratch.

117

Then we have greedy algorithms that will make the choice that is most beneficial in the short term, without considering the problem as a whole.

118

One example of this is Dijkstra's shortest path algorithm.

119

On the flip side, we have backtracking algorithms, which take a more incremental approach by looking at all of the possible options, like a rat in a maze exploring all the different potential paths.

120

Now when it comes to implementing your code, there are always multiple ways to get the job done.

121

One programming paradigm is declarative, where your code describes what the program does and the outcome, but doesn't care about things like control flow.

122

This style of programming is often associated with functional languages like Haskell.

123

The other paradigm is imperative programming, where your code uses statements like if and while, providing explicit instructions about how to produce an outcome.

124

It's associated with procedural languages like C.

125

Today, most general-purpose languages like Python, JavaScript, Kotlin, Swift, and so on are multi-paradigm, which means they support all these options at the same time,

126

in addition to object-oriented programming.

127

The idea behind OOP is that you use classes to write a blueprint for the data or objects in your code.

128

A class can encapsulate variables, which are commonly called properties, as well as functions, which are usually called methods in this context.

129

It's a common way to organize and reuse code because classes can share behaviors between each other through inheritance, where a subclass can extend and override the behaviors of the parent class,

130

and it opens the door to all kinds of other ideas called design patterns.

131

Now, a class by itself doesn't actually do anything.

132

Instead, it's used to instantiate objects, which are actual chunks of data that live in your computer's memory.

133

Often, you'll want to reference the same object over and over again in your code.

134

When data is long-lived, it can't go in the call stack.

135

Instead, most languages have a separate area of memory called the heap, which unlike the call stack, can grow and shrink based on how your application is used.

136

It also allows you to pass objects by reference, which means you can use the same object in multiple variables without increasing the memory footprint, because it always points to the same chunk of memory in the heap.

137

Now what's interesting is that if we go back to the CPU that we talked about in the beginning, you'll notice that it contains multiple threads.

138

A thread takes the physical CPU core and breaks it into virtual cores that allow it to run code simultaneously.

139

There are some programming languages that support parallelism, where you can write code that literally executes on two different threads at the same time.

140

However, many languages out there are only single-threaded, but that doesn't mean they can't do two things at the same time.

141

Instead, they implement concurrency models, like an event loop or coroutines, that can pause or delay the normal execution of code to handle multiple jobs on a single thread at the same time.

142

Now, in modern computing, we're rarely working with the bare metal CPU and RAM.

143

Instead, we work in the cloud with a virtual machine, which is just a piece of software that simulates hardware.

144

That allows us to take really big computers and split them up into a bunch of smaller virtual computers.

145

These These machines are the backbone of the internet and are connected via the internet protocol.

146

Each machine has a unique IP address to identify it on the network.

147

That IP address is usually alias to a URL that is registered in a global database called the Domain Name Service.

148

Now to establish a connection, the two computers will perform a TCP handshake, which will allow them to exchange messages called packets.

149

On top of that, there's usually a security layer like SSL to encrypt and decrypt the messages over the network.

150

Now the two computers can securely share data with the Hypertext Transfer Protocol.

151

The client may request a webpage, then the server will respond with some HTML.

152

Modern servers provide a standardized way for a client to request data, which is called an Application Programming Interface or API.

153

The most common architecture is REST, where URLs are mapped to different data entities available on the server.

154

And that brings us to our final topic, mother effin' printers.

155

You're gonna need to learn how these things work inside and out, because every time you go to grandma's house, she's going to ask you to fix it, which shouldn't be a problem for a computer scientist like you.

156

Thanks for watching, and I will see you in the next one.

Cos'è la tecnica dello Shadowing?

Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.

Pratica di Shadowing: 100+ Computer Science Concepts Explained - Impara a parlare inglese con i video

Contesto e Background

Le 5 frasi chiave per la comunicazione quotidiana

Guida passo-passo per il Shadowing

Cos'è la tecnica dello Shadowing?