The goal E University
Systems knowledge for AI engineers
Processes, memory, parallelism, containers, cryptography and code review — the computer science underneath the model, which decides whether the system can be run and trusted.
- Knowledge nodes
- 43
- From zero
- about 32 h
- Labs
- 4
See what you already know — no account
The diagnostic removes what you already know, so your path is usually much shorter.
What you can do afterwards
- EGraph algorithms: BFS, DFS, topological order
- EDynamic programming
- ECryptography — hashes, signatures, keys
- EDocker — containers
- EProcesses, threads and resource limits
- ECode review
- FFloating-point formats: fp32, fp16, bf16
- EParallelism and why GPUs
- FThe memory hierarchy and bandwidth
- EData pipelines and ETL
- EData storage and formats: Parquet, Arrow
- EData versioning
Labs along the way
You write the code. Tests you cannot see decide whether it holds up.
The whole path
Everything the goal builds on, grouped by level and in the order it builds on itself. Show on the map
AExplorer2 knowledge nodes
BInvestigator4 knowledge nodes
CBuilder8 knowledge nodes
DAI developer16 knowledge nodes
- Discrete mathematics: graphs and relations
- Time complexity and big-O notation
- Data structures: lists, stacks, queues, hash tables
- Python — functions, scope and exceptions
- Reading and understanding other people's code
- Python — modules, packages and virtual environments
- Git — version control
- Recursion
- The terminal and the shell
- Testing with pytest
- Logarithms
- Vectors
- Matrices and matrix multiplication
- NumPy — arrays and vectorisation
- Pandas — tables in Python
- SQL — the basics
EUniversity11 knowledge nodes
- Graph algorithms: BFS, DFS, topological order
- Dynamic programming
- Cryptography — hashes, signatures, keys
- Docker — containers
- Processes, threads and resource limits
- Code review
- Numerical stability and floating point
- Parallelism and why GPUs
- Data pipelines and ETL
- Data storage and formats: Parquet, Arrow
- Data versioning