Part 08 of 18

Electrical and Electronic Engineering

1. Purpose of This Part

This part defines the Electrical and Electronic Engineering roadmap. Electrical and Electronic Engineering is one of the most important practical domains in the master plan because it connects physics, mathematics, quantum hardware, embedded systems, PCB design, semiconductors, instrumentation, control, signal processing, and real physical building.

The goal is not merely to “study electronics.”

The goal is:

To rebuild EEE from the ground up until theory becomes circuits, circuits become measurements, measurements become debugging, and debugging becomes working hardware.

This matters because the original brief states that EEE was studied before at Level 5 diploma level, but much of it was forgotten or never truly learned, especially the mathematical and practical building side. The goal now is not theory alone, but actually designing circuits, building projects, designing complex PCBs, and understanding semiconductor fabrication at serious depth.

EEE in this plan must become:

circuit analysis
circuit simulation
breadboard experiments
measurement logs
datasheet reading
component selection
embedded programming
PCB design
hardware debugging
semiconductor understanding
fabrication awareness
instrumentation skill
hardware/software integration
quantum hardware preparation

The standard is:

Can I design it, simulate it, build it, measure it, debug it, document it, and explain why it works?

2. What EEE Competence Actually Means

EEE competence is not knowing component names.

It is not collecting Arduino boards.

It is not watching someone else wire a circuit.

It is not drawing a schematic that has never been tested.

Real EEE competence means being able to move between:

physical components
circuit symbols
equations
simulation
datasheets
breadboards
PCBs
test equipment
firmware
measurements
failures
revisions
documentation

A serious electronics builder asks:

What is this circuit supposed to do?
What are the input and output signals?
What voltage and current levels are involved?
What is the power budget?
What components are required?
What are the tolerances?
What does the datasheet say?
What happens at startup?
What happens at failure?
What happens if the load changes?
What happens with noise?
What does the simulator predict?
What does the oscilloscope show?
Why does the real circuit differ from the ideal circuit?
Can this be manufactured?
Can this be repaired?

The standard is not:

    “Can I copy a circuit diagram?”

The standard is:

  Can I understand, design, test, and improve the circuit myself?

3. The Research-Backed Source Spine

The EEE roadmap should use a combination of textbooks, university courses, official documentation, simulation tools, datasheets, and hardware practice.

The main source spine is:

MIT OCW 6.002 Circuits and Electronics for serious circuit foundations. MIT describes

6.002 as a first undergraduate course in electrical engineering or EECS, introducing the fundamentals of the lumped circuit abstraction. Its syllabus includes understanding electrical engineering principles such as lumped circuit models, digital circuits, operational amplifiers, using abstractions to analyze/design simple circuits, and solving differential equations for circuits with energy-storage elements. (MIT OpenCourseWare)

Electronic Devices and Circuit Theory by Robert L. Boylestad and Louis

Nashelsky for semiconductor devices and applied electronics. Pearson describes it as a complete, comprehensive survey focused on essentials students need for electronic devices and circuit applications. (Pearson)

All About Circuits textbook as a free multi-volume electronics textbook. All About

Circuits describes it as covering electricity and electronics, originally written by Tony R. Kuphaldt and updated/reformatted by All About Circuits. (All About Circuits)

LTspice for analog circuit simulation. Analog Devices describes LTspice as a powerful,

fast, free SPICE simulator with schematic capture and waveform viewing, including enhancements and models for analog circuit simulation. (Analog Devices)

KiCad for schematic capture and PCB design. KiCad describes itself as a free and

open-source electronics design automation suite with schematic capture, integrated circuit simulation, PCB layout, 3D rendering, and plotting/export tools. (KiCad Documentation)

Arduino official documentation for beginner-to-intermediate microcontroller and

embedded projects. Arduino’s documentation includes getting started guides, hardware tutorials, and ecosystem learning materials. (Arduino Docs)

Raspberry Pi Pico / RP2040 documentation for deeper microcontroller and embedded

work. Raspberry Pi documents Pico boards and RP2040/RP2350 microcontrollers as microcontroller platforms for real-time tasks such as controlling motors and reading sensors. (Raspberry Pi)

MIT OCW Physics of Microfabrication: Front End Processing for the semiconductor

fabrication bridge. MIT describes this graduate course as focused on front-end processes used in silicon integrated circuit fabrication, including oxidation, diffusion, ion implantation, and epitaxy. (MIT OpenCourseWare)

The rule is:

Textbooks teach the theory. Simulators test the idea. Breadboards expose reality. Instruments reveal truth. PCBs force discipline. Datasheets prevent fantasy.

4. The EEE Builder Identity

The identity to build here is:

     Hardware systems builder.

A hardware systems builder does not only know theory.

They can turn electrical ideas into physical systems.

They understand that hardware is unforgiving.

Code can often be patched quickly.

