# The rules of finding accurate instructions for doing something technical

**Published by:** [Operator](https://paragraph.com/@cybertelx/)
**Published on:** 2022-10-16
**URL:** https://paragraph.com/@cybertelx/the-rules-of-finding-accurate-instructions-for-doing-something-technical

## Content

First, always check the docs (if applicable) Then search it up on a search engine If it’s something web-y, always consult Mozilla Developer Docs Never go to W3schools If it’s a programming-related question, consult StackOverflow Resist the temptation to click anything in “Hot Network Questions” Never actually post your question on StackOverflow Search it up on Reddit in the applicable subreddit (if it exists) Guides found on websites with .dev domains are always accurate Guides found on personal blogs are always accurate Guides found on the DigitalOcean blog are always accurate Never trust GeeksForGeeks Never trust anything written in a serif font Never trust anything in a video unless it’s from Fireship Never trust anything on LinkedIn After a while, give up and come back later Never give up, stay focused Anything on the 2nd page of Google is almost always unhelpful Smash your computer into the wall in a fit of rage Finally, as a last resort, ask the community of this particular solution and then get a link to an extremely helpful document which you couldn’t find elsewhere

## Publication Information

- [Operator](https://paragraph.com/@cybertelx/): Publication homepage
- [All Posts](https://paragraph.com/@cybertelx/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@cybertelx): Subscribe to updates
- [Twitter](https://twitter.com/cybertel_x): Follow on Twitter