27 things I would like to know in advance before starting to program
Hello, Habr! I present to you the translation of the article “27 things I wish I knew when I started programming” by Ken Mazaika.
Before starting to program, I would like to know a lot of things, but here are 27 of them that come to mind. I put the most important ones under numbers 14 and 26, so that it would be interesting for you to read the full article.
The only way to get better at programming is to program. Do not let your efforts be interrupted by paralyzing yourself with analysis.
')
Remembering overflow is not significant.
I use Google to solve most of my problems, like many of the programmers.
I made random changes in my code and expected it to work right away. The disadvantage of this approach is that problems are collected one on top of the other, and it becomes difficult to figure out what went wrong.
Discussing the code and collaborating with other novice developers is the best way to learn for most people.
On the way to programming skills, you will encounter error messages.
In order to grow up in conditions when “tricking” is an integral part of the matter, you must meet punctures steadily.
Contrary to the Hollywood cliche, to be a programmer, you do not need a crazy cascade of monitors. The computer you own now is probably good enough to start programming. Do not waste your money.
It took me a while to get used to the subtle differences between similar characters and start to notice them. Until you get used to it, it can be pretty unpleasant.
At first, I tried to find the cause of each problem I encountered. It's not obligatory. Computers are so complex that you will always have something to learn from them. You will never understand everything at once, and this is normal.
There is no faster way to learn how to write code.
I used to think that every piece of code needed to be made perfect. But making improvements to your code is natural. You are not writing a book so that you cannot change it after publication.
Everyone at some point needs to ask for help. When you are about to do this, follow these four steps:
By following these steps, it is very likely that you will come to a decision without even asking for help. This approach promotes holistic consideration of problems.
If you are not a “mathematician”, this does not mean that you cannot be a programmer.
Creating utilities with code is really cool. I would never get to where I am, if I hadn’t turned around and admired the amazing things that I had created along the way.
In the beginning, it was very scary to get to a level where I would feel comfortable. But as soon as I took part in the meeting, I realized that there were many developers like me.
Merge conflicts are annoying. Therefore, when I realized that I could get to some function before my teammate, so that he (or she) had to deal with it instead of me, I was extremely delighted.
When programming your first tasks, you may be inclined to “pretend until you do.” Don't do this - no one expects you to know everything at once.
In reality, you just need to be generally positive, be prepared to correct and resume an active trajectory when faced with problems. It takes much less time than 10,000 hours.
And when that happens, it's really damn cool.
Once I made a mistake that cost my company 10,000 US dollars. As a result, I learned the most important lesson of my programming career: don't be afraid of situations where you can make a mistake if the risk justifies it. Thanks to this, you, as a developer, will become better.
Algorithms are a step-by-step approach in which there is only one correct next step. The easiest way to imagine this is with the example of a strategy with which you would look for a specific name in the phone book. I wrote about this process here , if you are interested.
There is an impostor syndrome. Try not to forget that knowing not everything is normal. The most important thing is to understand that you are able to deal with what you do not yet know.
New technologies are constantly appearing, therefore successful programmers are those who continue to learn and develop their skills on an ongoing basis.
Too many people have the impression that you need to think like a computer. In fact, the opposite is true.
At your disposal are many different open libraries, tools, and frameworks. Therefore, you need to expand your developer’s tools and understand which tool is more suitable for solving the problems you have encountered.
Learning to program is a big job, especially for the level where you can enter the profession. It takes time and discipline, but it is feasible. Too many people make a mistake - they complete the massive work, almost reaching the desired.
But that is why this is a worthwhile business.
Looking back, in fact, I am very glad that at first I was so naive. Weak knowledge motivated me to critically understand everything that I learned later.
Now I can help other people achieve their programming goals. What could be better?
Before starting to program, I would like to know a lot of things, but here are 27 of them that come to mind. I put the most important ones under numbers 14 and 26, so that it would be interesting for you to read the full article.
1. Learn from practice
The only way to get better at programming is to program. Do not let your efforts be interrupted by paralyzing yourself with analysis.
')
2. Programming is not like preparing for a test
Remembering overflow is not significant.
3. Fraud is perfectly acceptable
I use Google to solve most of my problems, like many of the programmers.
4. Accumulating unverified developments is a bad strategy
I made random changes in my code and expected it to work right away. The disadvantage of this approach is that problems are collected one on top of the other, and it becomes difficult to figure out what went wrong.
5. Learning on your own is very difficult
Discussing the code and collaborating with other novice developers is the best way to learn for most people.
6. Do not be loaded with regrets
On the way to programming skills, you will encounter error messages.
In order to grow up in conditions when “tricking” is an integral part of the matter, you must meet punctures steadily.
7. You do not need 5 monitors
Contrary to the Hollywood cliche, to be a programmer, you do not need a crazy cascade of monitors. The computer you own now is probably good enough to start programming. Do not waste your money.
8. There is a big difference between uppercase and lowercase
It took me a while to get used to the subtle differences between similar characters and start to notice them. Until you get used to it, it can be pretty unpleasant.
9. Trying to understand everything is a hopeless affair.
At first, I tried to find the cause of each problem I encountered. It's not obligatory. Computers are so complex that you will always have something to learn from them. You will never understand everything at once, and this is normal.
10. Participate in pair programming as much as possible
There is no faster way to learn how to write code.
11. Changing bad code is part of the job.
I used to think that every piece of code needed to be made perfect. But making improvements to your code is natural. You are not writing a book so that you cannot change it after publication.
12. Seek help correctly
Everyone at some point needs to ask for help. When you are about to do this, follow these four steps:
- Summarize the details that you have discovered.
- Clearly decide what should happen in your opinion.
- Clearly clarify what is really happening.
- Specify why you think that should work differently.
By following these steps, it is very likely that you will come to a decision without even asking for help. This approach promotes holistic consideration of problems.
13. You do not need to be a genius in mathematics
If you are not a “mathematician”, this does not mean that you cannot be a programmer.
14. Always celebrate small victories.
Creating utilities with code is really cool. I would never get to where I am, if I hadn’t turned around and admired the amazing things that I had created along the way.
15. Mitapas are incredibly valuable
In the beginning, it was very scary to get to a level where I would feel comfortable. But as soon as I took part in the meeting, I realized that there were many developers like me.
16. Avoiding merge conflicts makes you happier
Merge conflicts are annoying. Therefore, when I realized that I could get to some function before my teammate, so that he (or she) had to deal with it instead of me, I was extremely delighted.
17. To admit that you do not know something is normal
When programming your first tasks, you may be inclined to “pretend until you do.” Don't do this - no one expects you to know everything at once.
18. It does not take 10,000 hours to get a job
In reality, you just need to be generally positive, be prepared to correct and resume an active trajectory when faced with problems. It takes much less time than 10,000 hours.
19. Get ready to wake up in the morning thinking about code
And when that happens, it's really damn cool.
20. Making big mistakes is natural
Once I made a mistake that cost my company 10,000 US dollars. As a result, I learned the most important lesson of my programming career: don't be afraid of situations where you can make a mistake if the risk justifies it. Thanks to this, you, as a developer, will become better.
21. The algorithm is similar to finding a name in the phone book
Algorithms are a step-by-step approach in which there is only one correct next step. The easiest way to imagine this is with the example of a strategy with which you would look for a specific name in the phone book. I wrote about this process here , if you are interested.
22. You will never feel that you are ready to program seriously
There is an impostor syndrome. Try not to forget that knowing not everything is normal. The most important thing is to understand that you are able to deal with what you do not yet know.
23. Programmers never stop learning
New technologies are constantly appearing, therefore successful programmers are those who continue to learn and develop their skills on an ongoing basis.
24. Make the computer think like a human
Too many people have the impression that you need to think like a computer. In fact, the opposite is true.
25. Programming is the use of a suitable tool for work.
At your disposal are many different open libraries, tools, and frameworks. Therefore, you need to expand your developer’s tools and understand which tool is more suitable for solving the problems you have encountered.
26. Stop right before the changes for the better - a common act
Learning to program is a big job, especially for the level where you can enter the profession. It takes time and discipline, but it is feasible. Too many people make a mistake - they complete the massive work, almost reaching the desired.
27. Learning to program is not easy
But that is why this is a worthwhile business.
Looking back, in fact, I am very glad that at first I was so naive. Weak knowledge motivated me to critically understand everything that I learned later.
Now I can help other people achieve their programming goals. What could be better?
Source: https://habr.com/ru/post/461175/
All Articles