You're only ever a fail coder if you give up on solving the bug or problem that made you rage quit. Most folks write a TON of shitty code while they are learning things and if you're not running into bugs or issues that stump you atleast once in a project that you later come back to with a fresh head to fix then you're not building anything that challenges your abilities, ultimately making it "just work" and not the godmode that engineers can get into.

This is why we have testing cycles internally and then publicly so we can find where our code or logic is fucked and fix it to make a better system,

There are lots of resources where you can learn.. Honestly hands on for me, looking at others GitHub or scrolling through stack overflow has helped me far more than any codeacedemy or lessons site has.

Cracking DRM / reverse engineering binaries is still something I need to fuck around with more. Never found a compelling enough reason to dive into it.

Fresh eyes help a lot of the time too, Getting stuck then coming back an hour or day or whatever amount of time later often does the trick.

Enjoy the shower and such capotain.