Skip to content

Write for us

Write an article with me

Until now I have written every article here myself. I would like that to change. If you understand one part of web development well enough to teach it, pitch it below, and we will turn it into an article together.

You do not need to be a senior developer. Sometimes the best explanation comes from someone who figured the thing out last month and still remembers what was confusing about it.

How it works

  1. 01

    You pitch

    One topic, one reader, one result. A few sentences in the form below are enough.

  2. 02

    I answer

    I read every pitch myself and reply by email. If it fits, we agree on the outline and the details before you write a word.

  3. 03

    We edit together

    You write the draft. We go through it together until every code sample runs and every step makes sense to a beginner.

  4. 04

    It goes out under your name

    Published with your name, photo, a short bio and your links, and announced to the newsletter like every article.

Is it paid?

Not for now: writing here is unpaid. What you get is your name on the article, an author profile with your photo and links, careful editing of your piece, and the readers of the journal and its newsletter. If that changes, this page will say so first.

What fits the journal

  • One concept explained from scratch: why it exists, how it works, how to use it
  • Code you have run yourself, explained line by line
  • Pitfalls you actually hit, and how you got out of them
  • Written for beginners, with depth for people further along

What does not

  • Sponsored posts, paid links or product placements
  • Articles already published somewhere else
  • List posts ("10 tools you need") and news round-ups
  • Anything with code you have not run

Not sure what the articles here look like? Read a few in the journal before you pitch.

Send your pitch

Every field except the links is needed. Your details are used only to talk about this article with you; see the privacy policy.

As it should appear on the article.

Only used to answer you.

Where are you as a developer?

Who is the reader, what will they be able to do after reading, and why are you the right person to explain it? A few sentences are enough.

At least 100 characters (0 so far).