Bits and Binary: the computer’s secret language

This module’s first lesson, taught right here on the site — no other tab needed. It starts at the very bottom: the only language a computer truly understands. Read slowly. Every new word is explained the first time it appears.

The idea, in plain words

A computer does not think in words, pictures, or sounds. Deep inside, it works with electricity — and electricity in a chip is either flowing or not flowing. That is all it has. So everything a computer does must be built from just two states.

Binary is a way of writing numbers with only two digits: 0 and 1. The counting system you use every day has ten digits (0–9) and is called decimal. One single 0 or 1 is called a bit — short for binary digit. A bit is the smallest piece of information a computer can hold.

Why only two digits? A computer chip is made of billions of tiny switches called transistors. A switch has exactly two positions: off and on. Off means 0. On means 1. There is no “half-on” — and that is the point. Two very clear states are fast and hard to mix up, so a computer can flip them billions of times per second without making mistakes.

Bits usually travel in groups of eight. Eight bits together are called a byte. One byte is enough to store one character of text — the letter A, for example, is stored as the byte 01000001.

Everyday example: light switches

Think of a light switch at home. It is either off or on — never anything in between. One switch is exactly like one bit:

• One switch (1 bit): 2 possible states — 0 (off) or 1 (on).
• Two switches (2 bits): 4 combinations — 00, 01, 10, 11.
• Three switches (3 bits): 8 combinations.

See the pattern? Every switch you add doubles the number of combinations. Keep doubling up to eight switches — one byte — and you get 256 combinations. That is enough for every letter, digit, and symbol on a keyboard, which is exactly why one byte can hold one character.

Sa madaling salita: ang bit ay parang switch ng ilaw — patay (0) o bukas (1) lang. At bawat dagdag na switch, dumodoble ang kayang bilangin.

Worked example 1: counting in binary

In decimal, each place is worth ten times the place before it: 1, 10, 100. In binary, each place is worth double the place before it: 1, 2, 4, 8, and so on. To read a binary number, add up the places that hold a 1. Example: 101 means 4 + 0 + 1 = 5.

Watch how it counts: binary rolls over much sooner than decimal, because it runs out of digits after 1. Where decimal goes 1, 2, … 9, then 10, binary goes 1, then straight to 10.

Worked example 2: adding 5 + 3 in binary

5 in binary is 101, and 3 is 011. (Writing 3 as 011 changes nothing — a zero in front adds no value, like writing 03 in decimal. It just lines the columns up.) Add column by column, from right to left, exactly like ordinary addition:

   1 1       carried 1s
   1 0 1     = 5
+  0 1 1     = 3
-----------
 1 0 0 0     = 8

1. Right column: 1 + 1 = 2. Binary has no digit “2” — 2 is written 10. So write 0, and carry the 1 into the next column. To carry means the extra value moves one column to the left — the same thing that happens in decimal when a column goes past 9.
2. Middle column: 0 + 1, plus the carried 1, makes 2 again. Write 0, carry 1.
3. Left column: 1 + 0, plus the carried 1, makes 2 again. Write 0, carry 1.
4. The last carry has no column left to move into, so it becomes a brand-new column on the far left: 1.

The answer reads 1000. Check it in decimal: 1000 in binary is 8, and 5 + 3 = 8. It matches — the computer’s way and your way agree.

How computers talk: addresses and packets

This module’s first lesson, taught right here on the site — no other tab needed. It explains how computers find each other and swap information across a network. Read slowly. Every new word is explained the first time it appears.

The idea, in plain words

A network is two or more computers linked together so they can share things — files, messages, games, web pages. The internet is the biggest network of all: millions of smaller networks connected to each other.

Every computer on a network needs an address, so the others know where to send things. That address is called an IP address (IP is short for Internet Protocol — the shared set of rules computers follow when they talk to each other). No address, no delivery.

Data does not travel in one big lump. It is chopped into small pieces called packets. Each packet carries a little of the data, plus the address it is going to and the address it came from — so the pieces can find their way and be put back together at the other end.

The box that moves packets along is called a router. A router reads the address on a packet and forwards it — sends it onward, one step closer to where it needs to go. The Wi-Fi box in your home is a router.

One problem: people remember names, not numbers. So the internet has DNS (short for Domain Name System) — the internet’s phone book. You give DNS a website’s name, and it looks up the matching IP address for you.

Sa madaling salita: parang magkakapitbahay ang mga computer — bawat isa may sariling address, at ang packets ang mga sulat na ipinapadala nila sa isa’t isa.

Everyday example: sending a letter

A network works a lot like the postal service:

• Your house address = the IP address. It tells everyone exactly where to deliver.
• The letter you send = a packet. One piece of the message, travelling on its own.
• The post office sorting office = the router. It reads the address and sends the letter onward, closer to its destination.

What if your letter is too long for one envelope? You tear it into pages and mail each page in its own envelope, numbered 1, 2, 3… The person at the other end puts the pages back in order and reads the whole letter. That is exactly what splitting data into packets is like.

Worked example: opening a website, step by step

Say you open a website. Here is what actually happens:

1. You type the site’s name into your browser — a name you can remember, like a friend’s nickname.
2. DNS looks up its IP address. The name is easy for you; the number is what computers use. The answer might be 142.250.190.14.
3. Your request is split into numbered packets. Each packet is small, addressed, and numbered, so nothing gets mixed up on the way.
4. Your router forwards each packet along a path toward that address. A packet may pass through several routers on the way, like a letter passing through several sorting offices.
5. The reply packets come back. The website lives on a computer called a server — a computer whose job is answering other computers’ requests. Its reply packets travel back to you and are reassembled — put back together in order — into the page you see.

Now look closer at that address: 142.250.190.14. An IP address is four numbers, separated by dots. Each number is called an octet — oct means eight, because each one is stored as eight bits (remember bits and bytes from Module 1?). Eight bits can count from 0 up to 255, so every octet must be between 0 and 255.

Worked check: is 300.1.2.3 a valid IP address? No. The first octet is 300, and 300 is bigger than 255 — an octet can never be that large. One bad number makes the whole address invalid.

Variables: the computer’s labeled boxes

This module’s first lesson, taught right here on the site — no other tab needed. It covers the most useful idea in all of programming: keeping things in named boxes so your code can use them again. Read slowly. Every new word is explained the first time it appears.

The idea, in plain words

A variable is a named box in the computer’s memory that holds one value. Memory is the computer’s short-term workspace — where it keeps things while a program is running. You give the box a name, put a value inside it, and from then on you use the name whenever you need that value.

To put a value into a box, you write the name, then an equals sign, then the value — like age = 14. Careful: in code, the = sign does not mean the “equals” you know from math class. It means “put this inside the box.” So read age = 14 out loud as “age gets 14.”

Sa madaling salita: ang variable ay parang lalagyan na may pangalan — lagyan mo ng laman, tapos gamitin mo ang pangalan kapag kailangan mo ang laman.

Everyday example: a labeled kitchen jar

Picture a jar in your kitchen with a label that says “Snacks.” The label is the variable’s name. Whatever sits inside the jar — biscuits today, candy tomorrow — is the value.

You can empty the jar and refill it with something else. The contents change, but the label still says “Snacks.” A variable works exactly the same way: the name stays fixed, and the value inside can change whenever the program needs it to.

Worked example: your first variables

Here is a tiny program in Python — the programming language this module teaches. Python reads a program from top to bottom, one line at a time. Read the code first, then the walkthrough under it.

name = "Ana"
age = 14
print(name)
print("I am", age, "years old")
age = 15
print(age)

1. name = "Ana" — puts the text "Ana" into a box named name. Text in a program is called a string — a string of characters, like letters on a string of beads. The quotes are how you mark text: they tell Python “this is text, not an instruction.”
2. age = 14 — puts the number 14 into a box named age. A whole number like 14 is called an integer. Numbers need no quotes — written bare, 14 is a number the computer can do math with.
3. print(name) — print() shows what is inside a box on the screen. The thing to show goes inside the parentheses — the round brackets. This line shows Ana.
4. print("I am", age, "years old") — print can show several things at once, separated by commas. Text in quotes prints exactly as written; age prints the value inside its box. This line shows I am 14 years old.
5. age = 15 — puts a new value into the same box. The old value, 14, is gone — 15 takes its place. The box kept its name; only the contents changed, exactly like the snack jar.
6. print(age) — shows what is in the box now: 15. This last line proves the change really happened.

So the whole program prints these three lines:

a = 5
b = 3
print(a + b)

fruit = "mango"
print(fruit, fruit)

score = 10
score = score + 1
print(score)

Your first web page: HTML is the skeleton

This module’s first lesson, taught right here on the site — no other tab needed. You will read a real web page line by line, then change it yourself in the try-coding box. Read slowly. Every new word is explained the first time it appears.

