Argue with the learning resource.

The learning resource on this site is the problem space we work in, published openly. It is also written by people who are too close to it. If you can improve it, we would like you to.

What is worth sending

Corrections. If something in the learning resource is wrong, imprecise or out of date, tell us. Technical material goes stale faster than any other kind, and stale material is worse than none — somebody prepares for an interview on it.

Counter-arguments. The positions described there — acting as principal, insulation enforced in the schema rather than in policy, verification before value moves, privacy achieved structurally — are architectural choices, not laws. If you think a choice is wrong, say why. We will publish a good argument against our own position, and we have.

Explanations that work better than ours. If you have taught this material and found a clearer way through it, send it.

Security findings — but not here. Those go to security@blowtrumpet.com, under coordinated disclosure. We respond to good-faith reports and do not pursue researchers who give us reasonable time.

What we cannot accept

Do not send us anything confidential to someone else. If you are bound by an obligation to a current or former employer or client, keep it. We do not want it, we will not read it, and sending it creates a problem for you rather than an advantage.

Do not send production data, credentials or anything identifying a real person. Synthetic examples only.

What you get

Credit on corrections and contributions we adopt, where you want it. A direct conversation with the engineers who wrote the material. And, candidly, visibility — a good argument sent to this address is a better introduction than most applications.

Before you send anything

Invited work — a commissioned piece, a research collaboration, paid work on a brief — runs under a written agreement covering scope, credit, confidentiality and payment.

Anything else is unsolicited, including technical proposals, architectures and code, and including material produced in a recruitment process. It is received on a non-confidential basis under our Unsolicited Idea Submission Policy. Given how narrow this problem space is, assume we are already working on something adjacent — the policy says so plainly rather than leaving you to find out.

The licence described there is non-exclusive: what you send remains yours to use, publish or build on. If you have something you consider genuinely proprietary, write to legal@blowtrumpet.com before you send it.

[Read the Unsolicited Idea Submission Policy]

Get in touch

Corrections and contributions: editorial@blowtrumpet.com

Security: security@blowtrumpet.com

Agreements before submission: legal@blowtrumpet.com