A 20-week project where teams of community college students build a working, programmable 8-bit computer on breadboards from logic gates. Along the way, they encounter the physics, mathematics, linear algebra, differential equations, and chemistry that make it possible — not as separate subjects, but as the living foundation of the machine in front of them.
Every student uses a computer. Almost none understand how one works. Not at the level of “it has a processor and memory” — but at the level of why does flipping a switch produce a number. This gap is not a failure of student preparation. It is a failure of curriculum design. We teach computing through abstraction first, then wonder why students can’t connect the abstraction to anything real.
A computer is not a CS artifact. It is a STEM artifact. The clock module is an RC circuit — physics and differential equations. The ALU performs binary arithmetic — discrete mathematics. The control logic is a truth table realized in hardware — Boolean algebra and linear algebra. The semiconductors inside every chip are doped silicon — chemistry. When students build a computer from scratch, they don’t just learn CS. They encounter the foundations of every STEM course on their transcript, and they encounter them as necessary, not abstract. Jeff Anderson calls this “making math useful the moment it is introduced.” This project extends that principle across five disciplines simultaneously.
The structural principle is Perkins and Salomon’s transfer research: transfer does not happen automatically. It requires deliberate, explicit bridging — what Perkins and Salomon call “high road transfer.” Every module includes a “STEM Bridge Moment” where the instructor pauses the build to name the connection: “The equation governing this capacitor is the same first-order ODE you’ll solve in Math 1D. The truth table you just built for the control logic is a matrix operation you’ll formalize in Math 2B.” Without this bridging, students build a computer and learn CS. With it, they build a map of STEM — and they arrive in their next math, physics, or chemistry course having already touched the ideas with their hands.
The assessment philosophy follows Anderson’s ungrading framework: timed exams don’t reveal anything meaningful about learning. They measure anxiety management and test-taking strategy, not understanding. In this project, students build a learning portfolio, write structured self-reflections, and propose their own grade with evidence. The computer itself — working or not — is the most honest assessment instrument there is. It either adds correctly or it doesn’t. No partial credit. No curve. Just voltage.
A computer is a convergence point for five STEM disciplines. This project makes every connection explicit — giving students a head start in every course they take next. Anderson’s principle: math should be “useful the moment it is introduced.” Perkins and Salomon’s principle: transfer requires the instructor to name the bridge out loud. The map below shows every connection students encounter, and the bridge cards show the specific week each concept appears.
One person teaching CS to a camera. No connections to physics, math, or chemistry made explicit. No scaffolding for beginners. No collaboration. No structured reflection. No assessment of understanding. No metacognitive prompts. The most extraordinary CS education content ever produced — and structurally a solo, single-discipline experience that cannot reach the students who need it most.
Every module includes an explicit STEM Bridge Moment. Assessment is portfolio-based and ungraded — students propose their own grade with evidence. Reflection is structured around Kolb’s cycle. The track system honors student agency. The 555 timer IS the RC circuit from physics. The truth table IS Boolean algebra. The chip IS a chemistry artifact. Students leave with momentum for five courses, not one — and they leave knowing they built something real, not that they survived a test.
Jeff Anderson writes: “I work tirelessly to map every decision I make in my classroom back to research results in cognitive science, the psychology of learning, the science of expertise, and the scholarship of anti-racism and anti-oppression.” That standard governs this project. Seven bodies of research ground every structural decision. The seventh — Transfer Theory — is the foundation for the entire cross-STEM design.
Students learn most deeply when they build a public, shareable artifact. The construction is simultaneously external (the computer) and internal (the understanding).
The body is part of cognition. Physical manipulation produces deeper understanding than symbolic manipulation alone. Wiring circuits forms sensorimotor representations no simulation replicates.
New tools are meaningful only when they resolve a genuine need. A register appears as the answer to “how do we hold a number still while the ALU works?” — not as a vocabulary word.
Struggling before instruction produces deeper understanding and better transfer. Integration sessions are designed to fail first — the debugging IS the learning.
Learning is becoming a participant in a community of practice. Students do real engineering work, at a novice level, from Week 1. No distinction between learning and doing.
Intrinsic motivation requires autonomy (track choice), competence (scaffolded progression), and relatedness (team structure and exhibition). All three are structurally guaranteed.
Transfer does not happen automatically. “High road” transfer — the kind that lets a student recognize the RC circuit from their breadboard in a differential equations textbook — requires explicit bridging: the instructor names the connection, abstracts the principle, and prompts the student to look for it in future contexts. Without deliberate bridging, students build a computer and learn CS. With it, they build a map of STEM. This is the theoretical foundation for every STEM Bridge Moment in this project.
Each module is assigned to a team of 2–3 students. Inspired by Jeff Anderson’s choose-your-own-adventure approach to curriculum: students are not told “this math works, trust me.” They are asked “tell me how well this works and why.” Every module card shows what students build, the learning science principle in play, and the explicit STEM Bridge — the cross-disciplinary connection the instructor names during the build, using the exact language a student will hear again in their next STEM course.
A 555 timer producing a square wave. Students see that clock frequency is governed by a capacitor charging through a resistor — a physical process, not a setting.
Two 8-bit registers connected to a shared bus. A register holds a value as a pattern of high/low voltages — an 8-dimensional binary vector.
Two 74LS283 adders and XOR gates for two’s complement subtraction. Binary addition becomes physical reality on LEDs.
16 bytes of memory. The stored program concept becomes physical: behavior is voltage patterns in memory, not wiring.
EEPROM lookup table drives 7-segment displays. Students program the EEPROM with an Arduino — first code on hardware they built.
Three EEPROMs generate control signals. Students design microcode: a truth table mapping (instruction, step) → control signals. The lowest level of programming.
All modules integrate. Collaborative debugging. The computer runs Fibonacci — a recurrence relation solved in hardware, one clock tick at a time.
Every week includes a build session (2 hrs), concept session (1 hr), and reflection journal with “What other course does this connect to?” prompt. Key weeks with STEM bridge moments highlighted below.
Same computer, different depth of cross-STEM engagement. Tracks are not ability groups — they are depth choices. Anderson’s principle: learner-centered means the student determines their path, not the instructor. Track I students build a working module, document STEM connections, and present at exhibition — that is more real engineering than most exam-based courses produce in a full semester. Track III students formalize the connections mathematically and write research-quality technical papers. Both are serious, complete outcomes. Tracks are chosen weekly. No grade penalty for choosing Track I. Ever.
Build the module. Document it. Identify 3+ connections to other STEM courses in the build journal. Complete the Abuelita Test. Draw a personal STEM bridge map.
All of Track I, plus: read datasheets. Write the assembler. For each STEM bridge, solve one related problem from the connected discipline.
All of Track II, plus: write a technical paper formalizing one STEM bridge mathematically. Expand the instruction set. Connect the project to a textbook reading.
No exams. No quizzes. No letter grades assigned by the instructor. Following Jeff Anderson’s ungrading framework: timed exams measure anxiety and test-taking strategy, not learning. Instead, students build a learning portfolio across the semester, write structured self-reflections at midterm and end of term, and propose their own grade with evidence from their work. The build journal includes a “STEM Bridge” section each week. The computer either works or it doesn’t — the most honest assessment instrument there is.
Jeff Anderson — jeffandersonmath.wordpress.com · appliedlinearalgebra.com. Mathematics and Engineering instructor at Foothill College. Creator of the Applied Linear Algebra Fundamentals (ALAF) textbook, the Strategic Deep Learning framework, and a pioneering ungrading practice. Jeff’s five anti-racist, research-based, learner-centered learning objectives are the pedagogical foundation for this project’s assessment design, reflection structure, and commitment to serving the top 100% of learners. His work demonstrates that every classroom decision can and should map back to research in cognitive science, the psychology of learning, and the scholarship of anti-racism.
Ben Eater — eater.net/8bit. The 8-bit breadboard computer series. The direct technical foundation. Every student watches the first three videos before Week 1.
Nand2Tetris — nand2tetris.org. Nisan & Schocken. The Elements of Computing Systems. The full-stack narrative from NAND gates to Tetris. The intellectual aspiration: understand the entire stack, bottom to top. Track III reading.
Perkins & Salomon — “Teaching for Transfer” (Educational Leadership, 1988); “Transfer of Learning” (International Encyclopedia of Education, 1992). High road transfer requires deliberate abstraction and explicit connection-making. The theoretical backbone of the STEM Bridge design.
Seymour Papert — Mindstorms: Children, Computers, and Powerful Ideas (1980). The foundational text on constructionism: students learn most deeply when they build things that matter in the world. The reason this project uses physical breadboards, not simulators.
Manu Kapur — “Productive Failure in Mathematical Problem Solving” (Instructional Science, 2008, 2016). Why integration sessions are designed to fail first. The struggle before instruction produces deeper conceptual understanding and better transfer than direct instruction alone.
David Kolb — Experiential Learning: Experience as the Source of Learning and Development (1984). The four-phase cycle (experience → reflection → conceptualization → experimentation) structuring every weekly build session and every build journal entry.
Lave & Wenger — Situated Learning: Legitimate Peripheral Participation (1991). Learning is not the acquisition of propositions — it is the process of becoming a participant in a community of practice. Students do real engineering work from Week 1.
Deci & Ryan — Self-Determination Theory (1985, 2000). Intrinsic motivation requires autonomy, competence, and relatedness. The structural basis for the track system, the scaffolding progression, and the team-based design.
Guershon Harel — The DNR Framework: Duality, Necessity, Repeated Reasoning (2013). Mathematical concepts are meaningful only when they resolve a genuine intellectual need. The “Derive Before Compute” principle that governs how every module is introduced.
Code by Charles Petzold — The best popular book on how computers work. Recommended for all students who want the conceptual story alongside the physical build.
CS Unplugged — csunplugged.org. The Human Computer exercise (Week 9) is adapted from their activities. Free, equity-centered, and proven across hundreds of classrooms worldwide.