Skip to content
stateless.co · Engineering notes from the request/response layer
statelessThe engineering desk

A publication about the machinery under everyday software: the contracts between services, the queries behind a page, and the failures that only show up in production.

—ArchiveMethod

How we work

What a Stateless article is checked against before it is published, and what happens when we get something wrong.

Choosing a subject

A subject qualifies when three things are true: engineers search for it repeatedly, the answers currently available are partial, and a complete answer is possible in one reading. Broad surveys and “top ten” lists fail the third test and we do not run them.

Sourcing

Specifications, vendor documentation and primary standards come first; where a claim rests on behaviour rather than on a document, we say which version we observed it in. Where we do not know a number, we do not invent one.

Corrections

Errors are corrected in place, and the correction is stated in the article rather than removed quietly. If you have found one, write to us — the address is on the contact page.

Paid placements

Placements are sold, labelled and kept outside editorial judgement: an advertiser cannot buy a mention inside an article, a position in a section, or the removal of a sentence. Terms are on the placements page.