Didn't expected so much answers, thanks everybody for helping me out! Hope to recieve such help form yo in future also!!

:))

Reading is a discussion. Every one of the books talks. Be that as it may, great book tunes in too. You don't need to consume books to decimate a culture. Simply motivate individuals to quit understanding them. Instruction starts the courteous fellow, yet Essay Writing Online perusing, great organization, and reflection must complete him.

Do them simultaneously! Practice coding while you are reading/learning about programming. Type out the examples, expand upon them. Change them slightly and just enough to prove you learned what you just read.

Short answer: Both.

Long answer: Anyone should be reading on theory and analysing other people's code whether that's some of the classmates or some random people that seem to be at their level or lower and more importantly the code of experienced and knowledgeable coders. You should also code as you learn and not relying on the passive learning that can get you through school and uni. Why? Because:

1. You need to know concepts such as data-structures; when to use or not to use arrays, hashmaps, ..., algorithms and design patterns as well as understanding the paradigm used/available for a language you're learning.
2. Reading other people's code will help you see solutions from different perspectives and see how someone went about solving a problem and trying to understand what they did better or/and worse than you. It will also expose you to APIs, techniques, code styles, tools etc that you may not have encountered yet.
3. You should always be learning (especially in an always-evolving industry like ours).
4. Passive learning is not as helpful as hands-on (active) learning where you get to put your knowledge into use and practise it.

It depends on your own learning style.

For me it’s read a little, practice/experiment a lot. My sister needs more reading and only a little practice. (OK, I can also do it her way, I just like to get my hands dirty.) A friend of mine can’t learn anything if she’s not in motion; if you want her to understand some new concepts, take her to a walk.

Learning is a really tricky thing. You have to discover your own learning style instead of asking random strangers on the InterWebz.

Reading is knowledge, practicing is wisdom. You must have heard of people who had little knowledge but had a lot of wisdom because they kept practicing what little they knew and started learning as and when required. What practice gives you is experience and a much-needed skill of pattern recognition. Experience helps you learn from mistakes that reading can't teach you, and pattern recognition helps you save time, this again, cannot be learned from a book. So I believe in reading when required.

Coming from someone, who never read and got 100% hands-on practice, do read a little. But not too much. Work on something and learn on the go. Create something you like, so you stay super-motivated. And if you lose interest, don't be afraid to start building something else or throwing your earlier projects away.

Imho, learning a programming language is a lot like learning a natural language. Sure, there are some parts which are best read in books (vocabs, grammar, foreign script), but if you want to speak it, speak it. There's no better way to become fluent!

I follow 20% reading and 80% practice usually when learning programming language i first learn basics and try to build a simple CRUD app then after that i try to build something big like something using api's and then go for testing in that language, then for frameworks, I read as i build like while making app if i come across any new method of function , i try to read about that.

Read a little an practice it. This not one or the other both are crucial parts of the learning experince. Combined well it boosts your skills.