> best practices may not be obvious even when reading the docs I am right now working on a project because of the googling stuff has led to the worst practices

> best practices may not be obvious even when reading the docs I am right now working on a project because of the googling stuff has led to the worst practices at the moment. I have worked on many projects where people haven't bothered reading the docs and I have seen the same pattern for over a decade. Whereas if they had read the docs the best practices would have been immediately apparent. So that argument hold no water with me. > one can't assume that in a big doc, it's obvious where the solution for a problem is, which may force to read way more than expected I want people reading more. Which was part of my overall point. People don't read enough. They go for the quick solution (which is copy and paste from stack overflow) produce something which is usually quite bad and then you normally have to redo that work because the moment you try to change something (due to changing requirements) the whole thing falls to pieces. I've been guilty of it too. It is a bad habit that is produced through laziness. I literally wrote docs at a previous place and people kept on asking for help on IM. I wrote the document so I wouldn't have to answer the same questions many times. People getting into bad habits and not looking for or writing docs literally causes a hell of a lot more issues that you would see at first glance. > Thinking about it, the major problem seem to me unprocessed copy/paste, rather than "googling instead of RTFM'ing". I would rather have a unprocessed copy and paste then what you get in reality which is a "copy pasta". There are minor bits changed which make it difficult to recognise where it may have originally come from, which makes it difficult to know the original developer's intent.