Skip to main content
New

Write for DevOps Daily. Get merged. Get paid.

A weekly writing challenge for the community. Publish a technical article to thousands of engineers by opening a pull request. Every week, the 5 most popular community posts each win $10.

5 × $10weekly prizes
Every weeknew winners
Everyoneopen to
Submit your postAsk in Discord

// how-it-works

Four steps from idea to published

No new accounts, no proprietary editor. If you can open a pull request, you can take part.

1. Write what you know
A war story, a deep dive, a tool comparison, a postmortem. If you shipped it or debugged it at 3am, it makes a good post.
2. Open a pull request
Add your article as a Markdown file to our open GitHub repo and open a PR. The same workflow you already use every day. Writing with Claude Code? The repo ships a /write-post skill that scaffolds a draft in our format for you.
3. We review and merge
A maintainer checks it for accuracy and clarity, suggests edits if needed, and publishes it under Community with your byline.
4. Win the week
Each week the 5 most popular community posts each win $10. Five winners, every week.

// what-to-write

What makes a good community post

Technical, honest, and grounded in something you actually did. Here is the kind of thing that lands.

War stories and postmortems
The outage that taught you something. What broke, how you found it, what you changed.
Deep dives
How a protocol, a tool, or a piece of infrastructure actually works under the hood.
Hands-on tutorials
A real setup someone can follow end to end, with the gotchas you hit along the way.
Honest comparisons
Two tools, measured against real use. What you picked, what you would not pick again.
How winners are picked
Five winners every week

Each week, from Monday to Sunday, the 5 most popular community posts each win $10. Popularity comes down to reader engagement over the week, so the writing that genuinely helps people is what gets rewarded.

Five winners instead of one means more people get paid and more writers have a real shot, especially early on. Share your post and bring your own readers, it counts.

// the-rules

The fine print, kept short

  • Your work must be original and your own. No reposts, no AI-generated filler. If you used an AI assistant, disclose it.
  • You keep ownership of what you write. Publishing here grants us the right to host it; your byline stays on it and links back to you.
  • A maintainer reviews every submission. Merge decisions are based on accuracy, clarity, and fit.
  • 5 prizes per week, $10 each, to the week's most popular community posts.
  • Be accurate and be kind. Cite sources, do not punch down, and do not post anything you do not have the right to share.

// faq

Questions, answered

Get merged, then claim your author profile
Once your first post is published, add yourself to our Experts directory: a profile page with your bio, links, and specialties, so readers and potential clients can find you. It is another pull request, and we will help you set it up.

Do not miss a challenge

We announce each week's winners and call for the next round on X and LinkedIn. Follow along so you know when the clock resets.

Follow on XFollow on LinkedInJoin Discord

Got something worth writing about?

Open a pull request with your article and join this week's challenge. Worst case, you get a published, edited post with your name on it in front of thousands of engineers.

Submit your postRead recent posts