KES 001 · Computational Foundations with Python

From Curious Beginner to Computational Builder

KES 001 is an 8-week extended curriculum, also available as a 4-week intensive, that uses Python to help future engineers think computationally, build small systems, debug methodically, analyze data, simulate engineering problems, and present what they build.

  • 8 weeks extended
  • 4 weeks intensive option
  • Python + NumPy + matplotlib
  • Project-based
  • For engineers across disciplines
  • Think
  • Build
  • Compute
  • Show
THE PROMISE

What KES 001 Helps Learners Become

KES 001 does not promise to turn beginners into finished engineers in one module. It promises something more honest and more important: a learner who can think computationally, build small working systems from scratch, debug with a method, validate results, communicate their work, and continue into the next stage of the Kavana Labs Engineering Series with confidence.

01

Think computationally

Break fuzzy problems into precise steps.

02

Build from scratch

Create small working programs from an empty file.

03

Debug methodically

Read errors, isolate problems, test hypotheses, and fix issues.

04

Compute like an engineer

Use formulas, arrays, and plots to model engineering problems.

05

Validate results

Check outputs using sanity checks, known cases, units, and order of magnitude.

06

Communicate clearly

Document projects, explain design choices, and present results.

THE 8-WEEK ROADMAP

The Eight Week Curriculum Roadmap

KES 001 is designed as one curriculum that can run in two modes. The extended mode spreads the learning across approximately 8 weeks, giving learners more time for practice, reflection, and project work. The intensive mode compresses the same arc into 4 full-time weeks.

  1. 01
    Week 1Think

    Hello, Machine

    It’s not magic — I can make a computer do something.

    Learners are introduced to computation, simple Python programs, input/output, variables, values, and state.

    Topics
    • What a program is
    • Instructions and state
    • Running and editing code
    • Errors as messages
    • Values and variables
    • Basic types
    • Input and output
    • Units and simple sanity checks
    Learners build
    • Simple print/input programs
    • Unit converters
    • Basic engineering calculators

    OutcomeLearners can run code, edit code, use variables, and understand that errors can be read and fixed.

  2. 02
    Week 2Think

    Decisions, Loops, and Functions

    I can control what a program does and break problems into steps.

    Learners use decisions, repetition, and functions to build their first complete engineering calculator.

    Topics
    • if / elif / else
    • Comparisons and boolean logic
    • Edge cases
    • for loops
    • while loops
    • Accumulators
    • Functions
    • Parameters and return values
    • Decomposition
    • First GitHub commit
    Main deliverableMini-Project 1 — Engineering Calculator
    Example projects
    • Ohm’s Law calculator
    • Projectile range calculator
    • Half-life calculator
    • Unit converter
    • Energy consumption calculator
    • Dosage calculator

    OutcomeLearners build and publish their first complete program.

  3. 03
    Week 3Build

    Collections and Structured Data

    I can work with many values and model real-world information.

    Learners move from single values to collections and structured data.

    Topics
    • Lists
    • Indexing
    • Iteration over data
    • Mutation
    • Dictionaries
    • Key-value data
    • Records
    • List of dictionaries
    • Choosing the right data representation
    Learners build
    • Sensor reading processors
    • Material property lookups
    • Component inventories
    • Measurement records
    • Simple data summaries

    OutcomeLearners can represent and process collections of engineering data.

  4. 04
    Week 4Build

    Files, Debugging, and Small Systems

    I can build a thing with parts that work together.

    Learners build small systems that ingest, process, and save data.

    Topics
    • Reading files
    • Writing files
    • Simple CSV-style data
    • Input → process → output pipelines
    • Messy data
    • Error handling
    • Planning before coding
    • Systematic debugging
    • Reading tracebacks
    • Sanity checks
    • README writing
    Main deliverableWeekly Project 2 — Small Data Tool / CLI System
    Example projects
    • Lab data logger
    • Sensor reading analyzer
    • Parts inventory tool
    • Maintenance log tracker
    • Energy usage tracker
    • Production output summarizer

    OutcomeLearners build a documented command-line system that handles real or realistic data.

  5. 05
    Week 5Compute

    Arrays, Vectorized Thinking, and Visualization

    I can compute over many engineering quantities and visualize the result.

    Learners are introduced to the essential scientific Python toolkit: NumPy and matplotlib.

    Topics
    • NumPy arrays
    • Indexing and slicing
    • Elementwise math
    • Aggregation
    • Vectorized computation
    • matplotlib line plots
    • Scatter plots
    • Multiple series
    • Labels, units, and titles
    Learners build
    • Array-based engineering calculators
    • Plotted formulas
    • Trajectory plots
    • RC voltage curves
    • Decay curves
    • Stress-strain or load-deflection plots

    OutcomeLearners can use arrays and plots to communicate engineering computations clearly.

  6. 06
    Week 6Compute

    Real Engineering Data and Simulation

    I can analyze real data and simulate systems over time.

    Learners combine NumPy, plotting, data loading, and simulation patterns.

    Topics
    • Loading numeric data
    • Cleaning simple data issues
    • Summary statistics
    • Insight statements
    • Simulation loops
    • initialize → update → store → plot
    • Root-finding intuition
    • Numerical approximation
    • Validation against known cases
    Main deliverableWeekly Project 3 — Computational Engineering Tool
    Example projects
    • RC circuit simulator
    • Projectile motion visualizer
    • Radioactive decay model
    • Temperature or vibration data analyzer
    • Solar energy dataset analyzer
    • Drug concentration simulator
    • Production line throughput simulator

    OutcomeLearners build a computational engineering tool that computes, analyzes, or simulates a real problem in their discipline.

  7. 07
    Week 7Show

    Final Project: Scope and Build

    I can choose a real problem and build a working first version.

    Learners choose a meaningful final project, scope it carefully, and build the smallest end-to-end version.

    Topics
    • Project scoping
    • Compute / analyze / simulate project framing
    • MVP thinking
    • User need
    • Milestone planning
    • End-to-end-first building
    • Incremental development
    • GitHub build journal
    Learners build
    • Final project plan
    • Walking skeleton
    • Rough but working first version

    OutcomeLearners have a scoped final project and a working end-to-end prototype.

  8. 08
    Week 8Show

    Final Project: Validate, Document, and Demo

    I am a builder — here is proof.

    Learners improve, validate, document, and publicly present their final project.

    Topics
    • Robustness
    • Edge cases
    • Bad input handling
    • Sanity checks
    • Known-case validation
    • Refactoring
    • README writing
    • Technical storytelling
    • Demo preparation
    • Reflection
    • Personal learning roadmap toward KES 002
    Main deliverableFinal Project + Demo Day

    OutcomeLearners leave with a documented, validated, discipline-relevant project, a public demo, and a clear next step.

