Reading paths
Follow one path. Then build the lesson.
Each path orders a small set of articles around one practical bottleneck, then points back to the curriculum lesson where that idea becomes a working artifact.
- Paths
- 5
- Notes
- 33
- Use
- Public learning paths
Path 01
Containers from zero to deployed app
Understand what a container actually is at the kernel level, then learn how to compose multiple containers into one application stack, then ship a real Dockerized app.
~2 hours of reading + Lesson 06 hands-on
Lesson logos are curriculum references only: no affiliation, hiring promise, interview promise, salary promise, or placement guarantee.
Company-context skills
Cloud and backend teams care about repeatability because software must run beyond the learner laptop.
Cloud engineeringBackend servicesDevOps teamsShow the Dockerfile, the run command, and proof that the same app starts inside the container.
Platform and company logos are ecosystem references only: no affiliation, endorsement, interview access, hiring preference, salary outcome, or placement guarantee.
- 01Article · read
How Docker Actually Works — Container Internals Explained
Build the mental model: namespaces, cgroups, union filesystems.
- 02Article · read
Docker Compose Explained: Multi-Container Applications Made Simple
Move from one container to a real multi-service stack.
- 06Lesson · hands-on
Docker: Make Local Software Repeatable
Apply both ideas hands-on — write the Dockerfile, run the container, expose the port.
- 01
Path 02
Version control mastery — Git and GitHub
Start with Git as a snapshot DAG (the model in your head), then learn the GitHub workflow professionals use daily, then publish your first real repository.
~2 hours of reading + Lesson 05 hands-on
Lesson logos are curriculum references only: no affiliation, hiring promise, interview promise, salary promise, or placement guarantee.
Company-context skills
A repository is the simplest public proof surface for internships, freelance work, and engineering interviews.
Engineering hiring loopsOpen-source collaborationFreelance deliveryShow a clean repo with meaningful commits, a short README, and a working project path.
Platform and company logos are ecosystem references only: no affiliation, endorsement, interview access, hiring preference, salary outcome, or placement guarantee.
- 01Article · read
What is Git and Why Every Developer Needs It
See Git as a graph of snapshots, not a list of changes.
- 02Article · read
GitHub for Beginners: Creating Your First Repository and Pull Request
Translate the model into the daily GitHub workflow.
- 05Lesson · hands-on
Your Developer Passport: GitHub
Publish a real project and start the habit of visible engineering work.
- 01
Path 03
How modern apps exchange data — JSON and APIs
Understand JSON as the lingua franca of the web, then how APIs use it to enable communication between services, then build your own.
~2.5 hours of reading + Lessons 08, 09, 13 hands-on
Lesson logos are curriculum references only: no affiliation, hiring promise, interview promise, salary promise, or placement guarantee.
Company-context skills
Backend and full-stack teams care less about the framework name and more about clear endpoint behavior.
API teamsData toolingApp configurationBackend engineeringShow the endpoint, sample input, sample output, error case, and the frontend call that uses it.
Platform and company logos are ecosystem references only: no affiliation, endorsement, interview access, hiring preference, salary outcome, or placement guarantee.
- 01Article · read
What is JSON and Why Does Every Application Use It
Six data types, real gotchas, and how JSON beat XML.
- 02Article · read
What is an API and How Do APIs Actually Work
The request-response cycle, status codes, and architectural styles.
- 08Lesson · hands-on
JSON: The Data Format Apps Share
Read structured data, debug malformed JSON.
- 09Lesson · hands-on
How Apps Talk: APIs Revealed
Call a real API and use its data in an interface.
- 13Lesson · hands-on
Create Your Own API
Cross over from API consumer to API provider.
- 01
Path 04
The editor + terminal workbench
Configure VS Code as a professional editor, then master the Linux terminal commands that compose into automation, then use both on a real project.
~2 hours of reading + Lessons 02, 04 hands-on
Lesson logos are curriculum references only: no affiliation, hiring promise, interview promise, salary promise, or placement guarantee.
Company-context skills
Every serious software team expects command-line confidence because builds, logs, and deployments speak through text.
Product engineeringDeveloper toolsCode review teamsPlatform engineeringShow the command you ran, the output you read, and the fix you made after interpreting the terminal result.
Platform and company logos are ecosystem references only: no affiliation, endorsement, interview access, hiring preference, salary outcome, or placement guarantee.
- 01Article · read
VS Code Setup Guide: The Complete Configuration for Web Developers
A practical settings.json, the essential extensions, dev containers.
- 02Article · read
Linux Terminal Commands Every Developer Should Know
Navigation, permissions, pipes, sed, awk, ssh — the daily working set.
- 02Lesson · hands-on
Set Up VS Code Like a Developer
Set up the editor on a real project and modify a working interface.
- 04Lesson · hands-on
How Developers Actually Work: The Terminal
Make the terminal feel like home through practice.
- 01
Path 05
Cross-platform mobile — React Native vs Flutter
Decide whether mobile development is your next direction, then pick a framework based on team and project, then plan a graduation path from web to mobile.
~1 hour of reading + Lesson 20 reflection
Lesson logos are curriculum references only: no affiliation, hiring promise, interview promise, salary promise, or placement guarantee.
Company-context skills
Career direction becomes credible when the learner can explain completed work and choose the next depth path.
Early-career engineeringFreelance discoveryFounder-led productsShow the portfolio summary, strongest project link, next learning path, and one weakness to improve.
Platform and company logos are ecosystem references only: no affiliation, endorsement, interview access, hiring preference, salary outcome, or placement guarantee.
After the path
Return to the lesson with one clearer decision.
A reading path should end with action: run a tool, revise a repo, write a short note, or ask a sharper question before the next build step.
Use paid guidance only when it changes the artifact: a repo, demo, written note, architecture decision, or review trail another person can inspect.
BuildContinue public lessons
Open the 20-lesson path and turn the concept into a runnable artifact.
ReadFollow a focused path
Use a short article sequence only when one lesson needs more context.
DecideCompare plans
Use a paid plan only if feedback, accountability, or review would change the work.
AskAsk with context
Send the lesson, repo, error, or decision you want reviewed before scheduling a call or review.