The idea, in plain words

A web page is a document — a file of text — that a browser reads and draws on your screen. The browser is the app you open websites with, like Chrome or Edge. You write the document; the browser turns it into the page you see.

The document is written in HTML, short for HyperText Markup Language. HTML is the skeleton of the page: it says what each part is — this is a heading, this is a paragraph — not how it looks. Color, size, and layout are a different job, done by a different language you will meet soon.

HTML is built from tags. A tag is a short label inside angled brackets, like <h1>. A tag and the content it wraps together are called an element: an opening tag, the content, and a closing tag. A heading is a title line — h1 is the biggest heading of all. A paragraph, written p, is a block of text.

Sa madaling salita: ang HTML ang kalansay ng page — siya ang nagsasabi kung ano ang bawat parte, hindi kung ano ang itsura nito.

Everyday example: building a house

Think of building a house. First comes the wooden frame — the skeleton of the house. The frame decides where the walls stand, and where the doors and windows go. Without a frame, there is nothing to build on.

HTML is that frame. It decides where each part of the page stands. The paint, wallpaper, and furniture come later — that decorating work belongs to CSS, the language that controls how a page looks. A page with no HTML is like a pile of bricks with no plan: all the pieces are lying there, but nothing holds them together.

Worked example: a complete real page

Here is a whole web page — every line of it. It is short, and it really works: a browser would draw it exactly as the walkthrough below describes. Read the code first, then the walkthrough under it.

<!DOCTYPE html>
<html>
  <head>
    <title>My first page</title>
  </head>
  <body>
    <h1>Hello, world!</h1>
    <p>This is my first web page.</p>
  </body>
</html>

1. <!DOCTYPE html> — the first line. It tells the browser: “this is an HTML page.” It is a label for the browser, not a tag, and nothing from it is drawn.
2. <html> — wraps the whole page. Everything else sits inside it, and </html> at the very end closes it.
3. <head> — holds information about the page. The head is never drawn on the screen.
4. <title>My first page</title> — the page’s name. It shows on the browser tab, not on the page itself.
5. <body> — holds everything you actually see: the heading, the text, all of it.
6. <h1>Hello, world!</h1> — a heading, the biggest size. “Hello, world!” is the classic first message programmers write when they try something new.
7. <p>This is my first web page.</p> — a paragraph: one block of plain text under the heading.

One pattern to notice: every opening tag has a matching closing tag, and the closing tag carries a slash — <h1> opens, </h1> closes. Open, content, close. That is an element, every time.

Databases: where apps keep their data

This module’s first lesson, taught right here on the site — no other tab needed. It shows where apps actually keep their information, and how to ask for exactly the piece you want back. Read slowly. Every new word is explained the first time it appears.

The idea, in plain words

A database is an organized store of information that apps read and write. Reading means looking information up. Writing means saving new information, or changing what is already saved. Nothing inside a database is dumped in at random — everything is kept in a fixed shape, so the app always knows where each piece lives.

The main shape is a table: information arranged in rows and columns, like a spreadsheet. Each row is one record — one complete item, such as one student. Each column is one field — one kind of fact that every row has, such as a name or a grade. So a students table holds one row per student, with a column for each fact about them.

Sa madaling salita: ang database ay isang maayos na imbakan ng impormasyon — parang isang malaking talaan na binabasa at sinusulatan ng mga app.

To ask a database for information, you use a language called SQL, short for Structured Query Language. A question written in SQL is called a query. You will read two real queries in this lesson, line by line.

This is how the apps you already use keep track of their data. A class portal keeps students, sections, and grades in a database. An online store keeps its products, prices, and orders there. A social media app keeps accounts, posts, and likes there. When you open an app and your information appears, the app has just asked its database a question — and the database answered.

Everyday example: a teacher’s class record

You already know a table like this from school: the teacher’s class record, where every student gets a line, and every line carries the same facts.

Each row is one student — one record. Each column is one fact kept about every student — one field. A database table is this exact idea, kept inside the app instead of on paper, where it can be searched and sorted in a split second.

Worked example: asking the table questions

Here is that class as a real database table, named students. It has three columns: id, name, and grade. The id is a number that belongs to one row only — no two rows share an id, so the database can always tell rows apart, even if two students someday share a name.

First question: show the name and grade of everyone in the table.

SELECT name, grade
FROM students;

1. SELECT — the word that opens a question. It means “show me these columns.”
2. name, grade — the columns to show, in that order. The id column is not listed, so it will not appear in the answer.
3. FROM students — “from this table.” It names the table to look in.
4. The semicolon ; — ends the question, like the period at the end of a sentence.

Result

The answer is itself a small table: the columns you asked for, from every row. And nothing in the original table changed — SELECT only reads.

Second question, a sharper one: which students have a grade of 90 or higher?

SELECT name
FROM students
WHERE grade >= 90;

1. SELECT name — show only the name column this time.
2. FROM students — from the students table, same as before.
3. WHERE grade >= 90 — the new part. WHERE means “only keep rows where this is true.” The database checks each row one by one: is this row’s grade 90 or more? The symbol >= means “greater than or equal to” — so a grade of exactly 90 would count.

Result

Ana (92) and Carla (97) passed the check. Ben (85) and Dan (78) were checked too, but their grades are below 90, so their rows were left out. That row-by-row checking is all WHERE does.

SELECT name
FROM students;

SELECT name
FROM students
WHERE grade >= 95;

SELECT grade
FROM students
WHERE name = 'Ben';

The operating system: the manager inside your device

This module’s first lesson, taught right here on the site — no other tab needed. It explains the one program that runs everything else on your phone or computer. Read slowly. Every new word is explained the first time it appears.

The idea, in plain words

Start with the machine in your hand or on your desk. A device is a physical machine — a phone, a tablet, a laptop, a desktop computer. Its physical parts are called hardware: the screen, the keyboard, the battery, and the chips inside. Hardware on its own does nothing. It needs instructions before it can do a single useful thing.

A program is a set of instructions that tells hardware what to do, step by step. An app is a program built for one job you care about — sending messages, taking photos, playing a game. And a file is one saved piece of information with a name: one photo, one song, one document.

Now the star of this module. An operating system (short: OS) is a program — the first big one that starts when you switch a device on. Its job is to manage everything else: which app runs, where your files are kept, and how apps get to use the screen, the keyboard, the storage (the part of the device that keeps your files), and the camera. You never open the OS the way you open an app. It is simply in charge, all the time, behind everything you see.

You already know several operating systems, even if you never called them that. Windows runs most laptops and desktops. macOS runs Apple’s Mac computers. Linux is free, and it runs most servers — powerful computers that hold websites and apps for other computers to use. Android, the OS on most phones, is built on Linux. iOS is the OS on iPhones.

Sa madaling salita: ang OS ang manager ng device mo — siya ang nagpapasya kung anong app ang tatakbo, at siya ang nag-iingat ng lahat ng iyong files.

Everyday example: the school principal

Picture a school. The students are like apps — each one has somewhere to be and something to do. The classrooms and desks are like the computer’s memory (the workspace where work happens right now) and its processor (the part that does the actual work, following instructions). And the principal? The principal is the OS.

• The principal decides who gets which room. The OS decides which app gets to use the processor, and for how long.
• The principal keeps the filing room, where every student record is stored and can be found again. The OS keeps your files in storage, so any app can find them later.
• The principal makes sure two classes never clash over one room. The OS shares the hardware fairly, so apps take turns instead of fighting over the screen, the camera, or the processor.

A school without a principal would be chaos — every class grabbing whatever room it wants. A device without an OS is the same: hardware with nobody in charge.

Worked example: what happens when you tap an app icon

You tap the icon for a game. Here is what the OS does, in order — all of it in about a second:

1. The screen tells the OS your finger tapped. The touchscreen notices the touch and reports exactly where it landed. The OS works out which icon you meant.
2. The OS finds the app in storage. Storage is the device’s filing cabinet: it holds every app and file, and it keeps them even when the power is off. The price of that safety is speed — fetching from the cabinet is slow.
3. The OS copies the app into RAM. RAM is the device’s desk: a fast workspace where running apps sit. It is much faster than storage — but it forgets everything the moment the power goes off. That is why the app is copied there, not moved.
4. The OS tells the CPU to start. The CPU is the worker — the part that follows instructions and does the calculating. The OS hands it the app’s first instructions, and the game starts running.
5. The OS draws the app’s window on the screen. A window is the area of the screen where one app shows itself. The OS gives the game its window and paints it for you to see.
6. The OS keeps the other apps paused in the background. Your chat app and music app do not close. The OS holds them in RAM, paused, and switches the CPU between all of them so quickly that it feels like everything runs at once. Running several apps this way is called multitasking.

