Cease your study of hacking.

Are you trapped in a perpetual loop of studying hacking without actually engaging in it? It’s time to break free from this cycle.

Yes, you heard me right, It’s time for you to stop studying Hacking.

Stop Hacking

Absolutely! Set aside those books, close those Reddit tabs, and embark on a journey to become a true hacking pro!

In fact, what if I told you that the extensive time you dedicate to studying hacking or delving into specific bugs might be precisely why you find it challenging to truly grasp the subject?

Hacking or bug hunting is not a science; it is a skill honed solely through consistent practice.

If you’re eager to plunge into the exciting world of hacking, all you need to have open are your trusty VM, BurpSuite, and Google.com.

But here’s the thing — deep down inside, you probably already know this. So, why aren’t you out there finding bugs and hacking away? The reason might be that you’re not attempting to find bugs due to a deeper root problem, preventing you from doing the work you already know you should be doing.

I’ve learned this the hard way and realized that typically there are three core reasons that hinder people from sitting down at their computers and actually practicing. It’s often one of these three reasons that causes people to struggle with finding bugs. If you didn’t have any of these three problems, you would be hunting bugs every day, and it wouldn’t be a challenge for you.

Ultimately, regardless of whether you believe you’re intelligent or consider your background, you can learn it.

Let’s delve deep into these three core reasons that might be holding you back, and trust me, you’re not alone.

1. The Paralysis of Perfectionism

What if I told you that you are actually waiting for that perfect moment when you’re fully prepared to dive into hacking? Well, guess what? The truth is that won’t happen in a day or two. In fact, you don’t need to be a hacking genius to get started. The absolute best way to start finding more is just to begin thinking about how things work, such as how you would access a website as a regular user with your own style. Start with a simple idea and just go for it. Don’t worry about finding something monumental right away. The key is to start, even when you feel unprepared. As an engineer or analyst, your strength lies in your ability to figure things out on the fly.

As an engineer or analyst, you’re not supposed to know what to do. But you are supposed to know how to figure it out.

The Paralysis of Perfectionism

This marks the primary reason why you might be stuck watching additional tutorial videos. Cease viewing numerous YouTube tutorials and commence your hacking journey. Learn through practical experience, much like the rest of us. Keep in mind, you don’t have to possess all-encompassing knowledge; resourcefulness is the key.

For Example

Simply choose a target, fire up your Burp, and dive in. It’s not about using a specific framework or anything of the sort. The essence is, each day, I initiate my tasks with no clue about how to achieve them. Yet, I navigate and figure it out along the way. I still Google how to center a div every time I delve into CSS.

2. Analysis Paralysis

Have you ever felt overwhelmed by the multitude of options when purchasing a new computer? It’s a sensation akin to deciding how to embark on your hacking journey. Should you delve into hacking tools and Kali, concentrate on front-end development, or perhaps opt for full-stack to cover both front-end and back-end opportunities? The possibilities appear limitless, and that’s what has been hindering your progress.

So don’t overcomplicate things. Choose one path and stick with it. You can always pivot later if needed. Commit to a direction, build your skills, and you’ll find your way.

Let’s take a Example to understand it

In essence, let’s discuss how Apple has managed to deceive many of us with their MacBooks. When you’re in the market to purchase a product, such as a computer, and you peruse reviews for all the available options, delving into the realms of Dell, HP, Lenovo Y7, and the like, it becomes a process of weighing the pros and cons. You assess factors like graphics capability for gaming, durability such as the toughness of the ASUS TUF, and more. This is precisely how Apple has led many to opt for their products. Convincing oneself to buy a MacBook simplifies the decision-making process, offering a more straightforward selection from the limited two to three options with customizable specs, as opposed to navigating through the extensive array of 200 Windows options. This parallel phenomenon occurs when novice bug hunters grapple with the overwhelming choices at the outset.

3. The Smart ass vs. Dumb ass Dilemma

Believe it or not, sometimes it’s better to be a little “dumb” when you’re learning to code.

Let’s break it down with a Example

The “dumb” individual initiates the learning process by tackling HTML, CSS, and JavaScript, constructing a basic website without delving into the intricate workings of these languages. Despite not fully comprehending the underlying mechanisms, confidence builds, and learning progresses incrementally.

Conversely, the “smart” individual dedicates time to theoretical understanding, delving deep into concepts like hash maps before embarking on practical projects. The outcome? Less learning compared to the “dumb” counterpart, who actively engages in creating and experimenting.

The takeaway? Don’t strive for perfection or aim to be the most knowledgeable person in the room. Begin with a simple project, get hands-on experience, and learn through practical application. While theory holds value, its effectiveness is maximized when applied to real-world problems encountered.

Breaking it down further, there are instances where theoretical learning proves beneficial. However, it is most effective when pursued after encountering several situations where understanding is lacking, such as struggling to comprehend how user effects work. At that point, investing 30 minutes to learn the foundational theory becomes opportune.

So, let go of the need to be “smart”, be humble and embrace the process of becoming proficient. Build, add features, make mistakes, and keep learning.

Here in this blog, I shared the three biggest mistakes that I made and I really don’t want you to make them too. Also I just want you to know that it’s okay. I was there too. Even after you get over these three core reasons, you’re still prone to make lots of mistakes when you’re bringing it. So I highly recommend you go give it a shot live with the flow and until next time Happy Hacking!