I come across people every day who seem stuck in analysis paralysis concerning some class of software problems. They're typically reading every paper and book

I come across people every day who seem stuck in analysis paralysis concerning some class of software problems. They're typically reading every paper and book they can get their hands and engaging in endless discussions about definitions and hierarchies, but nothing of value seem to come out of the process. I used to read a lot of books and blogs, but what works a lot better for me is to make an honest attempt at solving any problem before seeking assistance. At least then I know what I'm looking for and I always learn something worth knowing along the way.