{"id":8563,"date":"2017-04-04T07:53:09","date_gmt":"2017-04-04T07:53:09","guid":{"rendered":"http:\/\/graphenelive.in\/?p=610"},"modified":"2017-04-04T07:53:09","modified_gmt":"2017-04-04T07:53:09","slug":"things-keep-mind-start-learning-programming","status":"publish","type":"post","link":"http:\/\/graphenelive.in\/things-keep-mind-start-learning-programming\/","title":{"rendered":"Things to Keep in mind when you start Learning Programming"},"content":{"rendered":"

1. Learn by doing<\/h3>\n
The only way to progress in programming is to actually start writing programs.<\/div>\n

2. Programming is not the same as learning to do the test<\/h3>\n

Remembering everything is not important.<\/p>\n

3. Fraud is completely acceptable<\/h3>\n

I use Google<\/a> to solve most problems, just like every other programmer.<\/p>\n

4. Putting problems together without checking is a bad strategy<\/h3>\n

I’ve made changes in my lines of code and expect them to work. The problem with this approach is that it overlaps one issue on another, and it’s hard to find out what has happened.<\/p>\n

5. Self-study is a really difficult job<\/h3>\n

Talking about code and collaborating with fellow developers is a better way to learn for most people.<\/p>\n

6. Give up your emotions<\/h3>\n

You will see the error message on the journey become a programmer. As it becomes an indispensable part of programming, you need to accept mistakes to progress.<\/p>\n

7. You do not need 5 screens<\/h3>\n

Contrary to what you see on Hollywood movies, you do not need to install multiple monitors to be a programmer. The computer you own is probably good enough to use and start programming. Do not waste your money!<\/p>\n

8. There is a HUGE \u00a0difference between a capital letter and a lowercase letter<\/h3>\n

It takes some time getting used to recognizing the small difference between the identical icons and can be quite frustrating until you get used to it.<\/p>\n

9. Trying to understand everything is a cause of failure<\/h3>\n

When I first started, I tried to answer the “why” question for every problem I encountered. This is not necessary. Computers are complex and there is so much to learn and you will never understand everything. That’s fine.<\/p>\n

10. Program in pairs<\/a> as much as possible<\/h3>\n

There is no faster way to learn how to code.<\/p>\n

11. Changing bad code is part of the process<\/h3>\n

I used to think that every piece of code I write should be perfect. But improving your code is normal. You do not write a book without calibration before it is published.<\/p>\n

12. There is a right way to ask for help<\/h3>\n

Everyone needs to ask for help at some point. And when you need help, make sure you do the following:<\/p>\n