I've been reading discussions about programming and software careers, but I'm increasingly unsure how much of the advice to trust. I have no way to know whether the people giving it have actually worked in the industry, built fast and maintainable software, or even tried their own recommendations. Some advice also seems contradictory or increasingly strange the longer I spend in online programming communities. Am I being overly suspicious, or is there a sensible way to evaluate advice from strangers online?
5 Answers
You don’t have to accept or reject advice wholesale. Treat it as a starting point, then check the reasoning, look for supporting evidence, compare several independent opinions, and test the idea in a small project when possible. Official documentation, technical references, and experienced mentors are usually better sources for factual or technical questions. Online discussions are more useful for hearing different experiences and career perspectives.
You’re not paranoid, but total distrust isn’t useful either. Most online advice is a mix of solid ideas, personal preferences, outdated information, and occasional nonsense. Learn enough fundamentals to reason about the claims yourself, then use trustworthy references and real-world results to separate the useful parts from the rest.
The most important skill is learning to filter advice. Ask what assumptions it depends on, whether it applies to your situation, and whether the person explains why it works rather than presenting it as an absolute rule. Even experienced developers can give outdated advice or describe something that only worked in their particular environment. Use your own judgment instead of blindly following anyone.
Advice is always shaped by the person giving it. A recommendation that worked for a senior developer on a large team may be unnecessary or harmful for someone learning or working on a small project. Ask follow-up questions, clarify the details of your situation, and consider opposing viewpoints before deciding what to try.
For programming questions, verify claims against documentation, source code, benchmarks, and actual experiments. For career advice, look for patterns across people with relevant and recent experience. A confident tone or a long list of years in the industry doesn’t automatically make someone correct, and popularity isn’t proof either.
That applies to advice from professionals too. Experience is valuable, but it doesn’t mean someone’s recommendation automatically fits every project or current job market.