I am stuck in a wall of "I want to do something with (topic)".
This all started when I encountered "Hypervisor Bypass" a couple of months ago in terms of game piracy. I thought, "*technically yes, this is not a crack, but a bypass. But how the fuck did these people even discover this?*". And I fell into the low-level rabbit hole. My priority really is reverse engineering, anything cybersecurity, and delving deeper into exploitation.
But recently, I also wanted to do "forward" engineering alongside this; like creating a tangible, visible low-level output just like how we see in fullstack / software development. So now, I'm stuck in this wall of "I want to do something with (topic)" but in my case, it's Hypervisors.
I am saying I am stuck in this wall because, I literally cannot move forward from it. This is how I've approached creating projects before but this time, I'm stuck because I only have the high-level knowledge of the topic I want, and I cannot name the "What do I specifically want?". There have also been times when I did have a conceptual understanding of a topic, but I still cannot name a something I want to create because I think I wired myself to be obsessed to always aim to create something innovatively absurd.
Can I not name anything because I don't have a knowledge of that area yet? What is this really and how can I approach this (dilemma?)
I have Learnt C for the past 3 months, and now studying Assembly through OST2. After this, I plan on reading and doing really deep work on OSTEP (people say its projects & activities are really rigorous too). Maybe after that, I can have more ideas?