This is the year computing shifts from using tools to building them. Students write and debug their own programs, break big problems into smaller pieces, and work with real data to back up a claim. They also weigh the trade-offs of technology in everyday life, from privacy to who gets left out. By spring, students can plan a program with a partner, test it, fix what breaks, and explain how it works.
Students start by learning how computers and the internet actually work behind the screen. They practice safer habits online, talk through privacy choices, and troubleshoot the everyday tech problems that come up at home and school.
Students break big problems into smaller steps and write short programs to solve them. Parents may hear about loops, functions, and bugs as students learn to plan code before they write it.
Students gather data, clean it up, and use tools like spreadsheets or simple code to spot patterns. They learn to back up claims with what the numbers actually show, and to question charts that mislead.
Students team up to design and build something useful, such as an app, a website, a game, or a simulation. They divide the work, give each other feedback, and test their project until it actually works for the people who will use it.
Students step back and look at how technology shapes daily life, from social media to artificial intelligence. They weigh trade-offs around privacy, fairness, and access, and practice explaining their thinking with clear evidence.
Students choose the right hardware and software for a task, then figure out what to do when something breaks or stops working.
Students explain how the internet moves data between devices and why security measures matter when sending information. They connect that understanding to real uses like sharing files, video calls, and working with others online.
Students gather raw data, clean or reorganize it, and display it in charts or tables. Then they use software to spot patterns and back up conclusions with numbers rather than guesses.
Students write and test programs that solve real problems or automate repetitive tasks. They also learn to read their own code critically, spotting where it breaks and why.
Students look at how technology shapes real life: who benefits, who gets left out, and what laws or ethical questions come up when software and data affect people's lives.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software High School | Students choose the right hardware and software for a task, then figure out what to do when something breaks or stops working. | NJ-CSDF.C1.9-12 |
| Explain how computer networks and the Internet enable communication… High School | Students explain how the internet moves data between devices and why security measures matter when sending information. They connect that understanding to real uses like sharing files, video calls, and working with others online. | NJ-CSDF.C2.9-12 |
| Collect, transform, and represent data High School | Students gather raw data, clean or reorganize it, and display it in charts or tables. Then they use software to spot patterns and back up conclusions with numbers rather than guesses. | NJ-CSDF.C3.9-12 |
| Design, develop, and analyze algorithms and programs to solve problems… High School | Students write and test programs that solve real problems or automate repetitive tasks. They also learn to read their own code critically, spotting where it breaks and why. | NJ-CSDF.C4.9-12 |
| Investigate the social, ethical, legal High School | Students look at how technology shapes real life: who benefits, who gets left out, and what laws or ethical questions come up when software and data affect people's lives. | NJ-CSDF.C5.9-12 |
Students learn to work with peers who have different backgrounds and viewpoints, and to build technology and solve problems in ways that consider everyone who might be affected.
Students split up tasks, share ideas, and fold in each other's feedback to build a working piece of software, an app, or another digital project together.
Students spot a complex problem, decide whether a computer could help solve it, and break it into smaller pieces a program could actually handle.
Students take a messy real-world problem and strip it down to the parts that matter, then write a solution that works for that problem and others like it.
Students build working programs or simulations by writing code, testing it, fixing what breaks, and repeating that cycle until the result does what they intended.
Students run planned tests on a program or app they built, find what breaks or confuses users, and fix those problems using what they learned from the results.
Students explain how a program works or why a technology matters using the right words, visuals, and data. The audience could be a teacher, a peer, or someone with no coding background.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… High School | Students learn to work with peers who have different backgrounds and viewpoints, and to build technology and solve problems in ways that consider everyone who might be affected. | NJ-CSDF.P1.9-12 |
| Collaborate around computing — divide work, share ideas High School | Students split up tasks, share ideas, and fold in each other's feedback to build a working piece of software, an app, or another digital project together. | NJ-CSDF.P2.9-12 |
| Identify and define problems that can be solved with computation and decompose… High School | Students spot a complex problem, decide whether a computer could help solve it, and break it into smaller pieces a program could actually handle. | NJ-CSDF.P3.9-12 |
| Use abstractions to simplify complexity, generalise solutions High School | Students take a messy real-world problem and strip it down to the parts that matter, then write a solution that works for that problem and others like it. | NJ-CSDF.P4.9-12 |
| Create computational artifacts — programs, simulations, models — by applying… High School | Students build working programs or simulations by writing code, testing it, fixing what breaks, and repeating that cycle until the result does what they intended. | NJ-CSDF.P5.9-12 |
| Systematically test computational artifacts and refine them based on evidence… High School | Students run planned tests on a program or app they built, find what breaks or confuses users, and fix those problems using what they learned from the results. | NJ-CSDF.P6.9-12 |
| Communicate clearly with appropriate vocabulary, visualizations High School | Students explain how a program works or why a technology matters using the right words, visuals, and data. The audience could be a teacher, a peer, or someone with no coding background. | NJ-CSDF.P7.9-12 |
Students learn to write programs, work with data, and understand how networks and the internet move information. They also look at how technology affects people, from privacy to fairness. The work mixes hands-on coding with thinking through the bigger picture.
No. Plenty of students start high school without any coding background and do fine. The early work focuses on breaking problems into steps and getting comfortable with the tools, not on knowing a specific language ahead of time.
Ask students to explain what their program is supposed to do and walk through it line by line out loud. Most coding bugs get found this way, and it shifts the thinking onto the student. Spending ten minutes as the audience is more useful than trying to debug the code yourself.
Most teachers start with problem solving and small programs, layer in data work once students can handle variables and loops, and weave ethics discussions into each unit rather than saving them for the end. Networks and hardware fit well alongside a project that needs them, like a shared app or a data pull.
Students can take a real problem, break it into smaller parts, and write a working program that solves it. They can pull data from a source, clean it up, and make a claim backed by what they found. They can also explain who their work affects and what trade-offs it involves.
Try a short puzzle on a site like Code.org or work through one challenge on a beginner Python tutorial. Talking through a news story about technology, like a data breach or an algorithm in the news, also counts and builds the thinking the class asks for.
Loops and conditionals trip students up the first time, and so does anything involving how data is stored versus how it is displayed. Plan extra practice and small low-stakes programs for both. Debugging as a skill, separate from writing code, is worth its own short lessons.
Roles help. Assign one student to design, one to code a specific part, one to test, and rotate across projects so everyone touches each role. Short check-ins where each student shows their piece keep the work honest.
Look for a student who can start a coding problem without being told exactly how to solve it, and who can talk about their code and what it does. Comfort with getting stuck, trying something, and trying again matters more than finishing every assignment quickly.