One thing I see a lot of developers (new and experienced) do is attempt to get around having to really understand the language and libraries they are working with by constantly googling whatever problem they are working on at a given time and assuming there should be an example or blog post out there somewhere that will show them exactly what they need to do.<p>Of course, when the code they find is incorrect, outdated, or not easily applied to their specific situation, they lack the understanding to figure out what they need to do to fix it on their own, so they ask.<p>This of comes out in the form of a question which, to anyone who has taken the time to build such an understanding, smacks of laziness, hence all of the &quot;RTFM&quot; replies.<p>And in that case, RTFM is the absolutely the right answer. They need to slow down, read the problem code, figure out what they don&#x27;t understand, and learn. Maybe they need to slow way down and learn about some of the constructs of the language they are working with. Maybe they need to read the docs for a particular library or framework to figure out what abstractions it relies on. Maybe they just need a high level view of the API so they will know what all is available to them.<p>Could this be communicated in a more friendly way? Sure. Is it the responsibility of the community to do that? I don&#x27;t know.<p>tl;dr RTFM.