The body of the
1, more communication, first understand the requirements, then start to write code.
Murphy’s Law really applies to requirements communication, requirements you don’t understand are often made wrong! It’s a waste of time and energy.
2. Think before you write code, and write code later
Get the demand, according to the function to achieve, the first analysis to achieve the idea. When analyzing the implementation idea, you can write it down in Chinese while analyzing it. Or you can write comments directly in the tool, then the next work is a translation process, easy to implement. You can avoid a lot of detours.
3. Business over technology
In absolute terms, technology is more important than the business, but from an enterprise perspective, technology serves the business. So business is far more important than technology.
4. Be sure to annotate
Many people do not want to write comments. In fact, the main purpose of writing comments is to improve the readability of the program. Good programs should be easy to read first, and efficiency second. Note less, let alone others see, a long time they can not understand their own code!
5. Change requirements frequently
It is normal to change requirements from time to time, because it is perfectly normal to change requirements as they constantly adjust to business needs. If you change requirements frequently. Then you might want to complain! But to learn to understand, after all, take wages to work is also very normal things!
Requirements document must be written!
If the requirement document is not written, the requirement will only be known by someone in the company, and other people need to ask him if they want to participate in the work. If most of the requirements are still communicated orally, and no documentation is written, it will be easy to quarrel later! So when the requirements document is written, anyone can read it, no one can ask anyone, no one can influence anyone. The requirements document is part of the process standardization, which is a sign of professionalism.
Think there is something wrong must be changed in time
Where you think there might be bugs, there will be bugs!
8. Use technology you know you can use
You may have recently learned a new technology online, but if you are not 100% sure, it is best not to use it. While introducing new technology is a good thing, it is also part of an organization’s quest for professional advancement. But think back to any new technology you’ve used in your work, and have you ever been cheated? I guess everyone has been “pit”!
9. Try to solve problems on your own
The boss of any enterprise hopes that his employees can solve problems independently, rather than asking the boss or colleagues for solutions when they encounter problems. If you really encounter problems that you can’t solve, you should ask your leaders and colleagues for help in time to avoid bigger problems.
10. Test yourself a few times
Write code that can be used without testing, unless you are a god! Otherwise there are generally residual bugs in it! So they still want to test after throwing to the testers to test, to ensure the quality! Don’t waste other people’s time, either.
About me
More Android Advanced Interview collections are available on Github
You can click on it if you need itAbout meContact me to obtain
I hope to communicate with you and make progress together
At present, I am a programmer. I not only share the knowledge related to Android development, but also share the growth history of technical people, including personal summary, workplace experience, interview experience, etc., hoping to make you take a little detours.