Notice who did every step: the OS. The game never touched the hardware directly — it asked the manager, and the manager arranged everything.

Staying safe online: what cybersecurity really is

This module’s first lesson, taught right here on the site — no other tab needed. It explains what cybersecurity means, who the good and bad hackers are, and how to spot the most common trick used against ordinary people. Read slowly. Every new word is explained the first time it appears.

The idea, in plain words

Cybersecurity means keeping computers, phones, accounts, and data safe from people who try to steal, damage, or break into them. Your data is the information about you stored on a device or online — your photos, messages, school files, and passwords. An account is your personal space on a website or app, the one you open with a username and password — like your school portal account or your email account.

A hacker is a person who tries to get into computer systems — sometimes to protect them, sometimes to harm them. That difference is everything in this module, and it comes down to one word: permission.

A white hat hacker tests and protects systems with permission. The owner asks them to look for weak spots, so those weak spots can be fixed before anyone bad finds them. A black hat hacker breaks in without permission, to steal or damage things. Same skills, opposite sides — permission is what separates the two.

That is not just a rule of politeness; it is the law. Testing a system without the owner’s clear permission is illegal. In the Philippines, Republic Act 10175 — the Cybercrime Prevention Act of 2012 — makes unauthorized access (breaking into a system that is not yours) and online fraud crimes. Curiosity is good, and this site points you to legal places to practice it. Permission always comes first.

Sa madaling salita: ang cybersecurity ay ang pagprotekta sa iyong mga account at data — at ang pahintulot ang hangganan ng tama at ilegal.

Everyday example: a house with doors and locks

Think of your online life as a house. Your accounts are the rooms inside, and your data is everything you keep in them. Keeping the house safe works the same way online:

• You lock your doors at night. Online, that means strong passwords — they are the locks on your accounts, so use long ones that are hard to guess.
• You don’t hand your keys to strangers. Never share your passwords or one-time codes (the short numbers sent to your phone to prove it is really you) with anyone who asks.
• A guard at the gate checks IDs before letting anyone in. That is what logging in does: the website checks your username and password to verify you are really you before it opens the door.

None of this needs special tools. Most online safety is ordinary habits, done every time — just like locking a door.

Worked example: spot the phishing email

Phishing is a trick: a fake message that pretends to come from someone you trust — a bank, a school, a delivery company — so you will hand over your password or your money. Here is a short fake email from a scammer pretending to be a bank. Read it, then we take it apart line by line.

Now the walkthrough — three warning signs, in order:

1. The sender’s address is not the bank’s real address. It says secure-banko-alerts.com — a made-up name that only sounds official. Always check the domain: the main part of an address, the part after the @ sign. A real bank message comes from the bank’s own domain, not a look-alike.
2. The email creates panic. “24 hours or your account closes” is meant to make you rush before you think. Real banks do not threaten you like this — pressure is the scammer’s main tool.
3. The link asks you to type your password on a strange page. Never do that. If you are worried about your account, close the email and open the bank’s real app or website yourself, the way you normally would. If nothing is wrong there, the email was fake.

Math for IT: logic, algebra, and how to study them

This module’s first lesson, taught right here on the site — no other tab needed. It covers the two kinds of math IT students meet first — logic and algebra — and, just as important, how to study them so they actually stick. Read slowly. Every new word is explained the first time it appears.

The idea, in plain words

Logic is reasoning with two answers only: true and false. Something is either true, or it is false — nothing in between. Logic is the math of deciding, step by step, whether a statement is true.

You have already met logic in this course. In Module 1, you learned that a computer stores everything as bits — tiny switches that are either 0 or 1. Bits are just logic in disguise: 0 means false, and 1 means true.

And in Module 3, the Python lesson used if statements — lines that tell the program, “if this is true, do that.” Every if condition is a small logic question with a true-or-false answer. So logic is not new to you; this lesson just gives it a name and a shape.

The basic tool of logic is the truth table: a chart that lists every combination of inputs and the answer each one gives. You will read two truth tables in the worked example below — slowly, row by row.

Algebra is math with an unknown number. The unknown is usually written as a letter, most often x. Algebra is the part of math that teaches you to rearrange a problem — move things from one side to the other — until the unknown stands alone and you can solve for it. When a program computes a total price, or a game updates a score, algebra is working underneath.

In college, this kind of math — logic, plus sets (groups of things, like the set of all students in one class) — has its own subject name: discrete math. It sounds scary, but it is mostly what this lesson covers: yes-or-no questions and careful step-by-step reasoning. When you meet the name later, you will already know what it means.

