# The rules of finding accurate instructions for doing something technical

By [Operator](https://paragraph.com/@cybertelx) · 2022-10-16

---

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

---

*Originally published on [Operator](https://paragraph.com/@cybertelx/the-rules-of-finding-accurate-instructions-for-doing-something-technical)*
