A route through a subject,
not a shelf of articles.

From the command line to production you would be willing to be paged for.

The path from "I can use a computer" to "I run the systems a business depends on". It starts at the shell and the network because everything above them is a lie you have not debugged yet, then climbs through Linux and a cloud platform, adds automation, and ends on the part most people skip: operating what you built.

Realistic pace

Evenings for 6–9 months, or a focused year alongside a day job.

Steps

37 steps0 of 37 steps have material written

The parts of a CS degree that keep earning, in the order they make sense.

Not a degree in a folder and not a list of frameworks. This is the durable half of computer science: how to program something you can still read in a year, which data structures actually decide whether your program is fast, how the machine underneath behaves, and the theory that tells you when a problem is impossible rather than merely hard.

Realistic pace

A steady year of evenings, or three to four months full time.

Steps

26 steps2 of 26 steps have material written