Read the Comments!

June 18, 2013 · 1 min read

Sorry, I have been lax in posting for quite some time. Hopefully this will be the start of a renewed posting binge!

A piece of advice, if you are searching for a solution to an issue, or a recommendation, or anything else on the web, when you find a post or a forum thread do 2 things. 

First, check the date on the post of thread. If it is older it may no longer be fully up to date and or inaccurate. Bear that in mind. 

Second, READ THE COMMENTS! Often small omissions or other issues in the post itself are resolved in the comments. If the solution to your issue does not appear to work check the comments. There may be a step missing or something else relavent that was raised by a prior reader or the author themselves.

Cheers,

Robert Porter

This article is part of the GWB Archives. Original Author: Bob Porter

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.