Java technology stack
www.javastack.cn
Open the website to see more quality articles
1. Be cautious about saying Yes
Promising programmers will not readily agree without understanding the development requirements, task workload, and team expectations. Especially for newcomers, they are more eager to express themselves. They are not refusing the work arrangements of colleagues or bosses. They are commendable and undesirable.
There are too many commitments, and you will not be able to complete on time. Even if you complete on time, you may not meet the expectations of others. In the long run, others will be more and more disappointed with you.
2. Dare to say No
It looks the same as the first one, but it's different in detail. The second one is much harder to implement than the first one. When encountering an obviously unreasonable request, you can consider refusal, provided that a comprehensive and sufficient reason is prepared.
Do n’t say No often, but once you say it, you have to hit the point. Promising programmers will not be bogged down in work, knowing their positioning and team expectations, clearly distinguishing which are unreasonable requirements and which are reasonable requirements, and then communicating clearly unreasonable requirements with leaders to obtain support.
3. Build your own knowledge system
In the era of information explosion, there is a lot of fragmented knowledge, and the time for systematic learning is getting less and less. If you do not have your own knowledge system, it is easy to be drowned in the ocean of knowledge, and it is difficult to remember.
A 100-point programmer recommended approach to build a knowledge framework through Wiki or other knowledge management tools. Large categories can include soft skills, architecture, language, front-end, back-end, etc. Small categories can be more refined.
4. Cultivate the big picture
The dilemma that programmers are more likely to fall into is to focus on their own one-third of an acre, not caring about the team's progress and performance, nor the overall architecture of the software and other modules. There is no benefit in this state for a long time, especially in large companies, it gradually grows into a screw.
100-point programmers will look at what they are doing in their spare time, look at the team's overall plan, and look at the architecture and documentation of the software system. A better understanding of your job and knowing why this product should be designed this way and why leaders should plan this way. This overall view is very beneficial to your career.
5. Code specification
Programmers need to develop good code specifications in the novice period. The most direct way is to follow the company's existing code specifications (if there are no similar provisions, it is also drunk), from simple variable naming to module division, some rules can be imported into the coding tool, and more parts need to be experienced and comply with.
Regarding this knowledge, the most authoritative book is Code Encyclopedia. Don't get me wrong. The title of the book is a beautiful mistake. It is not a collection of codes. For novices, it is very important to develop a unified coding style, which is a basic step. In addition, pay attention to the WeChat public account: Java technology stack, reply in the background: manual , you can get Alibaba's code development manual .
6. Code review
This is because it is very important for programmers. Many fast-growing companies do not have this step, and it is recommended that you stick to it. Let others review their code, you can get more feedback, but also a good opportunity to communicate with colleagues; review others' code, you can learn from other people's experience and ideas.
In general, code review is more rewarding than writing code yourself, and it is more valuable for novices. As long as you want to do it, regardless of whether the form is formal or not, it can be carried out. It is best to form a team habit. Code Review ’s two-year experience sharing from scratch is recommended.
7. Focus on only one type of language in a time period
If you are designing or developing a website, you will need to be familiar with many different languages at the same time. You may want to learn all these languages at the same time, especially considering how they are related to each other.
I think, to some extent, this is inevitable. But if you really want to improve quickly, I suggest that you focus on the expertise of a specific field. Do you want to make better use of CSS? Put your focus on this. Try to use a single HTML document using CSS only to achieve different layouts.
CSS Zen Garden is a great example of using the same layout to implement different page styles. You can also find the list of elements and concentrate on it. For example, you are familiar with CSS2, but if you want to improve your understanding of CSS3, you can learn CSS3 properties and implement them one by one. You can read the current CSS3 specification and learn what each module can (or cannot) do in the browser through the learning of each module.
8. Write logic through comments
When it comes to coding, I have adhered to many principles and ideas. One of them is that 95% of the code is logic. The other is that from human language to programming language, the logic has not changed. This means that if you can write it in the code, you can write it in English or other languages.
9. Good time management
Being late is a headache for any company. As a programmer, sometimes I have to stay up late in order to complete a task, resulting in being late for work the next day.
But we overlooked this, and our working hours are crucial, because during this time we have to synchronize with our customers and also work with other team members.
10. In-depth understanding of customer needs
It is not enough to understand the apparent meaning of a single user. A great programmer should have the ability to understand and decompose tedious requirements into technical tasks or sub-tasks of the project, and the final results should accurately meet the needs of customers.
11. Strangle your brain or "NO"
If we can't find a solution if we scratch our heads, what should we do? A great programmer should be resourceful and able to respond flexibly to difficult situations. They will ask colleagues or consult with team leaders; search on the Internet, and then patiently experiment over and over again. I believe that the mountains and rivers have no doubts, and Liu Anhuaming is in another village. The word surrender has never appeared in their dictionary.
12. Prepare a full set of algorithms before programming
Dear ~ Remember the flow chart our teacher forced us to draw? Remember the cases and pseudocode? They are all very important means of software development.
If a great programmer has prepared algorithms in advance, would he just like to write code like a fool? Therefore, before starting construction, it is necessary to do a full set of algorithms.
13. Understand and help define acceptance criteria
It is up to the product owner to decide whether a high-level test script is required. However, as a great programmer, you must be able to write technical test scripts, and you must also realize the consequences if you skip this step.
14. Take a little initiative
A good programmer does not need others to tell him what to do. His initiative is stronger than others. He can consciously pay attention to the process, improve the flexibility of the application and quickly solve the bugs in the development process.
Author: ΣGemini, from: Bole online
END
Learning materials:
Share a copy of the latest Java architect learning materials
Recent articles:
1. Java 10 big pack B writing method, you can brag!
2. Java 14 pattern matching, very new feature!
3. Heavy: Java 14 is officially released!
4. Are you still using Date? Quickly use LocalDateTime!
5. A bloody case caused by the leak of the Druid connection pool!
6. 8 data structures that every programmer must master!
7. The 8 ways of writing the singleton mode are very complete!
8. How to use chase MM to understand 23 design patterns?
9. When I go, my colleague actually stores the password in plain text! ! !
10. Why do big companies have to use microservices?
There are too many dry goods in the public account. Scan the code to pay attention to the public account of the Java technology stack . Read more.
Click " Read Original " to take you to fly ~
