A publication for engineers who take the work seriously.
No platform, no growth team
Engiprep is owned by the people who write for it. We take no investment and owe nothing to a recommendation algorithm.
Fewer pieces, more thought
Every piece is edited by a working engineer and fact-checked against documentation before it goes out.
Written to age well
We write about the parts of the craft that were interesting in 2010 and will be interesting in 2040.
Most writing about software is marketing wearing a cardigan. We wanted somewhere else — a journal with the temperament of a field notebook, written by people still shipping.
Engiprep is that journal. Our only editorial test is whether a piece would be useful to a working engineer a year from now. We insist on no AI-generated prose, ever.
How we work
Our editorial process is public by design. If you are considering pitching an idea, here is how we evaluate and refine the work.
We welcome ideas from working engineers
Send a paragraph describing what you'd like to write and why it matters. We prioritize topics with technical depth that will remain relevant for years, not weeks.
Patient, peer-led editing
Every piece is paired with a section editor. We iterate on structure and clarity until the piece earns its length. No work is rushed to a deadline.
Technical verification
Benchmarks are reproduced and code examples are run. We verify technical claims against documentation and industry standards before publication.
We correct, visibly
Nothing is silently edited. Material corrections are logged at the bottom of the piece with a timestamp. We value transparency over the appearance of perfection.
The people
Engiprep is run by editors who are practicing engineers. We rotate roles every two years to ensure our editorial remains grounded in production reality.
