This is the stretch where computer use turns into computer thinking. Students stop just running apps and start building small programs, breaking a tricky problem into smaller steps they can actually code. They also learn how the internet really moves information around, how to keep accounts safe, and how to spot patterns in a pile of data. By spring, students can write and debug a working program, explain a chart they made from real data, and talk through the trade-offs of a technology choice.
Students learn how the parts of a computer work together and how devices talk to each other over a network. They also practice basic troubleshooting and habits that keep accounts and personal information safe online.
Students gather information, sort it into charts and graphs, and look for patterns. They learn to back up a claim with the numbers behind it instead of a guess.
Students write step-by-step instructions and turn them into working programs. They break a big task into smaller pieces, test what they build, and fix the parts that do not work yet.
Students plan and build a project as a team. They divide the work, share early drafts, give and take feedback, and present what they made with clear language and visuals.
Students look at how technology shapes daily life, from privacy and access to honesty online. They weigh the trade-offs of a tool or app and think about who it helps and who it leaves out.
Students figure out which devices, programs, and fixes are the right fit for a given job. That means choosing the right tool and knowing what to try when something stops working.
Students learn how the internet connects computers so people can share files, send messages, and work together, and why encryption and passwords help keep that data private.
Students gather raw data, organize it, and turn it into charts or summaries. Then they use software or spreadsheets to spot patterns and explain what the numbers actually show.
Students write step-by-step instructions a computer can follow to solve a problem or automate a repetitive task, then test and refine those instructions until they work.
Students look at how computers and software shape everyday life, then weigh the real tradeoffs: who benefits, who gets left out, and what rules should govern how technology is built and used.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software Grades 6-8 | Students figure out which devices, programs, and fixes are the right fit for a given job. That means choosing the right tool and knowing what to try when something stops working. | ME-CSDF.C1.6-8 |
| Explain how computer networks and the Internet enable communication… Grades 6-8 | Students learn how the internet connects computers so people can share files, send messages, and work together, and why encryption and passwords help keep that data private. | ME-CSDF.C2.6-8 |
| Collect, transform, and represent data Grades 6-8 | Students gather raw data, organize it, and turn it into charts or summaries. Then they use software or spreadsheets to spot patterns and explain what the numbers actually show. | ME-CSDF.C3.6-8 |
| Design, develop, and analyze algorithms and programs to solve problems… Grades 6-8 | Students write step-by-step instructions a computer can follow to solve a problem or automate a repetitive task, then test and refine those instructions until they work. | ME-CSDF.C4.6-8 |
| Investigate the social, ethical, legal Grades 6-8 | Students look at how computers and software shape everyday life, then weigh the real tradeoffs: who benefits, who gets left out, and what rules should govern how technology is built and used. | ME-CSDF.C5.6-8 |
Students practice working with others who have different backgrounds and viewpoints when solving tech problems. The goal is to make sure everyone feels included and heard when the group is building or creating something together.
Students work in groups to plan, build, and improve a computing project, splitting up tasks and combining each person's work into a finished product.
Students look at a real problem, decide whether a computer could help solve it, and break it into smaller pieces that are each easier to tackle.
Students learn to spot patterns in a problem and use those patterns to write one solution that works in many situations, instead of solving the same problem from scratch each time.
Students write programs or build simulations by trying an idea, testing it, and improving it in repeated rounds. Each cycle teaches them something new about how their code works.
Students run planned tests on a program or app they built, find what breaks or confuses users, and fix it. The goal is a version that works correctly and is easier for someone else to use.
Students explain how a program or algorithm works using the right words, diagrams, or data. They describe not just what the code does but why it matters.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… Grades 6-8 | Students practice working with others who have different backgrounds and viewpoints when solving tech problems. The goal is to make sure everyone feels included and heard when the group is building or creating something together. | ME-CSDF.P1.6-8 |
| Collaborate around computing — divide work, share ideas Grades 6-8 | Students work in groups to plan, build, and improve a computing project, splitting up tasks and combining each person's work into a finished product. | ME-CSDF.P2.6-8 |
| Identify and define problems that can be solved with computation and decompose… Grades 6-8 | Students look at a real problem, decide whether a computer could help solve it, and break it into smaller pieces that are each easier to tackle. | ME-CSDF.P3.6-8 |
| Use abstractions to simplify complexity, generalise solutions Grades 6-8 | Students learn to spot patterns in a problem and use those patterns to write one solution that works in many situations, instead of solving the same problem from scratch each time. | ME-CSDF.P4.6-8 |
| Create computational artifacts — programs, simulations, models — by applying… Grades 6-8 | Students write programs or build simulations by trying an idea, testing it, and improving it in repeated rounds. Each cycle teaches them something new about how their code works. | ME-CSDF.P5.6-8 |
| Systematically test computational artifacts and refine them based on evidence… Grades 6-8 | Students run planned tests on a program or app they built, find what breaks or confuses users, and fix it. The goal is a version that works correctly and is easier for someone else to use. | ME-CSDF.P6.6-8 |
| Communicate clearly with appropriate vocabulary, visualizations Grades 6-8 | Students explain how a program or algorithm works using the right words, diagrams, or data. They describe not just what the code does but why it matters. | ME-CSDF.P7.6-8 |
Students write small programs, build simple websites or games, work with data in spreadsheets, and learn how the internet moves information. They also talk about how technology affects people, including privacy, copyright, and online safety.
No. Most students start middle school with very little coding experience. Teachers usually begin with block-based tools like Scratch before moving to text languages, so a student who has never written a line of code can still keep up.
Ask students to show what they built and explain how it works. Talking through the steps out loud is one of the most useful things a beginner programmer can do. Five minutes of curiosity from a parent goes a long way.
A common path is hardware and networks early, then programming and algorithms through the middle of the year, with data and societal impact woven in throughout. Save bigger projects for spring once students have the programming vocabulary to plan and test their own work.
Variables, loops, and conditionals tend to need several passes before they stick. Debugging is the other one. Students often guess and check instead of reading error messages, so plan short routines that force them to slow down and explain what the code is doing.
Students can break a problem into smaller steps, write a working program with loops and conditionals, test it, and fix what goes wrong. They can also explain how data moves on a network and discuss a real tradeoff, such as convenience versus privacy.
Not really. Building something on a computer uses different habits than scrolling or playing. That said, balance still matters. Ask what students made during a coding session, not just how long they sat at the screen.
Give each student a defined role and a short individual write-up explaining what they built, what they tested, and what they would change. The write-up surfaces who actually did the thinking and makes feedback specific to each student's work.
By the end of eighth grade, students should be able to plan a small program on paper, write it, test it, and explain their choices to someone else. If they can debug without giving up after the first error, they are in good shape.