Time flies, does not it?
My programming journey began in 2014, when I was just a web production intern. To be honest, I do not know what they are doing. Even now, the situation has not changed. However, in this process, I really learned a lot.
The question is: During programming, what language is the most important?
It's English? Spanish? Chinese? Polish? Or any other language used to communicate with other people at work?
Understand what you are doing and why
As you have a sense of purpose, it will feel better, which is the same at work.
As a software developer, your goal should not just put the issue in JIRA into JavaScript, or Trello in the project becomes C #.
Your goal should be to use the code to solve the problem.
If you know a lot about the system being built or maintained, it can be put aside to make technical decisions. This function is necessary? It solves the problem? It may be other ways to solve this problem? Really we need to solve this problem?
These are business issues, if you want to do a good job, not only to understand the business, but also actively participate. Even if you are not in the company C-level people, do not affect you, at least, you have to understand what you are doing.
If the code review to make you feel stressed, it is certainly wrong turn on the way
, although we do not need to think so, but to put out its own code written by other people "crowd Review", the experience with writing code really is a little bit different No wonder people feel anxious.
Canton someone because they do not tolerate certain people quibble, choose to submit code review on this person is not the company's time. Imagine, if you are a novice under PR bombing gives 50 less friendly comments, you actually do not just prove his superiority as a senior programmer, but also to prove you're not a "good man."
Then, open the right way should be like?
You can find a private person, have a conversation with him, asked him why he did write the code.
In fact, most people do not want to write code smell, for some reason unknown stink if you see the code, which may have. Of course, there may be because their programming skills are not good enough, this time you have to assume the role of "mentor", and to provide them with some guidance.
Take precautions
Murphy's Law: things will go wrong will go wrong.
It's like a truth, in the design of the system there are always some things will go wrong.
When developing a login form, you have to assume there will be some detractors who copy the contents of the entire book to the password input box.
When developing a WYSIWYG window visible, you have to assume that someone will try to sabotage, and they can usually get it.
If the system uses a database, it will hang at some point. If you do not try to use the backup to restore the database, then they are not really backed up.
If you are doing the presentation to someone else, make sure that this demonstration can be normal in any case, even if turned it upside down, or even throw it under the water.
Do not be afraid to let others see their own ignorance
As a senior programmer advantage is that when people ask questions I do not know, I can tell them lightly:
The thing I do not know, because in the past have not encountered before, but I can look at, and then tell you.
When I was a junior programmer, I was always afraid someone will see my ignorance. After several years of tough training, I came to understand, if you encounter something they do not understand, explain to the opportunity to learn. Lifelong learning is definitely not just a "mantra", it should be put into practice.
share it
And so they get to know you do not understand something, and it is imperative that they share it. Write a blog, a record instructional videos, or share in the company put forward a speech ...... you do not think you just learned something others know everything, even a very senior people, they have learned from junior staff things, and vice versa.
Sharing process is actually a test whether you really understand what you are learning process. There is a saying:
When you teach a person when in fact there are two people at the school.
To help make learning easy, efficient and free for everyone to share a large number of resources to help you become the front-end engineers, and even the way through the clutter full stack engineers. We are here to recommend a front-end full-stack learning buckle qun: 784783012 unpaid share some senior front-end development engineers recorded video (from zero base to project real case), front-end engineers the necessary knowledge. Also receive free learning resources
when the real start learning inevitably do not know where to start, leading to inefficiencies affect confidence to continue learning.
But the most important thing is I do not know what needs to master key technologies, frequently stepped pit learning, end up wasting a lot of time, it is effective or necessary resources.