🇩🇴 I'm a Technical Program Manager and Content Strategist with an MSc in UXD. I help developers become better content creators and DevRel teams build robust content programs.
As with anything, it depends :) But I aim for a minimum of two revisions. The purpose of each revision also matters. For example:
Revision #1: I'll re-read and check for technical accuracy, fix typos, cut sentences, and add content.
Revision #2: If it's a tutorial I'll recreate the experience by following the steps. If I'm missing something, I'll add it in or I'll revise if something isn't clear.
🇩🇴 I'm a Technical Program Manager and Content Strategist with an MSc in UXD. I help developers become better content creators and DevRel teams build robust content programs.
Re-do as in review? Yes, it's always preferable to have someone review the tutorial and try it from start to finish. This option isn't always available to people, however, but is generally considered a best practice.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As with anything, it depends :) But I aim for a minimum of two revisions. The purpose of each revision also matters. For example:
And then publish.
It's even better if you can get someone else to redo the tutorial, that's the best way to test it.
Re-do as in review? Yes, it's always preferable to have someone review the tutorial and try it from start to finish. This option isn't always available to people, however, but is generally considered a best practice.