Hardware mistakes can burn components, waste boards, mislead measurements, damage equipment, or create safety risks.

This means hardware requires patience, precision, and documentation.

A hardware systems builder respects:

● voltage ● current ● power ● heat ● noise ● grounding ● tolerances ● datasheets ● physical layout ● measurement ● safety ● manufacturing constraints ● debugging reality

The long-term goal is not only to wire hobby circuits. The goal is to become capable of serious hardware thinking:

analog circuits
digital systems
embedded systems
sensors
PCBs
semiconductor devices
signal processing
control systems
hardware-software integration
quantum hardware foundations

5. The EEE Roadmap Ladder

The roadmap is divided into layers.

Each layer must produce artifacts.

Do not move forward only because a chapter was read.

Move forward when the evidence shows competence: working circuits, simulations, measurement logs, schematics, PCB files, firmware, and postmortems.

Layer 0 — Electrical Safety, Lab Discipline,

and Instrumentation Mindset Purpose Before circuits become complex, the lab mindset must be established.

EEE work involves real voltages, currents, heat, batteries, power supplies, and components that can fail. Even low-voltage systems can overheat, short, damage equipment, or behave unpredictably.

This layer creates safe habits. Topics

voltage/current/power safety
short circuits
current limiting
fuses
heat
polarity
batteries
ESD basics
grounding
lab notebook discipline
power supply usage
multimeter usage
oscilloscope basics
function generator basics
breadboard limitations
component handling
measurement uncertainty

Required Artifacts Create:

Electronics safety checklist
Lab equipment setup guide
Multimeter practice log
Oscilloscope practice log
Power supply current-limit guide
Component storage system
Measurement notebook template
“What can go wrong?” hardware checklist
ESD and component handling notes
First lab notebook entry

Completion Standard This layer is complete when:

a bench power supply can be used safely
voltage/current/resistance can be measured
oscilloscope basics are understood
components are stored and labeled
every build has a lab note
safety checks happen before powering a circuit

Layer 1 — Electricity and Circuit

Fundamentals Purpose This layer rebuilds the foundation: charge, voltage, current, resistance, power, and basic circuit laws.

Without this, electronics becomes memorized rituals.

MIT 6.002 is useful here because it introduces the lumped circuit abstraction and first-principles circuit analysis for undergraduate EE/EECS students. (MIT OpenCourseWare)

Topics

charge
current
voltage
resistance
conductance
power
energy
Ohm’s law
Kirchhoff’s Current Law
Kirchhoff’s Voltage Law
series circuits
parallel circuits
voltage dividers
current dividers
source models
Thevenin equivalent
Norton equivalent
superposition
dependent sources
nodal analysis
mesh analysis Required Artifacts Create:

Circuit fundamentals notebook
Ohm’s law measurement lab
Series/parallel resistor lab
Voltage divider lab
Current measurement lab
Power dissipation calculation sheet
Nodal analysis problem set
Thevenin/Norton problem set
LTspice basic circuit simulations
“Voltage vs current vs power” explanation essay

Project Ideas Build:

resistor measurement board
voltage divider reference board
LED resistor calculator
simple continuity tester
power dissipation calculator
web/Python circuit calculator

Completion Standard This layer is complete when:

voltage, current, resistance, and power are distinct and meaningful
KCL and KVL are usable
simple circuits can be analyzed by hand
simulations match calculations
measurements are compared against predictions
power dissipation is considered before building

Layer 2 — Passive Components and

Real-World Non-Ideal Behavior Purpose Real components are not ideal textbook symbols.

Resistors have tolerance and power ratings.

Capacitors have leakage, ESR, voltage ratings, and frequency behavior.

Inductors have resistance, saturation, and parasitics.

This layer teaches real-world component behavior.

Topics

resistor tolerance
resistor power rating
potentiometers
capacitors
capacitance
ESR
leakage
capacitor voltage rating
ceramic vs electrolytic capacitors
inductors
inductance
inductor saturation
parasitic resistance
impedance
frequency response
real component datasheets
temperature effects
tolerances

Required Artifacts Create:

Passive component notebook
Resistor tolerance measurement log
Capacitor charge/discharge lab
RC time constant experiment
Inductor behavior notes
Datasheet reading notes for resistors/capacitors/inductors 7. LTspice RC/RL simulation

8. Real vs simulated RC curve comparison 9. Component selection checklist 10.“Ideal vs real components” essay

Completion Standard This layer is complete when:

● passive components can be selected intentionally ● tolerances and ratings are considered ● RC and RL behavior is understood ● datasheets are no longer ignored ● real measurements are compared with ideal predictions

Layer 3 — Time-Domain Circuits:

Capacitors, Inductors, and Differential Equations Purpose Capacitors and inductors introduce memory into circuits.

This is where circuits begin to involve differential equations, transients, filters, oscillations, and energy storage.

MIT 6.002 explicitly includes formulating and solving differential equations that describe time behavior in circuits with energy-storage elements. (MIT OpenCourseWare)

Topics

● RC transients ● RL transients ● RLC circuits ● natural response ● forced response ● time constants

step response
impulse response basics
damping
resonance
energy in capacitors
energy in inductors
first-order circuits
second-order circuits
differential equations in circuits

Required Artifacts Create:

RC transient notebook
RL transient notebook
RLC resonance notebook
Capacitor charging measurement lab
Inductor transient lab
LTspice transient analysis project
Oscilloscope screenshots of real transients
Differential equation derivation notes
Simulation vs measurement comparison report
“Circuits as dynamic systems” essay

Completion Standard This layer is complete when:

time constants are meaningful
first-order circuit behavior can be predicted
RLC resonance is understood
differential equations connect to real circuits
oscilloscope traces can be interpreted
simulations and measurements are compared honestly

Layer 4 — AC Circuits, Impedance,

Phasors, and Frequency Response Purpose AC analysis is essential for signals, filters, power, audio, RF, communication, and quantum hardware electronics.

This layer connects complex numbers, sinusoidal signals, impedance, and frequency behavior.

Topics

sinusoidal signals
amplitude
frequency
phase
RMS values
complex numbers
impedance
reactance
phasors
capacitive impedance
inductive impedance
AC power basics
filters
low-pass filters
high-pass filters
band-pass filters
Bode plots
frequency response
resonance
transfer functions

Required Artifacts Create:

AC circuits notebook
Phasor practice set
Complex impedance problem set
RC filter lab
RL/RLC filter simulation
Bode plot notebook
Function generator + oscilloscope frequency response lab
Audio filter project
LTspice AC analysis project
“Why complex numbers are useful in electronics” essay

Completion Standard This layer is complete when:

AC signals can be represented mathematically
impedance is meaningful
phasors can be used in simple analysis
filters can be designed and tested
Bode plots can be interpreted
frequency response can be measured

Layer 5 — Semiconductor Devices:

Diodes, BJTs, FETs, and Device Physics Purpose This layer is where electronics moves from passive circuits into active devices.

Boylestad and Nashelsky’s Electronic Devices and Circuit Theory should be a main source here because it focuses on electronic devices and circuit applications in a comprehensive way. (Pearson)

Topics

semiconductor basics
electrons and holes
doping
p-type and n-type material
p-n junctions
diodes
rectifiers
Zener diodes
LEDs
photodiodes
BJTs
transistor biasing
transistor switching
transistor amplification
JFETs
MOSFETs
MOSFET switching
MOSFET power dissipation
small-signal models
device datasheets
safe operating area
thermal behavior

Required Artifacts Create:

Semiconductor devices notebook
Diode I-V curve measurement lab
Rectifier circuit lab
Zener voltage regulator lab
LED driver notes
BJT switch lab
BJT amplifier simulation
MOSFET switching lab
MOSFET datasheet study
“Transistors as switches vs amplifiers” essay

Project Ideas Build:

bridge rectifier supply
LED constant-current driver
transistor switch board
MOSFET motor switch
light sensor circuit
simple audio amplifier
temperature-controlled fan switch

Completion Standard This layer is complete when:

p-n junction behavior is understood
diodes can be selected and used properly
BJTs and MOSFETs are distinguishable
transistors can be used as switches
basic amplifier behavior is understood
datasheets guide component choices

Layer 6 — Operational Amplifiers and

Analog Building Blocks Purpose Op-amps are one of the most important building blocks in analog electronics.

They appear in filters, amplifiers, sensor interfaces, active rectifiers, comparators, oscillators, instrumentation circuits, and control systems.

MIT 6.002 includes operational amplifiers as part of its core circuit abstraction outcomes, making this a natural continuation of circuit foundations. (MIT OpenCourseWare)

Topics

ideal op-amp assumptions
real op-amp limitations
inverting amplifier
non-inverting amplifier
voltage follower
summing amplifier
differential amplifier
instrumentation amplifier
comparator
active filters
integrators
differentiators
offset voltage
input bias current
slew rate
gain-bandwidth product
power rails
saturation
common-mode range
op-amp datasheets

Required Artifacts Create:

Op-amp fundamentals notebook
Inverting amplifier lab
Non-inverting amplifier lab
Voltage follower lab
Comparator lab
Active filter simulation
Instrumentation amplifier notes
Op-amp datasheet study
Real op-amp limitation report
“Why ideal op-amps lie” essay

Project Ideas Build:

microphone preamp
active low-pass filter
signal conditioning board
comparator threshold detector
sensor amplifier
simple function generator
op-amp based oscillator

Completion Standard This layer is complete when:

