Written tutorials · working code
Backend programming tutorials built around code you can run, not summaries you have to translate back into practice. Every Java, Spring Boot and Golang guide here states the version it was written against and shows the whole file, not a fragment.
Longer subjects are published as a series and meant to be read in order, with every part still useful on its own. Everything else is filed under its topic. Each guide states the language or framework version it was written against, because on subjects that move quickly that line is the difference between working code and a compile error.
Most referenced
KISS, DRY, YAGNI and SOLID are quoted far more often than they are applied. What each one actually claims, the failure mode it prevents, and the cost of following it too literally.
System Design · 12 min read
The most-referenced programming tutorials on the site — start here if you are new.
Plate 01
System Design
KISS, DRY, YAGNI and SOLID are quoted far more often than they are applied. What each one actually claims, the failure mode it prevents, and the cost of following it too literally.
12 min read
Plate 02
Java
A CompletableFuture tutorial that runs: how to create one, chain transformations, combine several, handle exceptions properly, and pick the right executor so your pipeline never quietly stalls the common pool.
22 min read
Plate 03
Spring Boot
Part one of a Spring Security OAuth2 example: registering the providers, mapping three different user-info payloads onto one account, and issuing your own JWT instead of holding a session.
15 min read
Multi-part walkthroughs, in order — Java collections and concurrency, Golang fundamentals, Spring Boot security.
The ground a backend engineer actually crosses: the Java standard library and its concurrency model, Spring Boot services and the persistence layer beneath them, Golang packages and tooling, and the algorithms that turn up in interviews. These are backend programming tutorials written to be worked through, not skimmed.
Each one names the language or framework release it was written against, shows complete files rather than excerpts, and says where an approach has trade-offs instead of presenting one option as the only one. Nothing is gated, timed or scored — there is no course to enrol in and no progress to track, just written material organised by subject.
Backend programming tutorials: Java and the Spring ecosystem, Go, Kotlin, Node.js, algorithms and data structures, system design and the DevOps work of getting a service deployed. Each guide is written around code you can run.
Each article names the release it was written against at the top. That matters more than it used to: Spring Boot 3 moved the whole framework from javax.* to jakarta.*, and Java has shipped a release every six months since 2018.
Yes. The guides show whole files with their imports rather than fragments, and print real output where behaviour is easier to see than to describe — which for anything involving threads is the only way to make the point stick.
No. Nothing here is gated, timed or scored. There is no enrolment and no progress tracking — just written material organised by subject.
A topic groups every article on a subject. A series is a set of articles written to be read in order, used when one subject genuinely needs several parts. A single guide stays a single guide rather than being split to look like a course.
The RSS feed carries the most recent articles. There is no newsletter and no email capture.