Turn the deployment into evidence

Anyone can list technologies on a profile. What is worth something is a record of a specific deployment — which recipe, at what scale, under which constraints, with which parts going wrong — that somebody checked before it was published. That is what this site means by a verified deployment, and it is the ordering principle of the engineer directory.

The reviewing is deliberately unglamorous: a submission is checked against evidence by a person, and the audit trail of that decision is kept. Reference material and real engagements are labelled differently and never merged.

The confidentiality rules that governed the work do not stop when it ships. Customer and client names are not published without explicit permission. Private evidence stays private and can be shown to a reviewer without becoming public. If a customer agrees to a reference, get it in writing and agree the wording.

You can describe a great deal without identifying anyone: the sector, the size band, the jurisdiction, the constraint, the architecture, the evaluation numbers and what you would do differently. That is the useful part anyway.

The most valuable paragraph in any deployment record is the one about what did not work: the conversion step that mangled the scans, the retrieval numbers before and after the change, the week lost to a firewall request. It is also the paragraph that makes the rest credible.

Write it while you still remember. Six months later you will have a tidy story, and the tidy story is worth less to everyone.