basic op-amp circuits can be analyzed
feedback is understood
real op-amp limitations are considered
op-amp circuits can be simulated and measured
datasheets are used before choosing parts

Layer 7 — Digital Electronics and Logic

Purpose Digital electronics connects hardware to computation.

This layer builds the foundation for microcontrollers, FPGAs, computer architecture, embedded systems, and digital interfaces.

Topics

binary
logic levels
Boolean algebra
logic gates
truth tables
combinational logic
multiplexers
decoders
encoders
flip-flops
latches
registers
counters
clocks
timing
propagation delay
setup and hold time
pull-up/pull-down resistors
debouncing
logic families
level shifting
digital interfaces basics

Required Artifacts Create:

Digital logic notebook
Boolean algebra problem set
Logic gate truth-table lab
Combinational circuit design
Flip-flop notes
Counter circuit simulation
Button debouncing lab
Level shifting notes
Timing diagram practice
“From logic gates to computation” essay

Project Ideas Build:

logic gate trainer
binary counter
digital dice
debounce circuit
simple state machine
seven-segment display driver
basic ALU simulation

Completion Standard This layer is complete when:

Boolean logic is usable
combinational/sequential logic are distinguishable
timing matters are understood
simple digital circuits can be built
digital signals can be measured on an oscilloscope or logic analyzer

Layer 8 — Embedded Systems and

Microcontrollers Purpose Embedded systems are where software controls hardware.

This layer combines electronics, programming, sensors, timing, communication, power, and debugging. Arduino is useful for early embedded work because its documentation provides official getting-started and tutorial materials. Raspberry Pi Pico/RP2040 is useful for moving deeper into microcontroller documentation and real embedded systems practice. (Arduino Docs)

Topics

microcontroller architecture basics
GPIO
digital input/output
analog input
PWM
ADC
DAC basics
timers
interrupts
UART
I2C
SPI
debouncing
sensor reading
actuator control
motors
displays
power management
sleep modes
firmware structure
debugging embedded systems
datasheets and reference manuals

Required Artifacts Create:

Arduino basics project log
GPIO input/output lab
PWM LED dimming lab
Button debounce firmware
ADC sensor reading project
UART communication demo
I2C sensor project
SPI display or sensor project
Raspberry Pi Pico/RP2040 project
Embedded debugging checklist Project Ideas Build:

temperature logger
environmental sensor station
motor controller
smart desk light
simple robot platform
electronic safe/lock
data logger
OLED display dashboard
IoT sensor node later
embedded study timer

Completion Standard This layer is complete when:

microcontrollers can read sensors and control outputs
firmware can be structured clearly
serial debugging is comfortable
datasheets are used
communication protocols are understood at a practical level
hardware and software failures can be distinguished

Layer 9 — Sensors, Instrumentation, and

Measurement Systems Purpose Many useful electronic systems exist to measure the world.

Sensors convert physical phenomena into electrical signals.

Instrumentation makes those signals accurate, useful, and interpretable.

Topics

sensor types
temperature sensors
light sensors
pressure sensors
accelerometers
gyroscopes
microphones
current sensors
voltage sensors
strain gauges
Wheatstone bridge
signal conditioning
filtering
amplification
calibration
noise
resolution
accuracy
precision
ADC limitations
data logging
measurement uncertainty

Required Artifacts Create:

Sensor fundamentals notebook
Temperature sensor lab
Light sensor lab
Accelerometer project
Microphone/sound level project
Calibration notebook
Instrumentation amplifier project
Noise measurement report
Data logger project
“Accuracy vs precision vs resolution” essay

Project Ideas Build:

environmental sensor logger
current/voltage monitor
vibration monitor
audio visualizer
mini weather station
lab instrument dashboard
sensor calibration tool
data acquisition board

Completion Standard This layer is complete when:

sensors can be selected properly
signals can be conditioned
measurements can be calibrated
noise is considered
data can be logged and interpreted
measurement limits are documented

Layer 10 — Power Electronics and Power

Supply Design Purpose Power is one of the most important and dangerous parts of electronics.

Almost every system needs clean, stable, safe power.

This layer begins with low-voltage DC systems and only gradually moves toward more complex power electronics.

Topics

power budgets
voltage regulators
linear regulators
switching regulators
buck converters
boost converters
LDOs
ripple
efficiency
thermal dissipation
batteries
charging basics
protection circuits
fuses
reverse polarity protection
flyback diodes
motor driver basics
grounding
decoupling capacitors
power distribution on PCBs

Required Artifacts Create:

Power electronics safety notes
Linear regulator lab
Buck converter study
Boost converter study
Power budget spreadsheet
Thermal dissipation calculations
Battery-powered project
Motor driver project
Protection circuit notes
“Why power design matters” essay

Project Ideas Build:

