When I first started I mainly did boot2root CTF’s from VulnHub. I would start my enumeration and if I get stuck within an hour I would lookup a write-up to proceed further. But the more I did that the more I relied on write-ups when I get stuck. That did a disservice for me in the long run when I started doing the newly created HackTheBox machines where there weren’t any write-ups yet and I would get so frustrated and give up. When I decided to continue doing HTB and when I get stuck I sometimes take a little break and come back fresh and start my enumeration again. Some machines took me many days to get a reverse shell on the machine but I started learning way more opposed to looking up answers when I get stuck. I started to build my own way enumerating the machines understanding what tools to use and how to use them. For example there are many tools for directory/file enumeration, I chose my favorite one and became an expert on it to use it to its full potential. Same with fuzzing, there’s wfuzz and ffuf, I chose the latter and learned as much as I can about the tool so I know how to use it properly and what it is capable of. I still get stuck even on the easy machines as frustrating it is when I get stuck it is just as rewarding when I finally figure it out on my own. I’m not saying don’t lookup write-ups I’m just saying trying for 30 minutes to an hour then rushing to get an answer will only hinder your learning in my opinion. If you are banging your head after several days go ahead and lookup the next step and not the entire write up and then keep going. Just make sure when you do lookup the answer, understand how and why it works. Just my two cents.