Why we organise tutorials by topic
Java is a large language. The official tutorial on Oracle's website runs to thousands of pages, and the most popular Java reference books exceed 1,500 pages. No reader consumes that in one sitting. The two common ways to slice a large body of material are by difficulty (beginner, intermediate, advanced) or by topic (basics, OOP, collections, and so on). Difficulty is good for absolute beginners who need a guided path; topics are good for working developers who already have a job to do and need to deepen one specific area.
If you are debugging a memory issue, you do not want to read four tutorials about loops and conditions first. You want to go straight to Multithreading, or to Collections, or to File I/O — whatever is closest to the failing code. Topic pages give you that direct route. Each topic page opens with a short prose overview of the area, lists the tutorials in that topic, and points at related topics so you can cross-reference easily.
The six topics below cover roughly 90 percent of what a working backend Java developer uses in a typical week. The remaining 10 percent — niche libraries, vendor-specific extensions, performance tuning, deployment — is the kind of thing you learn on the job. We deliberately do not split topics more finely than these six because the result would be pages with one or two tutorials each, and navigation across 20 tiny topics is worse than navigation across six well-populated ones.
Within each topic page you will also find a “Why this topic matters” section explaining the real-world value, a “Core concepts” section listing the key vocabulary, and a “Common pitfalls” section so you can recognise the bugs you are most likely to hit. We have found these three sections to be the most-saved pages on the site; many readers bookmark the topic page rather than the individual tutorials because the topic page serves as a launchpad.