5V regulated supply
battery monitor
USB-powered sensor board
small motor driver board
LED driver
protected power input circuit
bench power supply module Completion Standard This layer is complete when:
power budgets are created before building
regulators are selected intentionally
thermal limits are considered
protection circuits are understood
low-voltage power systems can be designed safely
power issues can be debugged systematically

Layer 11 — PCB Design with KiCad

Purpose PCB design forces seriousness.

Breadboards are useful for learning, but PCBs require correct schematics, footprints, layout, routing, manufacturing files, assembly planning, and design review.

KiCad is the correct tool for this roadmap because it is open-source, cross-platform, and supports schematic capture, PCB layout, 3D rendering, and plotting/export workflows. (KiCad)

Topics

schematic capture
symbols
footprints
libraries
ERC
netlists
PCB layout
board stackup basics
trace width
clearance
ground planes
decoupling
connectors
mounting holes
silkscreen
DRC
Gerber files
BOM
pick-and-place basics
manufacturer design rules
design for assembly
design for test
revision control
board bring-up

KiCad’s getting-started documentation notes that KiCad supports an integrated workflow where schematic and PCB are designed together. (KiCad Documentation)

Required Artifacts Create:

KiCad getting-started notes
First schematic-only project
First PCB layout project
Gerber export practice
PCB design checklist
Footprint verification checklist
Board bring-up checklist
PCB revision log template
DRC/ERC error explanation notes
“What breadboards do not teach” essay

Project Ladder Design PCBs for:

LED resistor board
Voltage divider/sensor board
Button/LED microcontroller board
USB-powered sensor board
Op-amp amplifier board
Power regulator board
Data logger board
Motor driver board
Modular lab instrument board
Custom embedded system board Completion Standard This layer is complete when:

schematics can be drawn cleanly
footprints are checked
simple PCBs can be routed
ERC/DRC are used seriously
Gerbers can be exported
boards can be ordered
bring-up is documented
revisions are made based on test results

Layer 12 — Communication Protocols and

Hardware Interfaces Purpose Modern electronics systems communicate.

This layer teaches how devices exchange data.

Topics

UART
I2C
SPI
USB basics
CAN basics
Ethernet basics
Bluetooth basics
Wi-Fi basics
logic analyzers
timing diagrams
pull-up resistors
bus addressing
signal integrity basics
protocol debugging
datasheet timing specs

Required Artifacts Create:

UART project
I2C sensor project
SPI display project
Logic analyzer capture notes
Timing diagram notebook
Protocol comparison table
Bus debugging checklist
Microcontroller interface library
Communication failure postmortem
“How hardware talks” essay

Completion Standard This layer is complete when:

UART/I2C/SPI are practically usable
timing diagrams can be read
protocol failures can be debugged
logic analyzer captures can be interpreted
datasheets are used for interface requirements

Layer 13 — Signals, Filters, and

Introductory DSP Purpose Signals connect electronics to communications, sensors, audio, control, and quantum hardware instrumentation.

This layer bridges analog circuits, math, and software.

Topics

time-domain signals
frequency-domain intuition
sampling
aliasing
Nyquist theorem
analog filters
digital filters
FFT basics
noise
SNR
low-pass/high-pass/band-pass filters
signal conditioning
audio signals
sensor signals
Python signal analysis

Required Artifacts Create:

Signals notebook
Sampling and aliasing simulation
FFT visualization project
Analog filter lab
Digital filter notebook
Audio signal analyzer
Sensor noise analysis
Signal conditioning project
SNR explanation essay
“Why signals matter for hardware and quantum systems” essay

Completion Standard This layer is complete when:

signals can be viewed in time and frequency domains
sampling/aliasing are understood
filters can be designed and tested
FFTs can be used carefully
noise is measured and discussed
signals connect electronics, software, and physics

Layer 14 — Control Systems and

Mechatronics Basics Purpose Control systems teach how hardware responds to feedback.

This matters for robotics, power electronics, motors, instrumentation, embedded systems, and experimental setups.

Topics

feedback
open-loop control
closed-loop control
stability
transfer functions
step response
PID control
sensors and actuators
motors
motor drivers
encoders
servo control
system identification basics
control loop tuning
safety limits

Required Artifacts Create:

Feedback systems notebook
PID control notes
Motor control project
Servo control project
Temperature control loop
Step response measurement
Control simulation
Stability notes
Tuning log
“Feedback as a universal engineering idea” essay

Completion Standard This layer is complete when:

feedback is understood
simple PID control can be implemented
sensors and actuators can be integrated
control loops can be tuned
instability and overshoot are recognizable
safety limits are considered

Layer 15 — Semiconductor Fabrication

and Device Manufacturing Purpose This layer connects electronics to the physical manufacturing of semiconductor devices.

It is not necessary before building basic circuits, but it is essential for long-term understanding of semiconductors, ICs, quantum hardware, and advanced electronics research.

