Ready to try · 6 sections
Train your first AI model
Start with I²R. Make examples, train a tree and find where it goes wrong.
Keep: A first regression tree and a reason to keep the equation.
Open lesson →The learning path
Start without code. Build your first model, explore its limits and choose a useful engineering question.
Block A, lessons 1 to 4, is available now. Blocks B to F are coming soon while I review them. Work through the available lessons in order.
The lessons build on each other, from your first model to a tool you can use again.
Your account →The newsletter is optional and has its own signup.
Complete each lesson to unlock the next. Your account status is being checked.
Follow your progress from a guided example to a result you can use again.
These milestones record completed course practice. A different case or another person reproducing your work provides further evidence; progress alone does not measure independent mastery or certify a model.
Make a first model and choose a useful engineering question.
Ready to try · 6 sections
Start with I²R. Make examples, train a tree and find where it goes wrong.
Keep: A first regression tree and a reason to keep the equation.
Open lesson →Checking your progress · 5 sections
Find a gap in your examples, spend a small data budget and check what actually changes.
Keep: Save a coverage map and compare the original, reduced and added-example models on the same validation currents.
Checking your progress · 5 sections
Plan how to check a model on a new component design, then see why a different split answers a different question.
Keep: Save a complete design partition map and explain which evaluation supports the intended use, while keeping reserved designs out of both comparisons.
Checking your progress · 6 sections
Turn an engineering idea into a brief that says what answer you need, how you will check it and when to request more work.
Keep: Download a practical brief with a decision, available inputs, simple reference, success criterion and limits, using the conduction-loss example to define the target.
Bring the four lessons together: upload a converter simulation table, train and compare two estimators, check a complete new design and hand over an honest scope.
Keep: a working estimator, its prediction files and a use card that explains where it can—and cannot—be used.
Repair a dataset and check an estimator against a simple reference.
Coming soon · 6 sections
Read a real teaching CSV, follow one simulated run and record what every column means.
Keep: Download a data dictionary with column roles, units, row meaning and the source of the reference values.
Coming soonComing soon · 6 sections
Repair a deliberately damaged CSV using its original run records, keeping a reason for each change.
Keep: Download five repaired teaching rows and a cleaning log that preserves their source and meaning.
Coming soonComing soon · 6 sections
Train two estimators, compare them with a constant and an engineering equation, and inspect where they fail.
Keep: Save a four-method comparison with errors in watts, physical checks and a clearly stated simulation scope.
Coming soonComing soon · 6 sections
Use validation for experiments, then freeze a choice before opening its final check.
Keep: Save a frozen model choice, a declared tolerance and a clearly labelled evaluation report.
Coming soonRun, change and download your own working notebook.
Coming soon · 6 sections
Run a calculation, change it, understand an error and reproduce your work.
Keep: Keep an editable notebook that calculates resistor losses from a clean start.
Coming soonComing soon · 6 sections
Build a small calculation that accepts values, returns watts and refuses invalid inputs.
Keep: Write and test a reusable loss function with explicit units and a declared range.
Coming soonComing soon · 6 sections
Read a small table, select comparable rows, convert units and draw your own graph.
Keep: Keep a notebook, a plot generated by Python and a transformed CSV with clear units.
Coming soonComing soon · 6 sections
Connect a small training pipeline to a CSV, then adapt the inputs and retrain.
Keep: Keep a notebook that trains on grouped teaching data and exports predictions for another CSV.
Coming soonTurn documented simulation runs into useful inputs and predictions.
Coming soon · 6 sections
Trace a training row back to the converter settings, simulation run and extraction window that produced it.
Keep: Save a dataset manifest with accepted runs, exclusions and a precise reference definition.
Coming soonComing soon · 6 sections
Choose valid operating conditions and discover gaps that simple minimum and maximum checks can miss.
Keep: Save a sampling plan with a data budget, reserved groups and a written domain of use.
Coming soonComing soon · 6 sections
Select a meaningful time window and calculate waveform summaries that you can check by hand.
Keep: Save a reproducible feature table with units, window boundaries and execution groups.
Coming soonComing soon · 6 sections
Approximate a declared simulation output and compare the result with a physical reference inside its domain.
Keep: Save a conduction-loss estimator, its comparison and the conditions that need simulation review.
Coming soonCompare models, inspect mistakes and recognise unsupported predictions.
Coming soon · 6 sections
Build a binary review-priority classifier using a declared ripple rule and inspect the mistakes it makes.
Keep: Save a logistic_regression classifier, its rule comparison and examples of misclassified runs.
Coming soonComing soon · 6 sections
Move a review threshold on validation and see how missed cases and unnecessary flags change.
Keep: Save a threshold choice with its assumptions, observed counts and reserved-evaluation plan.
Coming soonComing soon · 6 sections
Compare a small number of ensemble models fairly, then judge whether their extra complexity is worthwhile.
Keep: Save a reproducible comparison covering grouped validation, errors, stability and observed runtime.
Coming soonComing soon · 6 sections
Turn known model limits into explicit rules for accepting an input, requesting review or declining a prediction.
Keep: Save use and abstention rules with cases that demonstrate how the rules behave.
Coming soonChoose data, freeze a model and deliver a reusable tool.
Coming soon · 6 sections
Spend a limited simulation budget on a development question, then check whether the new information helped.
Keep: Save a candidate-request plan and a fair before-and-after validation comparison.
Coming soonComing soon · 6 sections
Adapt a real modelling decision and prepare a complete candidate for a later independent check.
Keep: Save your problem brief, data contract, comparison and frozen pipeline with a declared acceptance rule.
Coming soonComing soon · 6 sections
Save a complete model, start clean and use it on a new CSV with clear handling of invalid requests.
Keep: Download a reusable package containing the model, code, example inputs and instructions.
Coming soonComing soon · 6 sections
Evaluate a frozen tool on new cases and decide whether its evidence supports the proposed engineering use.
Keep: Deliver a reproducible tool and a use card with a defensible acceptance or insufficiency decision.
Coming soonKeep the engineering in view
The first exercises use equations. Later lessons use a documented teaching simulation of a buck converter. Neither is a hardware measurement. A simple physical calculation may still be your best tool.