Developer writing
Prose by and for developers that is not documentation: RFC prose, tech blog posts, release announcements, clarity rewrites.
Download all 58
Start here 1
The general, start-from-zero entry for a need in this category: it works from a blank start, asks for what it needs and hands off to the specific entries. Example: Plan a trip.
- Write about a technical topic
Drafts a technical post, announcement, proposal or explainer for a named audience, leading with the main point and inventing no facts. Use when you need to write about engineering work.
Specific 55
One situation, audience, tool or format inside the category. Example: Plan a road trip with children.
- 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.
- 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.
- 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.
- 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.
- 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 hackathon submission
Writes a hackathon project submission with the problem, what it does, how it was built, what is real versus mocked, challenges and next steps, fitted to the judging criteria and word limits.
- Write a what-we-shipped update
Turns merged PRs, tickets and release notes into a short what-we-shipped update for colleagues outside engineering, grouped by who it helps, in plain words, with credit and nothing overstated.
- Write a TIL post
Turns one thing you just learned while coding into a short Today I Learned post with the problem, the minimal example, why it works, the versions it applies to and the source.
- Write a conference trip report
Turns notes from a tech conference into a short report for your team with the ideas worth trying, talks worth watching, contacts made and whether the event is worth attending again.
- Write a planned maintenance notice
Writes the advance notice for planned maintenance on a software service, with the window in UTC and local time, what will and will not work, what users should do and how they hear it is over.
- Write a sprint review demo script
Writes the script for a sprint review demo that shows user outcomes rather than tickets, orders the items, prepares data and fallbacks, and ends with the questions you need stakeholders to answer.
- Write an engineering team README
Writes an engineering team's outward-facing README - what the team owns, how to request work, what response to expect, on-call and incidents, where to ask, and the links people keep asking for.
- Write a benchmark report
Writes up performance benchmark results with the setup, method, numbers with variance, honest caveats and what the results do and do not show. Use before sharing benchmark claims.
- Write a developer newsletter
Writes a periodic newsletter to the developers who use your API, SDK or platform, leading with breaking changes and action items, then new features, fixes, community and upcoming deadlines.
- Write engineering blog guidelines
Writes the contributor guide for a company engineering blog - what makes a good post, the pitch template, the review path including security and legal, what never to publish and the timeline.
- Write a spike report
Writes up a finished time-boxed spike as the answer to its question, the evidence, what was not tried, the recommendation and what to throw away. Use when a spike ends.
- Explain a technical problem to a client
Explains a technical problem, delay or limitation to a non-technical client or customer in plain words, with what it means for them, the options, the honest uncertainty and the next step.
- Write a standup or async daily update
Turns your commits, tickets and notes into a short standup or async daily update with done, next and blockers, including the specific asks people usually forget to make.
- Announce a technical decision to engineering
Announces a technical decision already made to the wider engineering organisation, with the rationale, alternatives rejected, what changes for whom and when, and when it will be revisited.
- Explain a cloud bill to finance
Explains a cloud bill to finance in business terms - what drives the cost, why it changed, a forecast, and which costs engineering can control and which it cannot.
- Explain an engineering estimate to stakeholders
Explains an engineering estimate to non-engineers - the range and confidence, what drives the time, what would shorten or lengthen it and the trade-offs on offer - without padding or false precision.
- Review a technical article draft
Reviews a colleague's technical blog post or article before publication for accuracy, code that runs, unsupported claims, disclosure risks and structure, as prioritised editor comments.
- Script a recorded code walkthrough
Scripts a short screen recording that walks colleagues through a pull request or an area of the codebase for async review or handover, with file order, what to show and the key points.
- Write an API beta invitation
Writes the invitation to a private API or SDK beta that sets honest expectations on breaking changes, support, data use and production use, says what feedback you need and how to opt out.
- Write an API launch announcement
Writes the announcement of a new public API, endpoint or SDK for developers, with what it lets them build, a first working call, limits, stability level and where to get help.
- Write a cross-team migration request
Writes the internal message asking other engineering teams to migrate off a library, service or platform by a date, with why, the steps, effort, support offered and what happens at the deadline.
- Write a developer experience survey
Writes an internal developer experience survey with neutral questions on builds, reviews, tooling, docs, on-call and focus time, plus the analysis plan and how results will be reported back.
- 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.
- Write a hands-on technical workshop guide
Writes materials for a live hands-on coding workshop - pre-event setup email, timed modules with checkpoints, catch-up branches, a no-install fallback and helper notes, so the room never stalls.
- 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 a paper reading group guide
Prepares a guide for an engineering reading group session on a computer science paper, with background, key ideas, sections to focus on, discussion questions and links to the team's own systems.
- Write up a cancelled engineering project
Writes the closing write-up for a stopped engineering project - why it stopped, what it cost, what is kept, what gets cleaned up and what was learned - without blame or spin.
- 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 security policy exception request
Writes a request for an exception to a security policy with the business need, the specific risk, compensating controls, an expiry date, a remediation plan and the owner who accepts the risk.
- Write a technical book review
Reviews a programming or engineering book from your reading notes - who it is for, prerequisites, what holds up, what is dated, chapters to skip and how it compares - for a blog or team wiki.
- Adapt an internal engineering doc into a public article
Turns an internal design doc, postmortem or project write-up into a public engineering article, removing confidential details, adding missing context and listing what to clear before publishing.
- Explain a system's data flows to legal or privacy
Answers a legal or privacy team's questions about a system as an engineer - what personal data it collects, where it flows, which vendors process it, where it is stored and for how long.
- Write the root cause note when closing a bug
Writes the closing note on a fixed bug explaining the root cause, the fix, why it was not caught, who else might be affected and the follow-ups, for the ticket and its watchers.
- Propose a change to an engineering practice
Writes a proposal to change a team engineering practice such as review rules, branching, testing or on-call, with the problem, evidence, the change, a time-boxed trial and how success is judged.
- Write the retrospective of a finished project
Writes the retrospective write-up of a finished software project with goals against results, planned versus actual timeline, what worked, what to change and recommendations for the next project.
- Write the README for a take-home assignment submission
Writes the README for your take-home coding assignment submission, explaining how to run it, the decisions and trade-offs, what is unfinished and what you would do with more time.
- Write testing notes for QA on a change
Writes the testing notes a QA engineer or tester needs for a change - what changed in user terms, how to reach it, risky areas, test data, known gaps and what is out of scope.
- Write a proposal to adopt a new tool
Writes a proposal to adopt a new library, framework, service or developer tool, with the problem, options compared, trial evidence, total cost, lock-in, an exit plan and a staged rollout.
- Write a feature proposal to an open-source project
Writes a feature request or proposal for an open-source project you do not maintain, grounded in a real use case, prior issues, the project's goals and an offer to help, so maintainers can say yes.
- Write a non-urgent support case to a vendor
Writes a non-incident support case to a software or cloud vendor - a how-to question, a suspected bug, a limit increase, a feature gap or a billing discrepancy - shaped so the first reply answers it.
- Review marketing copy for technical accuracy
Reviews marketing, launch or sales copy about a software product for technical claims that are wrong, unprovable or risky, and suggests accurate wording that still sells.
- Write a security advisory for customers
Writes a security advisory for business customers about a fixed vulnerability in your product, with affected versions, severity, required action, exploitation status and what is not known.
- Write a known-issue brief for support
Writes the note engineering gives support about a live bug - symptoms, who is affected, workaround, what to tell customers, what not to promise and when to escalate.
- 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.
Showing 50 of 55. See them all in search
Advanced 2
Expert or deep work that assumes the user can judge expert output. Example: Plan croissant lamination.
- Write an engineering strategy
Writes an engineering strategy document with an honest diagnosis, a few guiding policies and coherent actions, derived from the company's goals and constraints rather than a list of wishes.
- 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).