What does a student learn in
California, Grade 4, Computer Science & Digital Fluency ?

Students look at two or more step-by-step solutions to the same problem, then decide which one works best and why. It's less about finding the "right" answer and more about learning that there's usually more than one way to solve a problem.

Students write simple programs where a variable, like a score or a name, holds information that can change as the program runs. Think of it as a labeled box that stores a value the program can update.

Students write programs that respond to clicks or keypresses, repeat steps automatically, and make choices based on simple rules, like "if the score reaches ten, show the winning screen."

Students break a big problem into smaller steps, then break those smaller steps down further if needed. It's the same idea as turning "clean your room" into "make the bed, then sort the toys, then hang up clothes."

Students take pieces of working code they already have and combine them to build something bigger or add a new feature to a program they are working on.

Students plan a program, share it with classmates for feedback, and then revise it. The goal is to improve the work by considering what others notice, not just what the original programmer intended.

Students credit the original creator when they borrow or build on someone else's code, the same way they'd cite a book report source. Using another person's work without permission or credit is off-limits.

Students run their program, look for steps that go wrong, and fix the mistakes until the program does what it was supposed to do.

Students take on different jobs when building a program with a group: one person might plan the steps, another write the code, and another test it to find mistakes.

Students explain why they made choices while building a program by adding written notes inside their code and showing how it works to others.

Students explain how devices like a keyboard, screen, or printer work together as one system. They trace how each part plays a role, from input to output.

Students learn how the physical parts of a computer (the screen, keyboard, and processor) and the programs running on it depend on each other to get something done, like typing a document or playing a game.

When a device freezes or a program stops working, students figure out what might fix it. They practice basic steps like restarting, checking connections, or closing an app to get things running again.

Some files take up more space than others. A photo or video needs far more storage than a short text note, and a high-quality image needs more space than a blurry one.

Students gather information, arrange it into a chart or graph, and use what they see to back up a point they want to make. The visual makes the argument easier to follow.

Students look at information they have collected, then use it to spot patterns, guess what might happen next, or explain their thinking to others.

Students look at inventions like smartphones or search engines and talk about how those tools changed daily life, and how the way people already lived shaped what those tools became.

Students think about how technology could work better for people who have different needs, like someone who can't hear audio or struggles to read small text, and suggest changes that would make it easier for everyone to use.

Students look at a piece of software or a digital tool and ask: who is left out? They learn that bringing in different voices makes the final product work better for more people.

Students learn why someone who makes a book, song, or artwork might not want others to copy or sell it without permission. They practice explaining the basic idea behind copyright in their own words.

When you send a message or photo online, it gets chopped into small chunks called packets, travels through several devices to reach its destination, and gets put back together on the other end. Students model how this works.

Students learn why passwords, locked screens, and privacy settings matter. They also look at physical steps, like not leaving a device where strangers can see it, that help keep personal information safe.

Students learn to create passwords and codes that keep private information safe from people who shouldn't see it.