I saw an article recently with Google search tips for developers. Love this kind of thing! Newbies get hung up on code and forget there are other skills to develop.

The part I didn& #39;t love about the article is that it& #39;s Google-centric. Here are my tips as a @DuckDuckGo user. 1/7
Know the strengths/weaknesses of @DuckDuckGo. The search is great, but it doesn& #39;t find as many discussions as Google. If you& #39;re solving an obscure problem or getting feedback on a specific use case, you might not find your answer. Use the !g bang to try your search on Google. 2/7
Bangs are its greatest strength. Add a bang to your search, and the search is performed on another site instead. Here& #39;s an example. I searched for "podman lando" to see if Lando would work with Podman instead of Docker. (Don& #39;t worry if you& #39;re not familiar with those.) 3/7
DDG didn& #39;t find anything useful for those terms, so I just added the !g bang like this: "podman lando !g"

That takes me straight over to Google with the same search terms. 4/7
You: "If I& #39;m going to do that, why not just search on Google?"
Me: "Bangs become a superpower when DDG is your default search engine. Typing a plain query into your address bar searches DDG, but bangs give you access to other search engines directly from the address bar." 5/7
Here are some @DuckDuckGo bangs that are useful for devs:
• !mdn- @MozDevNet
• !sof- @StackOverflow
• !csst- @css (CSS-Tricks)
• !r- @reddit
• !dev.to- @ThePracticalDev 6/7
You can follow @raddevon.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: