1 min lesson
Writing for developers
Talk through the example in "Writing for developers", then name the result it is meant to produce.
Step 1 of 3
Developers don't read your post to admire your prose. They read the first code block, decide whether you know what you're talking about and either run it or close the tab.
The DX Engineer at Cursor writes for an audience that ships software with the very product you're explaining. The job description sets the bar explicitly: would this post actually land on X or HN and teach a real developer something. That bar is the whole reason this craft section exists. You are not writing to complete an assignment. You are writing something a skeptical engineer will judge in the first ten seconds.