TWO DELIVERY MODES

How the Four Week Intensive Mode Maps to the Eight Week Roadmap

Both modes teach the same curriculum and produce the same projects. The intensive mode runs full-time over 4 weeks; the extended mode spreads each intensive week across two part-time weeks for more spacing, reflection, and practice. The learning arc is identical — Think → Build → Compute → Show.

Intensive Week 1Extended Weeks 1–2
Think & make things workDeliverableMini-Project 1 — Engineering Calculator
Intensive Week 2Extended Weeks 3–4
Build small systems & handle dataDeliverableWeekly Project 2 — Data Tool / CLI System
Intensive Week 3Extended Weeks 5–6
Compute like an engineerDeliverableWeekly Project 3 — Computational Engineering Tool
Intensive Week 4Extended Weeks 7–8
Build something real & show itDeliverableFinal Project + Demo Day

Same curriculum, same projects — only the pace changes. The advertised cohort is the 8-week extended mode.

WHAT LEARNERS BUILD

What Learners Build

KES 001 is organized around three universal computational engineering patterns: compute, analyze, and simulate. These patterns appear across electrical, mechanical, biomedical, nuclear, aerospace, chemical, civil, software, energy, and industrial engineering.

Compute

Build calculators and tools from known engineering relationships.

Examples
  • Ohm’s Law calculator
  • Projectile range calculator
  • Beam deflection calculator
  • Half-life calculator
  • Ideal gas law explorer
  • Energy bill estimator

Analyze

Turn measurements, logs, and datasets into summaries, insights, and visualizations.

