Little Experience :
I am sharing my personal experience about learning hacking . Also how did i learn hacking . I am not an expert hacker . I was very curious about hacking and hackers in old days . I thought that after being a hacker life will be very easy and fruitful . But when I started learning the things got started to become complicated . Firstly I started learning from Udemy but all the free course were click bat . I don’t know about the paid one because I haven’t learned from them . After this i started to search ” learn hacking ” but i didn’t find good post or videos for learning . But I continued searching and finally found one site full of hacking tools and Videos . The Link is given bellow before that please read this things to know about hacking more and easily .
What Is Hacking?
The “hacking” we’ll be discussing in this report is exploratory programming in an open-source condition. On the off chance that you think “hacking” has anything to do with PC wrongdoing or security breaking and came here to discover that, you can leave now. There’s nothing for you here. This post will help you to learn hacking very easily .
Interpretations of this report are accessible in: Hungarian
Hacking is primarily a style of programming, and following the proposals in this record can be a successful method to procure broadly useful programming aptitudes. This way isn’t ensured to work for everyone; it seems to work best for the individuals who begin with a better than expected ability for programming and a reasonable level of mental adaptability. Individuals who effectively take in this style have a tendency to end up generalists with aptitudes that are not firmly fixing to a specific application area or dialect.
Note that one can be doing hacking without being a programmer. “Hacking”, extensively, is a depiction of a technique and style; “programmer” infers that you hack, and are additionally joined to a specific culture or verifiable convention that uses this strategy. Appropriately, “programmer” is a honorific offered by different programmers.
Hacking doesn’t have enough formal device to be an undeniable technique in the way the term is utilized as a part of programming building, yet it has a few attributes that tend to separate it from different styles of programming.
Hacking is done on open source. Today, hacking aptitudes are the individual smaller scale level of what is called “open source advancement” at the social full scale level. A developer working in the hacking style expects and promptly utilizes peer audit of source code by others to supplement and open up his or her individual capacity.
Hacking is lightweight and exploratory. Unbending methodology and expound from the earlier particulars have no place in hacking; rather, the inclination is attempt it-and-discover with a fast discharge beat.
Hacking places a high incentive on particularity and reuse. In the hacking style, you make a decent attempt never to compose a bit of code that must be utilized once. You predisposition towards making general instruments or libraries that can be specific into what you need by solidifying a few contentions/factors or providing a unique circumstance.
Hacking favors scrap-and-reconstruct over fix and-broaden. A basic piece of hacking is mercilessly discarding code that has progressed toward becoming over complicated or crufty, regardless of how much time you have put resources into it.
The hacking style has been nearly connected with the specialized convention of the Unix working system
As of late it has turned out to be apparent that hacking mixes well with the “spry programming” style. Light-footed procedures, for example, match programming and highlight stories adjust promptly to hacking and the other way around. To a limited extent this is on account of the early idea pioneers of coordinated were impacted by the open source network. Be that as it may, there has since been activity the other way too, with open-source extends progressively receiving strategies, for example, test-driven advancement.
Phases of Learning How To Hack
Figuring out how to make music has three phases. To start with, you need to take in the fundamental mechanical method of an instrument — fingering and how to play scales. At that point you need to prepare your ear to comprehend melodic examples. At last, you should figure out how to recombine melodic examples into unique manifestations. Hacking is comparable.
What might as well be called fingering is taking in the capacities of programming dialects, and the mechanics of utilizing devices like editors, mediators, and compilers. (On the off chance that you don’t comprehend these terms, see The Unix and Internet Fundamentals HOWTO.) We won’t cover those mechanics here as they differ excessively as per what dialect you’re utilizing. Instructional exercises for every one of the dialects you should need to utilize are accessible on the Web; utilize a web crawler.
What might as well be called playing scales is composing little projects, alone. Sadly, playing scales (a) doesn’t show you anything about music, and (b) is exhausting as hellfire. So also, written work toy programs doesn’t tend to show you much about hacking, and (b) will keep an eye on uninspire you except if the program quickly takes care of an issue you think about.
Most formal programming guideline gets to playing scales and stops. Along these lines, it tends to create coders who are poor at working together with each other and have what might as well be called no ear for music — a poor vibe for programming outline and design.
The Incremental-Hacking Cycle
There is a superior method to learn. I call it the incremental-hacking cycle.
To start with, pick a program that accomplishes something you are keen on. In a perfect world, it ought to be a program you utilize frequently and have sentiments about. The following best thing is a program you don’t ordinarily utilize, yet that accomplishes something you believe is fascinating. For this learning strategy to work, you ought to abstain from attempting to hack on code that bores you.
The program you pick doesn’t need to do anything genuine. Numerous developers have sharpened their abilities by enhancing recreations that they delighted in. The main disadvantage to this is present day amusements are frequently very expansive and convoluted, and might be outside the ability to understand of a crude apprentice. Hence, you might need to examine one of the great content arranged diversions that still survive; nethack is a prime illustration, and there are numerous others.
In the event that you don’t definitely know the program, figure out how to utilize it. Read the documentation. Build up a psychological model of how it functions.
Pick a little component to change or include.
Hunt the code until the point that you discover the part you have to adjust.
Note: you ought to explicitly not endeavor to peruse the whole program. You will simply debilitate and baffle yourself on the off chance that you do that. Rather, utilize the module structure of the code to focus in on simply the part you have to get it. En route, you will learn things about how the entire program fits together.
It’s a decent exercise to add illustrative remarks and notes to the code as you make sense of things about it. This will encourage your memory, and will enable you to sort out your contemplations also.
Make, test, investigate, and record your change.
Reporting your change is essential. On the off chance that you build up the propensity for doing this early, you’ll deliver considerably higher-quality work.
Send your change as a fix to the program maintainers. See the Software Release Practice HOWTO for tips on the most proficient method to do this in a successful and courteous way.
I initially portrayed this as a discretionary advance; a savvy companion called attention to that most likely I shouldn’t have. Lone noodling on your instrument is all exceptionally well for training, yet music is finished and approved when the innovativeness in it is heard by other individuals. Lone noodling on your PC is correspondingly useful for training, yet hacking is finished when other individuals utilize what you composed. That certifiable test is vital.
In some cases (oftener when you are simply beginning) your patches will be rejected. You have to figure out how to adapt to this. It doesn’t mean you’re destined to flop in your journey; for the most part what it means is that you have not perused the code deliberately enough, or (similarly as more often than not) you have missed something essential about the way of life and practices of the development gather you are endeavoring to add to. These slip-ups can be repaired.
Presently, ask yourself: do I comprehend this whole program?
In the event that yes, you’re finished. Assuming no, return to stage 3. This time, pick an alternate and maybe somewhat more troublesome thing to change.
The purpose of this activity is to figure out how to sneak up on the issue of understanding a program, instead of endeavoring to handle the greater part of the multifaceted nature on the double. As you experience this circle a few times, you will steadily build up a more total portrayal in your brain of the way the entire program fits together. Sooner or later you will achieve an edge where you comprehend everything — or at any rate enough of it for whatever your last intention is.
Building up Your Design Sense
To prepare yourself, begin little. In the event that conceivable, first do the incremental-hacking cycle as an activity on little projects or contents, 10-50 lines. These might be elusive, as most projects of any utilization are bigger than this. Most projects this little are contents in shell, Perl, Python, or Tcl; that is a characteristic to search for while trawling the Web for them.
When you have done the incremental-hacking cycle on a few little projects (or on the off chance that you are sufficiently unfortunate to not locate any reasonable little ones), attempt it on marginally bigger projects. Search for codebases in the scope of 100-500 lines.
When you ace that level, go to the request of size, 1000-5000 lines. When you ace the 1K-5K level, you will have entered the base end of the ability scope of what is typically viewed as a talented developer.
At or before the 1K-5K level, you ought to once in a while start to see that you are having tingles to change the structure or association of a program, not only its highlights. You may wind up deduction “This code is revolting” and having emotions about making it prettier and more clean.
At the point when this happens, focus. This is your outline sense attempting to wake up. Try not to hurry to fix in another element. Rather, begin to investigate the program that gives you this tingle at a more elevated amount. Presently may be a decent time to attempt to peruse all the code, however don’t be excessively concerned on the off chance that you can’t; most projects are simply too huge and untidy for swallowing them down at the same time to work. Simply endeavor to get it together on what you have to know to tidy things up.
You are currently entering the middle of the road segment of figuring out how to hack. This includes not only evolving surface-unmistakable highlights but rather doing what is called “refactoring” — redesigning the code inside with the goal that it is cleaner and has better engineering (better stowing away of information, smaller interfaces between various parts, more utilitarian partition among modules).
Once your outline sense (your likeness melodic ear) is initiated, you’ll regularly find that you begin refactor and this will make you easy to learn hacking and become a hacker .