As a programmer, you probably rely on your network of peers, mentors, and online communities to learn new skills, solve problems, and get feedback. But how do you evaluate the quality and relevance of the programming advice and resources you receive from your network? Here are some tips to help you assess the information and guidance you get from other programmers.
The first step is to check the source of the advice or resource. Who is the person or organization behind it? What are their credentials, experience, and reputation? How do they relate to your specific goals, needs, and interests? You want to look for sources that are credible, trustworthy, and aligned with your learning objectives. For example, if you want to learn web development, you might prefer advice from a professional web developer who has built successful projects and has a portfolio to show for it.
When I first started programming, I joined an online community and asked questions. I got helpful advice, but also some that didn't fit my needs. One day, I got stuck and someone suggested a new library. I tried it for hours, but couldn't figure it out. Frustrated, I realized I hadn't checked the source of the advice. I researched the library and found that it was created by a small team with little experience. I also found more popular libraries with better documentation. I switched to one of those libraries and was able to solve my problem. Lesson learned: Check the source of programming advice before following it and that it's not out-of-date. Make sure the source is credible, trustworthy, and aligned with your needs.
The next step is to verify the accuracy of the advice or resource. Is it based on facts, evidence, and best practices? Is it up to date and relevant to the current standards and trends in programming? Is it consistent with other reliable sources and your own knowledge and experience? You want to avoid sources that are outdated, inaccurate, or misleading. For example, if you want to learn Python, you might want to avoid resources that use Python 2 syntax, which is no longer supported, or that teach bad habits or anti-patterns.
I've done this mistake for a long period, which is not checking the OFFICIAL DOCUMENTATION of the technology I'm supposed to learn. Some documentations like MongoDB, FastAPI etc. are very very well structured and don't require external YouTube videos, Udemy Courses etc. for their understanding. And since it's the official documentation, it's never outdated, inaccurate or misleading.
The final step is to evaluate the usefulness of the advice or resource. How does it help you achieve your learning goals, solve your problems, or improve your skills? How does it fit your learning style, preferences, and level of expertise? How does it challenge you to grow and learn new things? You want to look for sources that are relevant, practical, and engaging. For example, if you want to learn data analysis, you might want to look for resources that provide real-world examples, exercises, and projects that you can apply to your own data.
One of the benefits of having a network of programmers is that you can get different perspectives and opinions on various topics and issues. However, this also means that you have to be careful not to rely on a single source or viewpoint. You should seek multiple perspectives and compare and contrast them to get a broader and deeper understanding of programming. For example, if you want to learn a new framework or tool, you might want to read reviews, tutorials, and blogs from different developers who have used it.
Another way to assess programming advice and resources from your network is to ask questions. You can ask questions to clarify, verify, or challenge the information or guidance you receive. You can also ask questions to seek more information, feedback, or recommendations. Asking questions can help you learn more, improve your critical thinking, and build relationships with other programmers. For example, if you want to learn a new algorithm or technique, you might want to ask how it works, why it is useful, and what are the pros and cons.
The ultimate way to assess programming advice and resources from your network is to test it yourself. You can try out the code, tools, or methods that you learn from your network and see how they work for you. You can experiment, modify, and improve them to suit your needs and preferences. You can also measure and evaluate the results and outcomes of your learning. Testing it yourself can help you verify, apply, and reinforce your learning. For example, if you want to learn a new language or library, you might want to create a small project or app using it.
One sources is not enough. If you want to really assess resources and programming advice from your network for the future , you need to get few and learn who you can confidently rely on for next time using the advised above.