Examples
  • Sensor data analyzer
  • Voltage/current trace analyzer
  • Temperature log visualizer
  • Detector count analyzer
  • Production output report
  • Energy dataset analyzer

Simulate

Model how a system changes over time and observe its behavior.

Examples
  • RC circuit simulator
  • Projectile motion simulator
  • Radioactive decay simulator
  • Drug concentration simulator
  • Cooling object simulator
  • Production line simulator
DAY-BY-DAY CURRICULUM

Day by Day Curriculum

The intensive version has 20 instructional days. In the extended version, these same days are distributed across approximately 8 weeks. Expand a block to see its days; expand a day for objectives, core concepts, lab focus, and the outcome.

PROJECT PORTFOLIO

Every Learner Leaves With Proof

By the end of KES 001, each learner has a small project portfolio showing their growth from beginner to computational builder.

Mini-Project 1

Engineering Calculator

A small interactive calculator based on a provided engineering formula.

Demonstrates
  • input/output
  • variables
  • decisions
  • loops
  • functions
  • first GitHub commit
Weekly Project 2

Data Tool / CLI System

A small command-line system that ingests, processes, and saves data.

Demonstrates
  • lists
  • dictionaries
  • file handling
  • simple data processing
  • error handling
  • README writing
Weekly Project 3

Computational Engineering Tool

A NumPy/matplotlib-based calculator, analyzer, or simulator in the learner’s discipline.

Demonstrates
  • arrays
  • vectorized computation
  • plots
  • engineering modeling
  • validation
  • technical demo
Final Project

Capstone + Demo Day

A self-chosen, discipline-relevant project built, documented, validated, and presented publicly.

Demonstrates
  • scoping
  • end-to-end development
  • robustness
  • communication
  • ownership
  • builder identity
OPERATING MODEL

How KES 001 Runs

KES 001 uses a daily rhythm designed around building, feedback, reflection, and community.

01

Standup

Learners state yesterday’s win, today’s commitment, and any blocker.

02

Concept Block

Short active lesson or live coding session. No long lectures.

03

Build Block

Learners work on labs, challenges, and projects with coaching support.

04

Code Review

Peers and mentors review real code and give specific feedback.

05

Demo / Share

Learners show what they built or explain a bug they fixed.

06

Reflection

Learners document what worked, what broke, and what they learned.

The extended 8-week version follows the same arc at a part-time pace, with between-session build prompts and pod check-ins.

EVALUATION

How Learners Are Evaluated

KES 001 does not rely on high-stakes written exams. Learners are evaluated through authentic evidence: projects, demos, code reviews, GitHub history, documentation, reflection, and a final “defend your build” conversation.

Evaluation domains
  • Implementation and building
  • Computational and engineering thinking
  • Debugging and robustness
  • Computation, modeling, and visualization
  • Communication and documentation
  • Growth and learning
  • Collaboration and community contribution
Completion outcomes

Completed KES 001

Learner participated and shipped all major projects.

Ready for KES 002

Learner can build small systems, compute/analyze/simulate with arrays and plots, debug methodically, and explain their work.

Fellowship Signal

Learner shows strong growth, independent learning, quality work, and community contribution.

SCOPE

What This Curriculum Is Not

KES 001 is not a web development bootcamp, not a full Python developer course, and not a shortcut to becoming an engineer. It is the first foundation in the Kavana Labs Engineering Series.

KES 001 does not cover
  • Web frameworks
  • Databases
  • Advanced object-oriented programming
  • Machine learning
  • pandas, SciPy, or scikit-learn
  • App development
  • Cloud deployment
  • Advanced algorithms
  • Discipline-specific professional simulation packages

These belong in later KES modules. KES 001 deliberately teaches a small toolkit deeply.

THE KES BUILDER ETHOS

I read the error before I panic.

I try before I ask — and when I ask, I bring what I tried.

I build the smallest thing that works, then make it better.

I don’t trust a number until I’ve checked it.

I ship and I show.

I help my pod.

I build to understand.

READY TO START BUILDING?

Ready to Start Building?

KES 001 is for learners who want to stop only consuming technology and start building with it. It is the first step in the Kavana Labs Engineering Series — a foundation for future engineers, researchers, builders, and problem-solvers.