<p>Justin overcomes the curse of knowledge and writes simply to explain well. The writing principles shown here create a digestible technical-explainer.</p>
<blockquote>
<p>G'day! flicstar your friendly editor here. I help writers create great written content. Let me help you improve your writing by taking a look at what some others are doing really well.</p>
</blockquote>
<p>I use <a target="_blank" href="https://github.com/open-strategy-partners/editing-codes">editing codes</a> to review articles and call out specific techniques for effective writing.</p>
<hr />
<p>Today I looked at some writing by <a target="_blank" href="https://technically.dev/justin">Justin</a> of <a target="_blank" href="https://technically.dev">Technically.dev</a>: </p>
<p>📝 <a target="_blank" href="https://technically.dev/posts/apis-for-the-rest-of-us/">APIs for the rest of us</a></p>
<div class="embed-wrapper"><div class="embed-loading"><div class="loadingRow"></div><div class="loadingRow"></div></div><a class="embed-card" href="https://youtu.be/vBqkalDGNkE">https://youtu.be/vBqkalDGNkE</a></div>
<p>In my <a target="_blank" href="https://openstrategypartners.com/blog/the-positivity-pass-and-why-we-do-it/">positivity pass</a> on this article, I highlight a couple of principles that make it work really well. </p>
<ul>
<li><strong>SIMPL</strong> - Low Flesch-Kincaid score for technical subject matter.</li>
<li><strong>ILLUS</strong> - Diagrams help understanding.</li>
<li><strong>TOOM, TRUST</strong> - The piece is scoped, and admitting the extent of your knowledge works to establish trust with the reader.</li>
</ul>
<p>🎉 Kudos to Justin for consistently great writing! </p>
<hr />
<p>You can find the editing codes on the <a target="_blank" href="https://openstrategypartners.com/resources/the-osp-editing-codes/">Open Strategy Partners website</a> and on <a target="_blank" href="https://github.com/open-strategy-partners/editing-codes">GitHub</a>.</p>


Justin overcomes the curse of knowledge and writes simply to explain well. The writing principles shown here create a digestible technical-explainer.

> G'day! flicstar your friendly editor here. I help writers create great written content. Let me help you improve your writing by taking a look at what some others are doing really well.

I use [editing codes](https://github.com/open-strategy-partners/editing-codes) to review articles and call out specific techniques for effective writing.

---

Today I looked at some writing by [Justin](https://technically.dev/justin) of [Technically.dev](https://technically.dev): 

📝 [APIs for the rest of us](https://technically.dev/posts/apis-for-the-rest-of-us/)


%[https://youtu.be/vBqkalDGNkE]


In my [positivity pass](https://openstrategypartners.com/blog/the-positivity-pass-and-why-we-do-it/) on this article, I highlight a couple of principles that make it work really well. 

- **SIMPL** - Low Flesch-Kincaid score for technical subject matter.
- **ILLUS** - Diagrams help understanding.
- **TOOM, TRUST** - The piece is scoped, and admitting the extent of your knowledge works to establish trust with the reader.


🎉 Kudos to Justin for consistently great writing! 

---

You can find the editing codes on the [Open Strategy Partners website](https://openstrategypartners.com/resources/the-osp-editing-codes/) and on [GitHub](https://github.com/open-strategy-partners/editing-codes).



Blogstar: Justin

G'day, I'm flicstar (Felicity Brand). I'm a technical writer and editor working in (mostly) open source. I enjoy helping writers and non-writers create great written content.
