{"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":"
Remembering everything is not important.<\/p>\n
I use Google<\/a> to solve most problems, just like every other programmer.<\/p>\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 Talking about code and collaborating with fellow developers is a better way to learn for most people.<\/p>\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 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 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 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 There is no faster way to learn how to code.<\/p>\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 Everyone needs to ask for help at some point. And when you need help, make sure you do the following:<\/p>\n As you go through this process, you will often find a solution without even asking for help from someone else. This helps you think about the issues in a comprehensive way.<\/p>\n If you are not a “mathematician”, that does not mean you can not become a programmer.<\/p>\n Building stuff with code is really great. I could never get to the present if I did not step back and admire the wonderful things that I created on my journey.<\/p>\n At first, it was scary for myself to feel comfortable attending meetings. But once I do that, I realize that there are many other developers like me.<\/p>\n The merge conflicts are quite annoying. (The following passage reads so I do not translate)<\/p>\n When you start your first programming job, you may tend to “pretend to know until you do it”. Right! Nobody expects you to know everything right away.<\/p>\n In fact, you need to be good at repairing yourself and back on the track<\/b> when problems arise. This takes less than 10,000 hours.<\/p>\n And when that happens, it’s really cool.<\/p>\n I made a mistake that cost my company $ 10,000. Thanks to that, I learned the most important lesson in my programming career.<\/p>\n Algorithms are a step-by-step approach where there is exactly one more step. An easier way to think about this is to strategy you need to do to find a specific name in the directory.<\/p>\n4. Putting problems together without checking is a bad strategy<\/h3>\n
5. Self-study is a really difficult job<\/h3>\n
6. Give up your emotions<\/h3>\n
7. You do not need 5 screens<\/h3>\n
8. There is a HUGE \u00a0difference between a capital letter and a lowercase letter<\/h3>\n
9. Trying to understand everything is a cause of failure<\/h3>\n
10. Program in pairs<\/a> as much as possible<\/h3>\n
11. Changing bad code is part of the process<\/h3>\n
12. There is a right way to ask for help<\/h3>\n
\n
13. You do not have to be a mathematical genius<\/h3>\n
14. Always celebrate small successes<\/h3>\n
15. Meetings, chat is very valuable<\/h3>\n
16. Avoid merge conflicts to make you happier<\/h3>\n
17. Recognize what you do not know is okay<\/h3>\n
18. It does not take up to 10,000 hours to be good enough to get a job<\/h3>\n
19. You will wake up in the morning and think about the code<\/h3>\n
20. Making big mistakes is normal<\/h3>\n
21. An algorithm is like finding a name in the directory<\/h3>\n
22. You will never feel you are ready to program full time<\/h3>\n