No matter who they are, when they first enter a certain field, no amount of ambition can beat the confusion in front of them: they don't know what to do, they don't know what to do. Below is what I've learned as a software developer, and I hope it helps.
1. Don't be afraid to learn on the job.
As long as you have a computer, you can read newspapers and most books with an e-reader. If you just do your job and the assigned tasks, you won't learn a lot. It is also impossible to improve yourself if you blindly demand more work. Slow down and pick up some basics first.
2. Be brave in your career and be responsible for yourself.
Only about 1 in 10 people get special care from a mentor, and if you are in 9 out of 10, that means no one is there to look after you most of the time. So you have to take care of yourself. If you can, try to avoid jobs that don't improve yourself or teach you anything: because it won't add value to your career, and other people 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 don't get any grades, then usually all you can do is change jobs.
3. Excessive performance and poor performance are both diseases and must be cured.
Many businesses have many inefficient workers. 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 mistakes. However, you also need to be careful not to overdo it. Because it can lead to some extra unwanted attention from superiors and co-workers -- maybe 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—probably worse 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, because they can never "agree." They may even express dislike for you, because from their point of view, you are showing no sense of responsibility and no love for your work. Of course, if what you want to do is really risky to the business, or in most cases, the boss can agree to, then boldly ask for instructions. Otherwise, there is no need to go.
5. Never say sorry for your time.
You can admit that a project didn't work out, and of course it's best to use it as a motivation and experience to move forward, but the point is that you should never feel sorry for your project. It just means you need more practice. And don't take the initiative to confess to the boss, "I only work on these business projects on my own time on weekends." If your company doesn't allow other things to be done during normal business hours, follow them strictly. If you don't respect your time, no one will respect it.
6. Understand CS666, even if you forget it and don't want to learn it, it will always be with you.
As we age, we tend to focus on transferable and general-purpose skills. Yes, CS666 isn't pretty, but it's transferable across the industry in a way no other programming language can. If you don't, your career will be crowded out by people who are good at CS666.
7. Don't be unrealistically trying to prove your boss wrong.
When young engineers feel their ideas are better than their boss's, but lack support, they tend to double down on it: "I'm going to prove the boss wrong...!"
If you're using your own time (and there's no urgency at work), your boss, in fact, doesn't really care. On the contrary, your boss will be suspicious and dissatisfied with your work status and work attitude, and will subconsciously refuse to give you the opportunity for promotion and salary increase. They will have their own way of substantiating the negative impression you gave them, so even if you succeed in convincing your boss, you have failed. If nothing else, your boss has already labeled you "good ability, but can't focus on completing the assigned work, and likes to work against me, which is really annoying."
8. Don't get involved in other people's fights.
As you are young and inexperienced, in most cases, you do not have any real power. If you get involved in other people's fights, or stand up for other people's injustices, you're likely to be pushed out to "kill the chickens and show the monkeys". We should fight for ourselves so that even if it doesn't end well, at least we can win the respect of some people and protect ourselves. Otherwise, others will only see you as a stupid and arrogant idiot.
9. Good and bad are not absolute. Look at the problem from a different angle.
Don't see anything and call it "good" or "bad," look at it differently. The boss loves to use the roaring body? Then it means that he may not be trusted by his superiors either. Bored of assigned projects? Maybe your manager is also depressed, so there is no time to find fault with you. And you can free up time to learn new skills to prepare for your next job. Awesome culture? If you can persevere and others can't, then you will stand out as a pro. So, don't simply label a thing as "good" or "bad." In other words, it seems to be a skill that improves with age.
10. Salary can't go downhill unless you start your own business.
If you change careers (from finance to biotechnology research), or go to an area with lower consumption levels, a 10% drop is allowed, otherwise, please answer "No". Let me tell you something, most people aren't 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 yourself, it's best to have a convincing reason, say, higher status.
11. Exercise.
Exercise can affect your health, your confidence, your sex life, and your career. And exercising can also improve work efficiency. If you find that you haven't exercised for a long time, you can start exercising immediately. In other words, the body is the capital of the revolution.
12. Working long hours: Occasionally okay, always doing the harm.
If your boss Zhou (Zhou Papi) makes you work two jobs by yourself just to save money and only get one salary, then leave immediately. Trust me, this boss of yours needs you more than you need the job.
13. Discover the development trend of core technologies through phenomena.
Half of the buzzwords like NoSQL databases and big data technologies will be a thing of the past 15 years from now. In contrast, working knowledge of linear algebra is evergreen. You have to figure out what makes sense, core technical principles worth learning (like functional programming), and what is just a fad. These "trends" may be very useful to you in the moment (for example, to help you get a job), but you shouldn't spend too much time on them. Only a solid foundation can prevent wave after wave of new trends and not be slapped 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 constantly learning and absorbing nutrients can this small sapling in our career grow into a towering tree. It's hard because even really smart people have a hard time reading those cutting-edge papers. (In part, this is because many papers are not very well written, but that's another topic.) Trust me, no one is born to understand complex formulas. We are actually very lucky, we are standing on the shoulders of giants. So, if you want to be a great programmer, you should study and study harder than you did in school.
Those with 1-5 work experience, who do not know where to start in the face of the current popular technology, and who need to break through the technical bottleneck can join the group. After staying in the company for a long time, I lived very comfortably, but the interview hit a wall when I changed jobs. Those who need to study in a short period of time and change jobs to get high salaries can join the group. If you have no work experience, but have a solid foundation, you can join the group if you are proficient in the working mechanism of java, common design ideas, and common java development frameworks. java architecture group: 697579751 to communicate together