CodeWithYash
Project ladder

Turn each layer of knowledge into evidence.

These are cumulative engineering checkpoints. Each project extends the previous mental model with a new source of complexity: persistence, trust, failure, distribution, then cloud-native delivery.

Portfolio rule

Show the decision, failure mode, and test—not only the happy-path code.

01

Foundation

Modules 0-3

Task API

Build a basic REST API for tasks.

Open starting checkpoint

Required evidence

  • API Contract
  • Unit Tests

02

Intermediate

Modules 4-5

Commerce Core

Layered architecture and JPA domain logic

Open starting checkpoint

Required evidence

  • Schema
  • Repositories

03

Advanced

Modules 6-10

Production API

Validation, configuration, logging, security, and testing

Open starting checkpoint

Required evidence

  • Security Config
  • Integration Tests

04

Expert

Modules 11-14

Event-driven Platform

Caching, messaging, API integration, and file handling

Open starting checkpoint

Required evidence

  • Kafka Config
  • Event Handlers

05

Master

Modules 15-19

Cloud Native Stack

Observability through microservices capstone

Open starting checkpoint

Required evidence

  • Gateway
  • Service Discovery

Mastery review

A shared definition of done

Use this gate after every checkpoint. If one item is missing, the project has exposed the next learning task.

Contract is documented with success and failure examples
Architecture decisions include their trade-offs
Critical behavior has automated evidence
Failure, security, and operational paths are explained