About
Editorial policy
The rules I hold myself to, written down so you can hold me to them as well.
How a guide gets written
I run the procedure
Steps come from an actual run on real hardware or in a virtual machine, not from other people's articles. Screens, wording and error messages are recorded as they appear.
Claims get checked against primary sources
Specification details come from the UEFI specification, vendor documentation and project documentation — not from forum summaries.
Limits get stated
Where behaviour varies by vendor, firmware version or release, the guide says so.
It gets reviewed on a schedule
Guides are re-read at least twice a year and after significant changes in the tools they describe. The update date on each page reflects the last substantive change.
Advertising and independence
- Advertising is sold as space, never as coverage. No advertiser sees an article before publication.
- I do not publish sponsored posts, paid reviews or paid links, and I do not accept payment for inclusion in a comparison.
- Recommendations are based on what a tool does. Where I prefer one, the reasoning is in the text so you can disagree with it.
- Any commercial relationship with something I write about will be disclosed in that article, at the top.
Software links
Links to software point to the official website of the project or vendor concerned. I do not host files, I do not use link shorteners or interstitial pages on software links, and I do not repackage installers. Where a project publishes checksums or signatures, I tell you to check them.
Accuracy and corrections
Mistakes get fixed in place. Substantive corrections — anything that changed the meaning of a procedure — are noted at the foot of the page along with the date. Pages that turn out to be wrong are corrected or marked as superseded, not deleted.
Safety and scope
These procedures can erase storage devices. Guides say so plainly wherever it applies and identify the steps where a mistake cannot be undone. I do not publish material aimed at circumventing licensing, activation or the security controls of a device someone does not own, and I do not link to sources that distribute software without the rights to do so.
Use of AI tools
Drafting assistance may be used for structure and language. Technical claims, commands and procedures are verified against primary sources or a real run before publication. Nothing is published unreviewed.
Questions about any of this
Write to thomas@sonnabendlabs.com or call (603) 945-2452.