Engineering notes, written from the work
Diagnostic procedures from live engagements, governance patterns used in production, and implementation lessons from defects we have found and fixed.
Diagnostic procedures and implementation patterns
Written for people who have to make a decision about a real system. Each one names where it came from, so you can weigh it accordingly.
- Diagnostic procedure
Diagnosing a crawl-rate collapse from server logs
A crawl rate rarely falls for the reason it appears to. Six measurements, in order, that separate a server problem from a directive problem from a content problem — before anyone changes anything.
Search EngineeringRead - Implementation pattern
Making content governance executable, not advisory
A written claims policy does not survive contact with a deadline. Here is the pattern that made it a build failure instead — a typed register, a single rendering path, and a verifier that refuses to ship an unapproved figure.
Publishing governanceRead - Implementation lesson
Why layout verification has to happen at real widths
A bug that only appears above 1200px is invisible to a preview pane 781px wide. It took a specific class of tooling to find, and the lesson generalises: verify at the dimensions the defect needs, not the ones that are convenient.
Platform EngineeringRead
A diagnostic procedure is more useful applied to your system
If one of these reads like the problem you are looking at, that is usually the point at which a conversation is cheaper than further reading.