No matter which junior programmer is involved in a certain field, no matter how ambitious he or she is, he or she will be overwhelmed by the confusion: not knowing what to do or what to do. Here are the lessons I learned as a software developer that I hope will be helpful to everyone.
1. Don’t be afraid to learn on the job.
As long as you have a computer, you can read newspapers and most books through an e-reader. If you just do your job and the assigned tasks, you won't learn much. It's impossible to improve yourself if you blindly ask for more work. Slow down and pick up some basic knowledge first.
2. Move forward courageously in your career and take responsibility for yourself.
Only one in ten people can get special care from their mentor. If you are one of nine out of ten, it means that no one will take care of you most of the time. So you have to take care of yourself. If you can, try to avoid jobs that don't advance you or teach you anything: because it won't add value to your career, and others won't care about the effort you put in (as long as you don't get in their way). Then after three years, if you can't achieve anything, usually all you can do is change jobs.
3. Over-performance and under-performance are diseases and must be treated.
Many companies have many inefficient staff. This is not a bad decision, because you can improve their efficiency through management and other measures. The ones who get fired are usually the guys who both underperformed and made some big mistake. However, you should also be wary of overacting. Because this will lead to some extra unnecessary attention from superiors and colleagues-perhaps waiting to grab your pigtails at any time.
I don’t mean that you can stop working hard. On the contrary, you should work hard and study hard. But from my personal experience, there is absolutely no need to over-perform—perhaps even more unnecessarily than under-performing.
4. Don’t ask for “consent” unless there are unbearable consequences for not doing so.
Want to spend a week delving into your own research? Don’t ask your boss for advice, because they will never “agree.” They may even express displeasure with you, because from their point of view, you are irresponsible and not dedicated to your job. Of course, if what you want to do is indeed risky for the business, or if your boss can agree to it in most cases, then feel free to ask for permission. Otherwise, there is no need to go.
5. Never say sorry for your time.
You can admit that a project did not succeed, of course it is best to use it as a motivation and experience to move forward, but the key is that you should never feel sorry for the failure of your project. This only means that you need more training. Never take the initiative to confess to your boss, "I only work on these business projects in my own time on weekends." If your company doesn't allow you to do other things during regular work hours, then strictly adhere to it. If you don't respect your time, no one will respect it.
6. Understand CS666, even if you forget it and are unwilling to learn it, it will always be with you.
As we age, we tend to focus on transferable and general skills. Yes, CS666 isn't pretty, but it transfers across industries in a way that no other programming language can. If you don't learn, your career will be squeezed out by those who are good at CS666.
7. Don’t make unrealistic attempts to prove your boss wrong.
When young engineers feel that their ideas are better than their boss’s but lack support, they often double their time and energy on it: “I want to prove that the boss is wrong…!”
If you If you are using your own time (and there is no urgent matter at work), your boss will not actually care. On the contrary, your boss will be suspicious and dissatisfied with your working status and attitude, and will subconsciously refuse to give you the opportunity for promotion and salary increase. They will use their own methods to confirm the negative impression you gave them, so even if you succeed in convincing your boss, you have actually failed. If nothing else, your boss has already labeled you as "you have good abilities, but you can't focus on completing the assigned work, and you like to work against me, which is really annoying."
8. Don’t get involved in other people’s fights.
Just because you are young and inexperienced, in most cases, you do not have any real power. If you get involved in fights between other people, or stand up to support the injustice suffered by others, then you are likely to be pushed out to scare the monkeys. We should fight for ourselves, so that even if the outcome is not happy, we can at least win the respect of some people and protect ourselves. Otherwise, others will just think you are a stupid and arrogant fool.
9. Good and bad are not absolute. Look at the problem from another angle.
Don’t label anything as “good” or “bad” when you see it, look at it from another perspective. The boss likes to use roaring body? That means he may not be trusted by his superiors either. Assigned project that’s boring? Maybe your manager is depressed too, so he doesn't have time to find fault with you. And you can use the free time to learn new skills to prepare for your next job. A head-scratching culture? If you can persevere and others can't, then you'll stand out dear. So don’t simply label something as “good” or “bad.” In other words, this seems to be a skill that improves with age.
10. Salaries cannot go downhill unless you start your own business.
If you change careers (from finance to biotechnology research), or go to an area with a lower consumption level, then a 10% decrease is allowed. Otherwise, please answer "No". Let me tell you one thing, most people are not very good at evaluating other people's work. In other words, your current salary level can be used as a starting point for future negotiations. If you decide to lower your status, it's best to have a convincing reason, such as a higher status.
11. Exercise.
Exercise can impact your health, your confidence, your sex life and your career. And exercising can also improve work efficiency. If you find that you have not exercised for a long time, you can start exercising immediately. After all, the body is the capital of revolution.
12. Working long hours: Occasionally is okay, but doing it all the time is harmful.
If your boss Zhou (Zhou Papi) lets you work two jobs and only get one salary just to save money, then leave immediately. Trust me, your boss needs you more than you need this job.
13. Discover the development trends of core technologies through phenomena.
Half of hot words such as NoSQL database and big data technology will become obsolete in 15 years. In contrast, a working knowledge of linear algebra is evergreen. You have to figure out what are the core technical principles that are meaningful and worth learning (such as functional programming), and which are just trends. These "trends" may be very useful to you in the moment (eg, help you get a job), but you shouldn't spend too much time on them. Only a solid foundation can withstand waves of new trends without being beaten to death on the beach by the previous waves.
14. Finally, learn as much as you can. It's hard, but keep at it.
Learning is the foundation. Only by continuous learning and continuous absorption of nutrients can the sapling of our career grow into a towering tree. It's hard because even really smart people have a hard time reading those cutting-edge papers. (To some extent, this is because many papers are not very well written, but that’s another topic.) Trust me, no one is born understanding complex formulas. We are actually very lucky, we stand on the shoulders of one giant after another. So, if you want to be a great programmer, you should study and study harder than you did in school.
Get LAMP Brothers' original PHP video tutorial CD/"Tell Me in Details PHP" essential version for free. For details, please contact the official website customer service:
http://www.lampbrother.net [Brothers IT Education] Learn PHP, Linux, HTML5, UI, Android Waiting for video tutorials (courseware + notes + videos)!
Network disk tutorial download: [url]http://pan.baidu.com/s/1mg8ANMg [/url]
The above introduces 14 tips for junior programmers to avoid mistakes, including all aspects. I hope it will be helpful to friends who are interested in PHP tutorials.