Earlier quoted context omitted.
I've personally found the opposite. In order to advance you need to know the specific techniques or mathematics and there are no hints or information on how to approach the problem. So it boils down to how much of that mathematics you know. If you don't then the brute force approaches take a long time to find the solution.
I think with a few math tricks you can solve around 25-50, It gets very tough after that without maths background.
Project Euler
21–30 of 142 posts
Re: Project Euler
#22Re: Project Euler
#23Re: Project Euler
#24Re: Project Euler
#25Re: Project Euler
#26I have done Project Euler very sporadically since high school. To date I've only done problems 1-54. Despite this, I think the website was a big contributor to my love of programming. I found it before knowing about leetcode and I think it prepared me well. I think I owe Project Euler a decent %-age of my eventual entry into Software Engineering as a field.
Also a great way to learn a new programming language is to try project Euler problems with it.
Re: Project Euler
#27I also love looking back at my old PE code and having absolutely no idea what it doing. No comments, no docs, no notes. From a different era.
Re: Project Euler
#28i was a euler fanatic some years ago reaching problems in the 500s albeit, skipping problems along the way. at that point, too many problems required a deeper math background than i possessed so i abandoned it. what amazed me was that others composed solutions that solved problems in mere milliseconds that brute force approaches would still be running when the universe cooled to absolute zero.
Re: Project Euler
#29Re: Project Euler
#30I love running euler problems when trying to learn the basics of a new programming language. I have a small collection of programs in like 10 different languages that I keep around as a reference for things because I always try to use language-specific features to solve the problems, and then I reference them as examples.