Layers of Logic

Programming · source to system

Code is the surface.

Learn what runs beneath it. Layers of Logic connects the code you write to data, memory, runtimes, and the tradeoffs that shape real programs.

shared-stateone line / four layers
// two tasks update the same value
balance = balance + payment
  1. 01Source

    One assignment looks like one operation.

  2. 02Work

    Read, add, and write happen separately.

  3. 03State

    Both tasks can read the same old value.

  4. 04Result

    An update disappears. The cause is visible.

Course catalogue

Two courses in preview. Three tracks planned.
01JavaAvailable02DSAPreview available
03AptitudeComing soon
04SQLComing soon
05PythonComing soon

How each course works

Syntax is only the top layer.

A keyword or formula is easy to memorize. The useful part is knowing what it changes, when it fails, and why one approach fits better than another.

01

input → operation → result

Use it

Meet the idea in a complete example with the inputs, output, and rules visible.

  • What problem it solves
  • How to use it correctly
  • What the result means
02

source → runtime → state

Trace it

Connect what you wrote to the work the language, runtime, or machine performs.

  • Execution order
  • Data and memory
  • Errors and edge cases
03

option A ≠ option B

Choose it

Compare alternatives by cost, constraints, and the behaviour your program needs.

  • When the idea helps
  • What it costs
  • Which alternative fits

Course structure

No hidden prerequisites.

Before a course uses an idea, it teaches the dependency. The full sequence is visible from the start.

Browse all courses
  1. 01
    Set up the model

    Tools, notation, first complete example, essential vocabulary

  2. 02
    Build with it

    Core operations, data, control, and reusable structures

  3. 03
    Handle real cases

    Failure paths, edge cases, libraries, and larger problems

  4. 04
    Look underneath

    Runtime behaviour, memory, performance, and tradeoffs

Practice

Practice is part of the course, not an appendix.

Every task is attached to the lesson that prepares you for it. Open the work beside your code, use a hint only when you need one, and check the result without leaving VS Code.

EXPLORERexercise-03
⌄ CURRENT TASK ◇ src  Solution ◇ checks

✓ build completes

✓ expected state is preserved

✓ edge case is handled

3 checks passed