On page 235 of Ray Tracing Gems, a small calculation has an awkward encounter with zero. The accompanying GitHub repository explains the problem: one case can produce division by zero. There is a correction. Anyone following the example can find it. For a technical publisher, this is a revealing little scene. The reader has left the page, opened the files, and discovered that the lesson continues outside the book.
- Apress publishes practical books for developers and IT professionals.
- Technical reviewers are asked to run code and follow tutorial steps.
- Companion repositories extend the books; selected titles are free to read.
Apress occupies that space between knowing what a tool promises and making it behave. Its subject is technology, but its practical problem is the reader’s time. A chapter that saves an afternoon has done something valuable. A plausible example that consumes an afternoon has done the opposite.
The authors behind the imprint
Founded in 1999 by authors Gary Cornell and Dan Appleman, Apress began with people who understood the business from the manuscript side. The original name, Author’s Press, makes the emphasis fairly plain. Today it belongs to Springer Nature, placing a specialist technical list inside a much larger publishing group.
The catalog now exceeds 3,000 titles. It ranges across databases, Java, Python, Apple development, Microsoft and .NET, and other computing subjects. The customer might be a programmer learning a framework, an administrator confronting an unfamiliar system, or an enthusiast moving from curiosity to a project. These are readers with different starting points, united by a desire to do something.
In its author guidance, Apress starts with the prospective writer’s expertise and experience. It says it is willing to publish on niche and emerging technologies. That makes editorial judgment central: an expert’s narrow obsession can become another person’s useful manual, provided someone can explain why the details matter.
A reviewer with a keyboard
The revealing document is the technical reviewer’s brief. Reviewers must flag unclear passages, examine graphics, perform tutorial instructions, and test code across the operating systems and languages the text names. Apress offers an honorarium, a copy of the title, and recognition in the book. The job involves reproducing the reader’s experience before the reader pays for it.
“Test all of the code”
From Apress’s instructions to technical reviewers
This is a useful standard for anyone teaching a difficult process. Ask a second person to perform the steps. Notice where they hesitate. A sentence can sound perfectly clear to its author because the author silently supplies everything the sentence leaves out. A reviewer’s machine supplies nothing of the kind.
A book on two clocks
Printed pages and software age differently. Apress addresses part of that mismatch through public companion repositories. Readers can search GitHub by book title, author, or ISBN and download files without creating an account. Code can receive corrections after publication; changes to the published book generally wait for a new edition.
That arrangement has limits. A repository being public does not make every file freely reusable. Apress’s guidance leaves copyright with authors and permits authors to choose open source licenses. The Ray Tracing Gems repository, for example, specifies MIT licensing unless individual chapter files say otherwise. Before putting an example into a product, read its license.
There is a particularly neat example in Pro Git. Scott Chacon and Ben Straub’s second edition is available in full on Git’s own website, with corrections and additions from hundreds of contributors. A publisher of a book about version control has helped produce a book that benefits from version control. The subject and the method agree.
Sixty-four people, one useful book
Ray Tracing Gems shows the coordination involved. Eric Haines’s GDC presentation records 32 accepted papers, 64 authors, and 121 days between paper submission and the finished book proof. Its intended territory lay between introductory material and research papers: practical techniques for people already serious about rendering.
The follow-up, Ray Tracing Gems II, arrived as a free digital download in August 2021, with supplementary code on GitHub. NVIDIA promoted its release. For the reader, the digital price was zero. For the project, the work still included gathering contributors, reviewing technical material, and turning separate contributions into a readable volume.
The checkout changed
Apress’s commercial model includes individual print and eBook purchases, institutional packages, and selected open access titles. Its subscription history needs a qualification. An October 2024 support notice says Apress Access is closed to new subscribers because of technical limitations following the move to Springer Nature Link. Existing subscribers can renew. A platform decision changed the purchase options.
The publishing list keeps moving. Governance-First AI appeared in September 2026; Mastering DevSecOps followed in October. Together they point toward enterprise readers wrestling with governance and secure delivery. Apress’s expertise is in commissioning and shaping instruction around such work, rather than supplying the software itself.
Alternatives include Manning, whose liveBook brings reading, discussion, and exercises together, alongside other technical publishers and official documentation. The sensible choice depends on the task. An extended project may benefit from a book’s sequence. A changed command may require current documentation. For any title, check its edition, prerequisites, repository, and errata before committing an evening.
For a team lead, that suggests a modest experiment. Choose a chapter that matches a real task. Have one colleague follow it on a clean setup, recording the missing assumptions and checking the accompanying files. If the lesson survives that exercise, it can become shared training material. If it does not, the notes still expose what the team needs to learn. This is an application of the reviewer’s method, rather than a claim about measured results at Apress. Its value depends on choosing a suitable edition and leaving time to practice.
Apress’s most transferable habit is the one hidden in that reviewer’s brief: perform the instructions. Open the files. Try the example. When the result disagrees with the page, investigate. That is how a technical book earns its place beside the keyboard.