Intro to Coding Curriculum

Public curriculum preview for visitors and enrolled students. Use this page to evaluate module scope, outcomes, and learning path.

Curriculum

Intro to Coding

Your first steps into programming: variables, logic, and writing your first code.

Duration: 12 Weeks
Level: Beginner
Study Time: 2 hours/week + labs
School: Hexadigitall Academy

Welcome to Intro to Coding! 🎓

This curriculum is designed to take you from core understanding to confident delivery through weekly applied practice, measurable outcomes, and portfolio evidence.

Each week builds progressively with practical tasks, implementation checkpoints, and reflection points so you can convert knowledge into repeatable professional performance.

Your success is our priority. Stay consistent with weekly execution, document your work, and use feedback loops to continuously improve your delivery quality.

Essential Resources

  • Project Charter template, WBS examples, and stakeholder analysis worksheets
  • Risk register, change log, and lessons learned repository templates
  • ROI calculation models, benefits tracking dashboards, and governance frameworks

Learning Roadmap

  • Early Weeks: Project fundamentals, planning, and stakeholder management
  • Middle Weeks: Execution excellence, risk management, and adaptive strategies
  • Late Weeks: Delivery validation, lessons learned, and strategic impact
  • Loops and Repetition Patterns
  • Functions and Reusable Code Blocks
  • Lists, Objects, and Basic Data Structures
  • Debugging, Errors, and Reading Stack Messages
  • User Input, Validation, and Program Flow
  • Working with Files or Simple Persistent Data
  • Building a Small Console or Browser Project
  • Refactoring, Naming, and Clean Beginner Code
  • Capstone: Build and Present Your First Working App

Detailed Weekly Curriculum

Each week includes outcomes and practical lab work aligned to the curriculum structure.

Week 1

How Programs Work: Input, Output, and Instructions

2 hours/week + labs
Learning Outcomes
  • Identify the principles of How Programs Work: Input, Output, and Instructions and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain How Programs Work: Input, Output, and Instructions in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for How Programs Work: Input, Output, and Instructions, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for How Programs Work: Input, Output, and Instructions with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 2

Variables, Data Types, and Operators

2 hours/week + labs
Learning Outcomes
  • Identify the principles of Variables, Data Types, and Operators and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Variables, Data Types, and Operators in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Variables, Data Types, and Operators, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Variables, Data Types, and Operators with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 3

Conditions and Boolean Logic

2 hours/week + labs
Learning Outcomes
  • Identify the principles of Conditions and Boolean Logic and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Conditions and Boolean Logic in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Conditions and Boolean Logic, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Conditions and Boolean Logic with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 4

Loops and Repetition Patterns

2 hours/week + labs
Learning Outcomes
  • Identify the principles of Loops and Repetition Patterns and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Explain Loops and Repetition Patterns in a guided scenario using realistic tools, constraints, and quality gates.
  • Apply trade-offs, risks, and decision points for Loops and Repetition Patterns, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Loops and Repetition Patterns with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 5

Functions and Reusable Code Blocks

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Functions and Reusable Code Blocks and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Functions and Reusable Code Blocks in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Functions and Reusable Code Blocks, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Functions and Reusable Code Blocks with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 6

Lists, Objects, and Basic Data Structures

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Lists, Objects, and Basic Data Structures and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Lists, Objects, and Basic Data Structures in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Lists, Objects, and Basic Data Structures, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Lists, Objects, and Basic Data Structures with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 7

Debugging, Errors, and Reading Stack Messages

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Debugging, Errors, and Reading Stack Messages and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze Debugging, Errors, and Reading Stack Messages in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Debugging, Errors, and Reading Stack Messages, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Debugging, Errors, and Reading Stack Messages with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 8

User Input, Validation, and Program Flow

2 hours/week + labs
Learning Outcomes
  • Apply the principles of User Input, Validation, and Program Flow and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Analyze User Input, Validation, and Program Flow in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for User Input, Validation, and Program Flow, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for User Input, Validation, and Program Flow with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 9

Working with Files or Simple Persistent Data

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Working with Files or Simple Persistent Data and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Working with Files or Simple Persistent Data in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Working with Files or Simple Persistent Data, then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Working with Files or Simple Persistent Data with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 10

Building a Small Console or Browser Project

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Building a Small Console or Browser Project and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Building a Small Console or Browser Project in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Building a Small Console or Browser Project, then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Building a Small Console or Browser Project with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 11

Refactoring, Naming, and Clean Beginner Code

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Refactoring, Naming, and Clean Beginner Code and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Refactoring, Naming, and Clean Beginner Code in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Refactoring, Naming, and Clean Beginner Code, then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Refactoring, Naming, and Clean Beginner Code with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 12

Capstone: Build and Present Your First Working App

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Capstone: Build and Present Your First Working App and link them to course outcomes with scaffolded guidance and beginner-safe checkpoints.
  • Evaluate Capstone: Build and Present Your First Working App in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Capstone: Build and Present Your First Working App, then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Capstone: Build and Present Your First Working App with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.

Capstone Projects

Project 1: Beginner Utility Program

Create a practical console utility (calculator, grade checker, or unit converter) with clear logic flow.

  • Input handling, conditional logic, and looping behavior
  • Function-based structure with readable naming
  • Test outputs that confirm expected behavior

Project 2: Data-Driven Mini App

Build a small records app that stores and retrieves structured data from files.

  • Create, read, update, and delete style operations
  • Validation and error handling for invalid input
  • Bug-fix log and concise implementation notes

Project 3: Final Coding Capstone

Deliver and present a complete beginner application demonstrating end-to-end coding competency.

  • Integrated use of all core programming fundamentals
  • Cleaned codebase with run instructions
  • Presentation notes and improvement roadmap