Developer writing
Prose by and for developers that is not documentation: RFC prose, tech blog posts, release announcements, clarity rewrites.
Download all 15
- Rewrite for clarity
Rewrites technical prose so the main point comes first and every sentence is plain and specific, while keeping every fact, number and caveat. Use on design notes, emails, RFC drafts and docs.
- Write a conference talk proposal
Writes a CFP submission with title options, abstract, timed outline, takeaways and notes for reviewers, aimed at the event's audience and selection criteria. Use for engineers and developer advocates.
- Write a technical blog post
Turns engineering notes, code and results into a technical blog post with one clear takeaway, real numbers and working code, and no hype. Use for engineering blogs and write-ups of a project.
- Developer advocate
Acts as a developer advocate who earns attention by teaching, builds demos that work on the first try, carries user feedback back to maintainers and discloses affiliation every time.
- Draft maintainer issue replies
Drafts kind but firm replies to the issues maintainers find hardest, such as support questions, out-of-scope requests, hostile reports, ETA demands and stale needs-info, with labels and next action.
- Explain a technical issue to executives
Translates a technical issue or decision into a one-page executive brief with business impact, options, cost, risk and the specific ask. Use when leadership must decide or fund something technical.
- Outline a tech talk with a live demo
Outlines a conference or meetup talk built around a live demo, with the one idea, a timed structure, a demo script with checkpoints, slides versus editor, a recorded fallback and a failure plan.
- Write an API deprecation notice
Writes the notice to API consumers for a deprecation or breaking change, covering what changes, the timeline, migration steps and where to get help. Use before announcing an API change.
- Write a "how I built it" article for a project launch
Writes a build-story article for dev.to, Hashnode or a project blog that teaches one real technical lesson from making an open-source project. Use to support a launch.
- Write an engineering quarter review
Writes an engineering team's quarterly review for leadership, with outcomes against goals, what shipped and why it mattered, reliability, team health, tech debt, next-quarter bets and asks.
- Announce a new open-source project
Writes the launch post for a project going open source for the first time, new or released by a company, with a first-screen example, honest maturity, the maintainers' commitment and a readiness list.
- Write an open-source grant application
Drafts an open-source grant application with the problem and users, priced milestones, maintainer capacity, sustainability after the grant and measurable outcomes, fitted to the funder's questions.
- Write a public incident report
Writes a public, customer-facing incident report from the internal postmortem, explaining impact, cause and fixes honestly, without blame, speculation or sensitive internal details.
- Write a release announcement kit
Turns an open-source release's changes into a GitHub release body, a blog piece, social posts and an upgrade note, led by the change users care about and crediting contributors.
- Write tech radar entries
Writes tech radar blips for an engineering organisation from team notes and experience reports, each with a ring (adopt, trial, assess, hold), the evidence, where it fits, risks and an owner.
Not: general writing, editing or email (writing-communication domain); marketing copy (copywriting).