You read less tutorials, but you actually try to implement more stuff you read about, instead of reading it.
You learn from people. Those who know more, those who know different, those who study CS and those who study art, psychology, gerontology, whatever.
You go over what you learn. You teach, you tutor, you explain, you blog, so you get a better grasp on what you know, so you think about and recontextualize what you take for granted, so you can nail down ideas.
You go back and look at old code you wrote, and fix it. You read code, yours and others, bad code and good code. You submit a pull request to add a feature to something you use.
You stop worrying about being the top whatever, and focus on being better then you used to be.
As an addendum to what adrianhoward said, work with people who are better at coding than you are, then work with people who are worse at coding than you are. You will learns loads of things from both.
++$lots to this. Helping and teaching others is a stupidly effective technique to understand things better yourself.
2) Write lots of code.
3) Repeat.
Now granted, you could teach yourself all of this, but then you'd have a teacher who knows absolutely nothing. It's worth having a mentor to guide you through all this. Doesn't have to be from a university, but it doesn't hurt either.
Please note- there is no top here. Every developer's technique to write code would be different. So, you cant compare yourself with others. You just need to worry about writing efficient code.
- Choose you favorite language ( your can't have same skill in all languages so choose you base language mine is JAVA )
- Work in opensource ( it will give you experience of reading and understanding code of other programmers, also your code will be seen by others )
- Follow tutorials for tasks you have not fully grasp
- Automation ( do automation testing for your code )
hope it might help
I think it's critical to be able to think in languages outside your "favorite" language's paradigms. Java and similar languages, in particular, force you into a depressingly narrow range of looking at problems, and it will hurt your programming skills.