Written by practitioners · one imprint

Cognate Press — cog·nate

/ˈkɒɡ·neɪt/ · adjective · descended from a common root

One publication for every language we build in, each written by the engineer who works in it — about what production actually taught them.

Cognate Press is the imprint behind independent technical publications: one programming language each, each signed by an engineer who works in that language every day, each on its own domain. Nothing here is a rewritten tutorial. Every issue is distilled from production — systems its author built, broke, measured and repaired — and published only when the claim can be checked. The imprint hosts nothing and aggregates nothing. It is a mark of authorship: where the asterisk appears, a single expert wrote every word, and they do the work they write about.

From Latin cognātus, “born together” — English night, German Nacht, Dutch nacht: different forms, recognizably related, one origin. One title per language, one practitioner per title, one standard of evidence.

One title per language, written by the engineer who works in it

One independent title per language. Each takes the layer under the documentation — the runtime, the framework, the failure that only appears in production — and is written by the person who had to fix it.

ElephantPHP
PHP · elephantphp.comPHP internals, performance, architecture and production behavior — measurements over assumptions, trade-offs over rules. — Alden Pike JS Ledger
JavaScript · jsledger.comJavaScript, TypeScript, and the runtimes, frameworks and tooling behind modern web applications. — Jonah Vail JVM Scope
Java · jvmscope.comJava, runtimes, frameworks, and the systems beneath them: the JVM and its ecosystem, read closely. — Marcus Venn PyDepth
Python · pydepth.comPython, its runtimes, frameworks, and the systems beneath them — read from source, measured, not assumed. — Elliot Sayer CSharpMind
C# · csharpmind.comC#, .NET, and the runtime beneath them: the CLR, the JIT, the garbage collector and the frameworks built on top. — Callum Reeve SQLPress
SQL · sqlpress.comDatabases, queries and the people who run them: PostgreSQL, MySQL, SQL Server, Oracle and data engineering. — Elias Rowe Gopheria
Go · gopheria.comGo, beneath the surface — the runtime, concurrency, performance, and the trade-offs behind clean abstractions. — Nolan Keir

Every publication opens on its own domain. The imprint publishes nothing of its own — the writing lives where the byline lives.

All publications →

One byline each, and every one a practitioner

Every name here is a practitioner first. Each writes the single language they work in every day, and each publication carries exactly one byline — nothing ghostwritten, nothing syndicated, nothing generated. The expertise is the product.

Alden Pike

Writes ElephantPHP · PHP

Writes about what happens beneath frameworks and abstractions, from language internals to production behavior. Measurements over assumptions.

Jonah Vail

Writes JS Ledger · JavaScript

Explores what happens beneath runtimes, frameworks and tooling. Source code and reproducible experiments over received wisdom.

Marcus Venn

Writes JVM Scope · Java

Runtime behaviour, concurrency and garbage collection. Prefers JDK source and reproducible experiments to rules of thumb.

Elliot Sayer

Writes PyDepth · Python

Language behavior, concurrency and the trade-offs hidden beneath Python's deceptively simple surface. Measurements over folklore.

Callum Reeve

Writes CSharpMind · C#

The language and its lowering, the JIT’s decisions, and what garbage collection costs. Settles a claim against runtime source, a documented knob, or an experiment that states its SDK build.

Elias Rowe

Writes SQLPress · SQL

Database engineer. Publishes a claim only when the version is exact, the setup is written down, and the reasoning can be checked.

Nolan Keir

Writes Gopheria · Go

Concurrency, runtime behavior and performance. Prefers reproducible experiments to rules of thumb, and publishes the code behind every measurement.

Every name opens its own profile — the language they work in, the publication they write, the issues out so far, and the standard of evidence the byline holds itself to.

All authors →

One subscription, every publication

The Cognate letter

One email a month: the strongest piece from each publication — every language in the imprint, one letter — with a line on why it matters. No product news; the imprint has nothing to sell you.