MIT’s Physics of Microfabrication: Front End Processing is directly relevant because it focuses on front-end silicon integrated circuit fabrication processes such as oxidation, diffusion, ion implantation, and epitaxy. (MIT OpenCourseWare)

Topics

silicon crystal basics
wafers
cleanrooms
oxidation
diffusion
ion implantation
epitaxy
photolithography
etching
deposition
doping profiles
MOS structure
CMOS basics
process variation
yield
device scaling
packaging
MEMS overview
fabrication constraints for quantum devices

Required Artifacts Create:

Semiconductor fabrication overview map
Wafer process flow notes
Photolithography explanation
Oxidation/diffusion/implantation notes
MOS capacitor concept map
CMOS process overview
Process variation essay
Fabrication glossary
Quantum hardware fabrication bridge notes
“From sand to circuit” long-form essay

Completion Standard This layer is complete when:

semiconductor devices are understood physically, not only symbolically
fabrication steps can be ordered conceptually
doping and junctions make physical sense
CMOS basics are understood
process variation and yield are meaningful
semiconductor fabrication connects to device design and quantum hardware

Layer 16 — Advanced Hardware Systems

and Integration Purpose This layer combines everything: circuits, firmware, sensors, power, PCBs, communication, measurement, software, and documentation.

This is where projects become real systems.

Topics

hardware architecture
subsystem design
modular design
power distribution
signal integrity basics
EMI/EMC basics
enclosure design basics
firmware architecture
hardware abstraction layers
manufacturing constraints
assembly
test jigs
calibration
field reliability
repairability
documentation
revision control
production checklists

Required Artifacts Create:

Hardware architecture template
Full system block diagram
Requirements document
Schematic design review
PCB design review
Firmware architecture notes
Bring-up procedure
Calibration procedure
Failure-mode analysis
Final project case study Completion Standard This layer is complete when:

complete hardware systems can be designed
subsystems are documented
boards can be brought up methodically
firmware and hardware are integrated
failures are analyzed
revisions are planned
the project is documented like a real engineering artifact

6. EEE Project Ladder

EEE projects must move from simple circuits to real hardware systems.

Level 1 — Measurement and Fundamentals Purpose: build lab confidence.

Examples:

resistor measurement
voltage divider
LED resistor circuit
RC charge/discharge
diode I-V curve
transistor switch
op-amp amplifier
filter circuit
current measurement
oscilloscope signal capture

Each project must include:

schematic
expected behavior
simulation if possible
measurement
comparison
mistakes
conclusion

Level 2 — Small Functional Circuits Purpose: make circuits do useful things.

Examples:

regulated power supply
light sensor
temperature sensor
audio preamp
comparator threshold detector
LED driver
battery monitor
motor switch
simple oscillator
active filter

Level 3 — Embedded Projects Purpose: integrate hardware and firmware.

Examples:

temperature logger
mini weather station
OLED sensor dashboard
motor controller
smart lamp
electronic lock
study timer hardware
vibration monitor
current monitor
data logger Level 4 — PCB Projects Purpose: move from prototype to manufacturable artifact.

Examples:

LED test board
sensor breakout
op-amp amplifier board
regulator board
microcontroller carrier board
data logger PCB
motor driver PCB
modular sensor node
lab instrument PCB
custom embedded controller

Level 5 — Instrumentation and Lab Tools Purpose: build tools that help future building.

Examples:

component tester
signal generator
simple oscilloscope accessory
programmable power monitor
electronic load
current probe interface
data acquisition board
sensor calibration fixture
bench timer/controller
lab inventory tracker with hardware integration

Level 6 — Advanced Hardware Systems Purpose: build serious integrated systems.

Examples:

environmental monitoring system
robotics control board
battery-powered IoT sensor node
custom data acquisition system
modular lab instrument
FPGA-assisted measurement system later
RF signal detector later
quantum-control electronics study project later
semiconductor process simulation notes
hardware/software research platform

7. EEE GitHub Strategy

EEE should appear on GitHub as seriously as software.

Hardware GitHub repositories should include:

README
problem statement
block diagram
schematic
PCB files
firmware
simulation files
BOM
datasheets
assembly notes
test procedure
measurement results
oscilloscope screenshots
known issues
revision history
photos
enclosure notes if relevant
lessons learned
safety notes

Repository categories:

electronics-foundations-lab
ltspice-circuit-simulations 3. kicad-pcb-projects

4. embedded-systems-lab 5. sensor-instrumentation-lab 6. power-electronics-lab 7. digital-logic-lab 8. signals-and-dsp-lab 9. semiconductor-fabrication-notes 10.hardware-system-case-studies

The GitHub goal is:

Make hardware learning visible through schematics, simulations, PCBs, firmware, measurements, failures, and revisions.

8. How EEE Connects to the Other

Domains EEE is not isolated.