Sa madaling salita: ang logic ay pangangatwiran gamit ang true at false, at ang algebra ay math na may hindi pa alam na numero.

Worked example: solving for x, one move at a time

Here is a small problem in the kind of words a game would use: You need 100 points to reach the next level, and you already have 35. How many more do you need?

You probably solved that in your head already. Algebra is just a careful way to write the same problem down: 35 + x = 100. Here, x is just a name for the number you don’t know yet — the points still missing.

There is really only one rule of algebra: whatever you do to one side of the equals sign, you must do to the other side too. That is what keeps the two sides equal.

So, take 35 away from both sides: 35 − 35 + x = 100 − 35. The left side simplifies to just x standing alone, and the right side gives the answer: x = 65.

Now check it back, the way you would check any answer: 35 + 65 = 100. It works — the two sides really are equal.

This is exactly what your Python programs do — x = 100 - 35 is the computer “solving for x” by rearranging, the same move you just made.

Sa madaling salita: sa algebra, ilipat-lipat ang mga numero hanggang ang x na lang ang mag-isa — at kung ano ang ginawa mo sa isang side, gawin mo rin sa kabilang side.

Everyday example: the umbrella decision

Students make logic decisions like this every day, without noticing. Here is one, in everyday words:

Kung umuulan AND wala akong payong → mag-jeep ako. (“If it is raining AND I have no umbrella → I will ride a jeep.”)

Look at the AND hiding inside that sentence. Two conditions must both be true before the decision happens:

• It is raining — true or false?
• I have no umbrella — true or false?

If it rains but you do have an umbrella, you might just walk with it. If it is sunny, umbrella or not, you walk. Only when both conditions are true at the same time does the jeep decision happen. That is an everyday if/then sentence with an AND inside it — the same shape as an if statement in code.

Worked example: the AND truth table, row by row

Now the same idea as a small machine: a lamp wired to two switches, A and B, where the electricity must pass both switches to reach the lamp. In logic, this wiring is called AND. Here is its truth table. On means 1 (true); off means 0 (false).

Here is how to read any truth table, using this one:

1. Each row is one combination. Two switches have exactly four possible combinations — off/off, off/on, on/off, on/on — so the table has four rows. Nothing is missing: every possibility gets its own row.
2. Read each row left to right. First the inputs (Switch A, then Switch B), then the answer. Row 3, for example, says: A is on, B is off.
3. The last column is the answer. The Lamp column tells you what that combination produces. Row 3’s answer: the lamp stays off, because the off switch blocks the path.
4. Look for the pattern. The lamp turns on in exactly one row — the row where both switches are on. That is the whole rule: AND = output on only when ALL inputs are on.

Now change the wiring so the electricity can pass through either switch. That wiring is called OR. Same four combinations — only the answers change:

Read it the same way: one row at a time, inputs first, answer last. The lamp is on in three of the four rows — every row except the one where both switches are off — because OR = output on when AT LEAST ONE input is on.

NOT: flip the answer

There is one more basic logic word, and it is the simplest of the three: NOT. NOT flips a statement’s answer — true becomes false, false becomes true. It has only one input, so its truth table is the smallest you will ever see:

Read it row by row, the same way as before: switch off → lamp ON; switch on → lamp off. Picture the lamp as a night-light that stays on until someone flips the switch — the switch being on is exactly what turns the lamp off. That is the whole rule: NOT = output is the opposite of the input.

In programming, NOT shows up everywhere: in Python, != means “not equal to”, and the word not flips a condition, as in if not finished: — “if it is NOT true that I am finished, do it again.” Same flip, same table.

Sa madaling salita: ang NOT ay pambaligtad — ang true nagiging false, ang false nagiging true.

How to study math for IT

Knowing the ideas is half the work. The other half is studying in a way that makes them stay. Three moves that work:

1. Try the worked example yourself first. After you read an idea, close the explanation and work the example again on your own — with different numbers, or different switch settings — before looking at the answer. Struggling a little first is what makes the answer stick when you check it.
2. Space it out. Three short sessions on three different days beat one long cram session the night before. Your brain keeps what it recalls again and again, so coming back to an idea on a new day is not wasted time — it is the method.
3. Treat mistakes as the lesson. When a practice answer comes out wrong, do not just read the right answer and move on. Find exactly which row or step broke — the same way you debug a program — because that broken step is the thing you actually needed to learn.