Become an author
Most guides on this blog started as a problem that cost somebody an afternoon. Have one of those, and can write it down so the next person gets the afternoon back? Then send it to us.
What we look for
The topic sits next to the toolbox: data formats, encodings, HTTP, DNS, certificates, the shell. Narrow wins. A piece on the quoting rules of CSV dialects is worth more here than another overview of anything.
What goes in it has to be checkable, so name the version, the flag, the command. And describe at least one failure you ran into yourself, with the output it produced. That is the part nobody can look up, and the part readers come back for. In your own words, please. Generated drafts and rewritten manual pages go back unread.
How it works
- 01 create an account We unlock it by hand, within two working days.
- 02 send us your portrait A square image. It ends up next to your byline.
- 03 write and submit the draft Wherever you write, handed in as a file. There is no editor to learn here.
- 04 review and publish Notes from us, at most two rounds, then it goes live with your byline.
Not what this page is for
Sponsored posts, paid links and link insertions into existing articles. We turn those down without exception. Nobody pays us for an article, and we pay nobody for one either.
Questions authors ask
Do you pay for guest posts?
No, and we take no money for publishing one either. What an author gets is the byline with name and portrait, and the right to republish the piece on their own site after 30 days with a canonical link back here.
Do you accept AI-written articles?
No, and it is the fastest rejection we hand out. A generated draft has no error message anybody actually saw, no version numbers, and it hedges every claim. Using a language model to check your grammar or argue with your outline is fine. Handing in its prose is not.
Can I republish a guest article on my own blog?
Here, yes, after 30 days and with a rel="canonical" pointing at the original URL. That is the safe pattern in general, because the canonical tag tells search engines which copy is the source. Republishing without one is what makes both versions rank badly.
What word count do technical guides need?
Our floor is 1,200 words, and the guides we publish ourselves run 1,800 to 3,500. Length is a symptom rather than a goal. A piece that covers the failure modes, the versions and the fix reaches that count on its own.