The publication
About TechRoom360
TechRoom360 is a technology publication covering the tools, ideas and people shaping how software gets built.
This page sets out what that means in practice — what we cover, how the work is done, and who is answerable for it.
What we cover
Technology that changes how software actually gets built, across eight subjects. The list is short on purpose — a publication that covers everything covers nothing closely enough to be worth reading.
- AI
- Infrastructure
- Developer Tools
- Security
- Product & Design
- Business of Tech
- Research
- Hardware
What we leave alone
Funding rounds reported as news, launches we have not used, and rumour repackaged as reporting. If we have nothing to add to a story, we do not add to the pile.
How we work
Four standards, applied before an issue goes out rather than defended after it.
- Primary sources
- Every claim is traced to where it came from — the paper, the changelog, the filing, the transcript. Where we are inferring rather than reporting, the sentence doing it says so.
- Corrections in place
- An error is fixed on the page that carried it, dated and described. Nothing is quietly edited into having been right all along.
- No coverage for sale
- Nothing is published in exchange for payment, access or a product. Where a relationship exists that a reader would want to know about, the piece is where they find out.
- The record stays
- Issues are not removed or rewritten to suit how things turned out. Each one keeps its own permanent address, in full, and the archive is the whole of it.
Who makes it
Every issue carries a byline, and the byline is answerable for what is under it. Contributors appear here as they join the masthead.
Editorial
TechRoom360
The TechRoom360 editorial desk.
Follow the work
New issues go out by email and appear here the same day, in full.