How to Find High-Quality Technical Writing
Not all articles teach the same thing.
Some teach syntax. Others teach judgment.
You want writing that explains trade-offs, mental models, and reasoning.
Kent C. Dodds
Kent writes deeply about:
- React mental models
- Testing philosophy
- Developer experience
Search like this:
site:kentcdodds.com react testing
site:egghead.io kent c dodds
His writing explains why patterns exist, not just how to use them.
phryneas (Redux Core Maintainer)
If you work with Redux or RTK, his explanations are essential.
Search:
site:stackoverflow.com phryneas redux
site:github.com phryneas redux
Many of his Stack Overflow answers are better than long blog posts.
DEV.to With Filtering
DEV.to has mixed quality. Filter aggressively.
site:dev.to react performance
site:dev.to "deep dive" react
Check the author:
- Do they reference official documentation?
- Do they explain trade-offs?
- Do they link to source code?
If not, move on.
Medium Without the Noise
Medium requires filtering to be useful.
site:medium.com react architecture
site:medium.com "lessons learned" open source
Avoid articles with titles like:
- “X things you must know”
- “Ultimate guide”
- “Become senior in 30 days”
These are content farms, not engineering writing.
Building a Personal Learning System
Strong engineers do not memorize answers. They build systems for finding them.
A simple approach:
- Check official documentation
- Search GitHub issues
- Use Stack Overflow for edge cases
- Read long-form articles for deeper understanding
- Save and revisit high-quality links
Mentors notice when your questions are informed by reading.