It connects deeply to the rest of the life plan.

Mathematics EEE uses:

● algebra ● complex numbers ● calculus ● differential equations ● linear algebra ● probability/statistics ● numerical methods ● optimization

Physics EEE depends on: - electromagnetism

● charge ● fields ● energy ● waves ● optics ● thermodynamics ● quantum physics ● semiconductor physics

Software Development EEE connects through:

● embedded firmware ● hardware dashboards ● lab automation ● data logging ● device interfaces ● hardware control software ● web dashboards for devices

AI EEE connects through:

● edge AI ● sensor data ● signal processing ● model deployment on devices ● AI lab assistants ● hardware monitoring ● automated test analysis

Cybersecurity EEE connects through:

● embedded security ● hardware hacking ● side channels ● firmware security ● IoT security

physical attack surfaces

Operating Systems / Low-Level EEE connects through:

device drivers
memory-mapped I/O
interrupts
firmware
real-time systems
hardware abstraction layers
Linux device interfaces

Quantum Hardware EEE connects through:

microwave electronics
low-noise measurement
control pulses
readout systems
cryogenic electronics
semiconductor devices
superconducting circuits
fabrication constraints

Research EEE connects through:

experimental design
measurement
simulation
reproducibility
technical reports
device characterization
hardware papers

9. How AI Should Be Used in EEE

AI can help tremendously in electronics, but it can also be dangerous if trusted blindly.

Hardware mistakes are physical.

An AI hallucination in code may crash a program.

An AI hallucination in electronics may burn components, damage equipment, or produce unsafe designs.

Correct AI Use Use AI to:

explain circuit concepts
generate practice problems
help read datasheets
suggest simulation setups
review schematics
create debugging checklists
explain oscilloscope readings
help structure lab notes
generate test procedures
compare components
write firmware drafts after requirements are clear
create PCB review checklists
explain failure modes

Incorrect AI Use Do not use AI to:

design power circuits blindly
choose components without checking datasheets
skip calculations
skip simulations
skip current limiting
skip safety review
trust pinouts without verification
trust footprints without checking
generate PCB layouts you do not understand
avoid measuring the real circuit The AI EEE Rule

AI may suggest. Datasheets, instruments, and physical measurements decide.

For every AI-assisted hardware design:

State the requirement.
Draw the schematic yourself.
Calculate expected values.
Verify component ratings from datasheets.
Simulate where possible.
Build safely with current limiting.
Measure.
Compare expected vs actual.
Document failure modes.
Revise.

If it has not been measured, it has not been proven.

10. Common EEE Traps

Trap 1 — Copying Circuits Without Understanding A copied circuit may work once but teach little.

Rule:

    Every copied circuit must be explained, simulated, measured, and modified.

Trap 2 — Ignoring Datasheets Datasheets are not optional.

Rule:

    Every active component needs a datasheet study.

Trap 3 — No Current Limiting Many beginners destroy parts by powering circuits carelessly.

Rule:

    Use current limiting when bringing up circuits.

Trap 4 — Breadboard Overconfidence Breadboards are useful but have limitations.

Rule:

    Understand breadboard parasitics, poor contacts, and high-frequency limitations.

Trap 5 — Simulation Worship Simulations are models, not reality.

Rule:

    Simulate first, but measure reality.

Trap 6 — PCB Without Review A PCB mistake costs time and money.

Rule:

    Every PCB needs schematic review, footprint review, ERC, DRC, and bring-up plan.

Trap 7 — Ignoring Power and Grounding Many hardware bugs are power or grounding problems. Rule:

    Power and ground are design features, not afterthoughts.

Trap 8 — Treating Firmware and Hardware Separately Embedded systems fail at the boundary.

Rule:

    Debug hardware and firmware together.

11. First 25 Serious EEE Artifacts

These are the first serious EEE artifacts to create.

Artifact 1 — Electronics Diagnostic Report A self-assessment of remembered knowledge, missing foundations, available tools, and starting weaknesses.

Artifact 2 — Electronics Safety and Lab Setup Manual A personal safety checklist and lab setup guide.

Artifact 3 — Circuit Fundamentals Notebook Voltage, current, resistance, power, KCL, KVL, Ohm’s law, and basic circuit analysis.

Artifact 4 — LTspice Simulation Lab A repository of simulated resistor networks, RC/RL/RLC circuits, filters, transistor circuits, and op-amp circuits.

Artifact 5 — Measurement Lab Notebook Multimeter, oscilloscope, function generator, and power supply measurement exercises.

Artifact 6 — Passive Components Lab Resistor tolerance, capacitor charge/discharge, inductors, RC filters, and real component behavior.

Artifact 7 — Semiconductor Devices Notebook Diodes, BJTs, FETs, MOSFETs, biasing, switching, and amplification.

