Object-Oriented Programming (OOP)
Students preparing for object-oriented theory questions in interviews and university exams, and beginners who have written programs in their first language.
This page needs a newer browser to run its tools. You can still read everything here.
The core subjects of a computer science degree, written for self-study: what each part of a computer system does, and why it works the way it does.
Students preparing for object-oriented theory questions in interviews and university exams, and beginners who have written programs in their first language.
Computer science students preparing for university exams, entrance exams and interviews, and back-end developers who want to know what their database does.
Computer science students preparing for university exams, entrance exams and interviews, and developers who want to understand processes, memory and files.
Computer science students preparing for exams and interviews, IT learners, and developers who debug network problems.
CS and IT students on university graphics courses and OpenGL labs or UGC NET Computer Science, web developers moving to WebGL 2, WebGPU and three.js, and game and creative-coding developers.
ECE, EEE and CS learners preparing for RTL design, design verification and FPGA roles, and software engineers moving into Python-based hardware verification.
University and entrance exams reward precise definitions, numerical problems and derivations you can reproduce on paper. Interviews ask you to explain an idea in your own words and connect it to systems you have used: what happens when you open a web page, why a database needs transactions, why a program slows down when memory runs short.
Prepare for both in the same way: learn the definition, work one problem by hand, then explain the idea aloud without notes.
These subjects depend on each other less than it seems, so start with the one your course or your next interview needs. Within a subject, read the lessons in order, because later lessons use the terms that earlier ones define.
When a lesson works through a calculation, such as a delay on a network link or the cost of a query, redo the arithmetic yourself before you read on. Numbers you have worked out are the ones you remember.
Connect each subject to a real system: list the processes your computer is running, ask a small database how it plans a query, or watch the requests your browser sends when a page loads. Seeing an idea at work makes its definition stick.