Coding Career Advice: Searching and Evaluating Online Information Efficiently

This is a post in the Coding Career Advice series.

How to efficiently find and evaluate information online

Tip #3: Searching and Evaluating Online Information Efficiently 🔗︎

A while back I saw this excellent quote on Twitter:

When I learn something today, I usually do it by piecing together clues gleaned from out of date tutorials and random forum posts until a coherent picture forms, and that is a skill you should practice relentlessly because it's the most valuable skill you will ever acquire.

I attribute much of my success as a developer to my ability to search for information online quickly and efficiently, absorb key pieces of info from the relevant search results, and then synthesize that information into a potential solution.

To be honest, this is a really hard topic for me to write about, because it's something I've been doing my whole online life. It's kind of like trying to describe "How to learn and speak English" as a native speaker. It's not something I can exactly describe based on learning it, because it's a skill I naturally developed back during the dawn of the Web. It's also not something I think about, because by now it's entirely instinctive. Similarly, I can't go tell anyone "start using the internet back in 1995", or "spend most of your childhood learning to speed-read" - clearly that doesn't scale or actually help anyone else :)

That said, I firmly believe that developing a strong ability to search for and evaluate information online is a key skill that every developer should aim for. I actually already described a form of this in my earlier post on evaluating software libraries and tools.

Here's my suggestions for a general set of steps to follow.

Suggested Search and Evaluation Process 🔗︎

Know what it is you're trying to find. Obviously you don't know the exact details yet, otherwise you wouldn't be looking :) But, think of it as drawing an outline, and then trying to find a picture that matches that outline. The better idea you have up front of what you're looking for, the easier it is to look at a result and say "this does or does not match what I'm looking for"

Know where to look for relevant information. Google is the typical starting point, but I'll use the search feature on other sites for specific things: NPM for JS libraries, Twitter for tweets, Github for code repos or usage snippets, and so on.

Use specific phrases and keywords as part of your search. You might not even know what the relevant keywords are to begin with, but after opening up a few initial results, you might find some info that's in the same general category as what you're looking for. Start up a new search using specific relevant phrases you just found, and keep narrowing the results down based on those. (I'll throw an extra-special shout out to Shawn Swyx Wang's post on "How to Google Your Error Messages", which both has some excellent advice for a common problem and tweet-quotes me in the process.)

Learn to skim search results quickly and do an initial filtering pass based on likely relevance. This includes looking at page titles or software library names, "last updated at" dates, URLs, and anything else in the actual search results list that can give you a sense of whether a given result is likely to be relevant and trustworthy. Learn to immediately disqualify search results as "too old", "likely spam or clickbait", or "just not relevant" as you move your eyes down the results list. Pop open potential candidates in a new tab for later review, and keep skimming results.

Once you've got an initial set of potentially useful results opened up, skim the pages and get a sense of what the actual content is and whether it's worth looking at further. Consider the source (blog, docs site, tutorial), date, author, length, apparent level of detail, and overall content. If it doesn't look relevant, close the tab and move on to the next one. The emphasis here is on trying to figure out which of these results should be kept for the the real deeper reading and understanding portion of the process.

Now that you have a good list of likely meaningful results, go back through them in more detail. You might want to take notes on your findings, bookmark some of the results and save them for later, or start up new searches based on some of the keywords you find.

Finally, you should have accumulated a good set of info from across all these results. Maybe none of those pieces of info directly solves your problem by itself, but it's possible to take some of the info as a basis for putting together your own solution. Think of it as lego blocks - maybe you didn't find a complete pre-assembled kit, but you've got enough blocks that you can build something yourself.

Note that these steps aren't limited to Google searches. They apply as you look at just about any other search site or tool, even if you're looking for something like a software library on NPM.

Additionally, one of the main reasons why I still use Firefox as my primary browser is the Tree Style Tabs addon. It lets you switch from a row of tabs on top of the browser, to a sidebar that has a tree of tabs that can be nested and collapsed at any level. This makes it much easier to have a large number of tabs open at once, including grouping results from different searches based on the starting page. (My understanding is that Chrome addons can't do the same kind of UI changes that Firefox addons can, and last I checked there wasn't a good equivalent of Tree Style Tabs for Chrome. Could easily have changed since the last time I looked, though.)

Examples 🔗︎

I'll briefly describe some specific cases where I went through this process myself.

Git History Rewriting 🔗︎

In my post Rewriting Git History and JS Source for Fun and Profit, I described how I completely migrated our team's Git repository history, by stripping out unused files and rewriting the JS source to modernize it at all points in the history of the codebase.

When I started this task, I had some prior experience with rewriting Git history. I frequently used commands like rebase in my daily work, and I had used git filter-branch a few times. I also generally understood how Git's data structures worked, and that tools like JS codemods existed. So, I understood the general shape of what I wanted to do ("create an alternate Git history but with changed content", "rewrite JS source automatically on a large scale") and key terms that I needed to look for ("git filter-branch", "rewrite Git history", "JS codemod"). I also assumed that what I wanted to do must be possible, somehow - I just didn't know the exact technical details of how.

I probably spent at least a week doing initial research on this. I didn't find an exact solution, but I did find several critical resources that gave me much deeper understanding, key terms to look for, and ideas that shaped my potential solution:

None of those pieces by itself was the entire solution, but together they gave me enough understanding to figure out how to build the actual solution I needed.

By the time I was done building this, I had learned enough to write a 6000-word blog post on the topic, off the top of my head, in about 5 hours :)

I started this evening by searching online and evaluating info on how to search online and evaluate info efficiently. (How meta!)

My first search was for how to search for information on the internet. In a sense I didn't follow my own advice here, because that's more of a question or a phrase than specific keywords, but I didn't quite know where to start looking for details on this topic. Most of these results were either blogspam about search engine optimization, or too narrowly focused on how to actually type things into a search engine rather than how to look at the results. I also avoided any results with dates older than the last couple years, on the grounds that they probably weren't as relevant.

That initial search turned into effectively evaluating search results, which produced some better hits. I also saw the phrase "digital literacy", realized that was a relevant aspect of this topic, and searched for digital literacy searching for information. These queries gave me some better results, including a number of academic-related pages like university libraries.

Ultimately, I didn't end up using those resources to write this post, but I have linked the best results in the "Further Information" section below.

React-Redux, React Native, and Jest 🔗︎

Last year I fixed a bug in React-Redux where it broke under React Native. As part of that, I needed to update our test suite to make it correctly test behavior with React Native, vs just ReactDOM.

I remember having seen a tweet that day about "all the stuff I googled in a week as a software developer", so for fun I wrote down every Google search I did while trying to solve this particular React Native test setup problem. This included searches like react uselayouteffect ssr to find a particular issue thread I knew existed in the React repo, jest mockComponent.js Support for the experimental syntax 'classProperties' isn't currently enabled to find a solution to a particular error message I was seeing, and microsoft ipod naming as a sidebar based on a discussion with a friend, to find the classic Microsoft self-parody video on how they're so bad at naming things.

Further Information 🔗︎

This is a post in the Coding Career Advice series. Other posts in this series: