[tastyminerals2]

I tried doing some LeetCode problems and found that the time I spent making sense of their task descriptions is just not worth it. They are a mixed bag and some of them are simply not well written to a degree that you feel stupid while spending hours to make your code pass their tests. Is it some elaborate scheme to make you pay and use the debugger? In the end I simply didn't enjoy the process.

What I really liked going through though are project euler and 4ever-clojure problems. It's subjective but I suspect it's because you don't need to read through paragraphs of text before starting to write a solution. It's the opposite, the small problems with clear goals leave you with more space for creativity and urge you to write more code in the end. I personally found the hours spent on such problems to be more productive.

[arihantparsoya]

There are definitely problems whose description is not well written. You can validate that by reading the comments on the problem.