Artifact 8 — Diode and Rectifier Lab I-V curves, rectifiers, Zeners, LEDs, and regulator experiments.

Artifact 9 — Transistor Switching and Amplification Lab BJT/MOSFET switching, biasing, and amplifier experiments.

Artifact 10 — Op-Amp Circuit Lab Inverting, non-inverting, comparator, buffer, active filter, and sensor amplifier circuits.

Artifact 11 — Digital Logic Lab Logic gates, truth tables, flip-flops, counters, timing, and debounce circuits.

Artifact 12 — Arduino / Microcontroller Starter Lab GPIO, PWM, ADC, serial communication, sensors, and basic embedded control.

Artifact 13 — Raspberry Pi Pico / RP2040 Embedded Lab A deeper embedded project set using official microcontroller documentation.

Artifact 14 — Sensor and Instrumentation Lab Temperature, light, motion, sound, current, voltage, calibration, and noise measurement. Artifact 15 — Power Supply and Regulation Lab Linear regulators, buck/boost converters, protection circuits, thermal calculations, and power budgets.

Artifact 16 — Communication Protocols Lab UART, I2C, SPI, logic analyzer captures, timing diagrams, and interface debugging.

Artifact 17 — Signals and Filters Lab Analog filters, digital filters, FFT, sampling, noise, and signal-conditioning experiments.

Artifact 18 — First KiCad PCB A simple LED/resistor or sensor breakout board with schematic, PCB, Gerbers, BOM, and bring-up notes.

Artifact 19 — Op-Amp PCB A small amplifier or active filter board designed, ordered, assembled, tested, and revised.

Artifact 20 — Microcontroller Sensor PCB A custom embedded board integrating a microcontroller, sensor, power, and communication.

Artifact 21 — Hardware Debugging Postmortem Archive A collection of failed circuits, symptoms, causes, fixes, and lessons learned.

Artifact 22 — Semiconductor Fabrication Notes A structured study archive on oxidation, diffusion, ion implantation, epitaxy, lithography, etching, deposition, and CMOS basics.

Artifact 23 — Quantum Hardware Electronics Bridge Notebook Notes connecting EEE foundations to quantum control, readout, noise, and hardware constraints.

Artifact 24 — Full Hardware System Case Study A complete project writeup from requirement to schematic, simulation, PCB, firmware, test, failure analysis, and revision.

Artifact 25 — Personal Electronics Reference Manual A living manual containing formulas, component notes, datasheet checklists, test procedures, PCB rules, and debugging strategies.

12. When to Move Forward

Do not move forward because a video series or textbook chapter is complete.

Move forward when circuits, measurements, and documentation prove competence.

Move past lab basics when:

instruments can be used safely
measurements are documented
current limiting is understood
basic safety habits are automatic

Move past circuit fundamentals when:

Ohm’s law, KCL, and KVL are usable
resistor networks can be analyzed
simulations and calculations are compared
simple circuits can be built and measured

Move past passive components when:

capacitors and inductors are understood dynamically
tolerances and ratings are considered
RC/RL behavior can be measured Move past time-domain circuits when:
transients are understood
oscilloscope traces can be interpreted
differential equations connect to circuits

Move past AC circuits when:

impedance and phasors are usable
filters can be designed
frequency response can be measured

Move past semiconductor devices when:

diodes, BJTs, and MOSFETs can be selected and used
basic switching and amplification are understood
datasheets guide design choices

Move past op-amps when:

common op-amp circuits can be designed
feedback is understood
real op-amp limitations are considered

Move past digital logic when:

logic gates and timing are understood
simple combinational and sequential circuits can be built
digital signals can be debugged

Move past embedded basics when:

sensors can be read
actuators can be controlled
UART/I2C/SPI can be used
firmware and hardware are debugged together

Move past PCB basics when:

simple PCBs can be designed, ordered, assembled, tested, and revised
- ERC/DRC are used

● footprint checks happen before ordering ● bring-up plans are written

Move into semiconductor fabrication when:

● semiconductor devices are physically meaningful ● p-n junctions and MOSFETs are understood ● physics and electronics foundations are strong enough

Move into advanced hardware systems when:

● circuits, PCBs, firmware, sensors, power, and documentation can be combined into one coherent project

13. The EEE Standard

The final standard for this domain is:

I can analyze circuits mathematically, simulate them, build them physically, measure their behavior, debug failures, design PCBs, write firmware, read datasheets, understand semiconductor devices, document systems, and connect electronics to physics, software, AI, cybersecurity, research, and quantum hardware.

EEE is the domain that forces contact with physical reality.

It does not care whether the idea sounded good.

It does not care whether the schematic looked elegant.

It does not care whether AI said it should work.

The circuit either works, fails, overheats, oscillates, saturates, shorts, drifts, or reveals that the assumptions were wrong.

That is why EEE is so important.

It trains the builder to respect reality.