Five courses required by web developers

Document directory

• Introduction

Introduction five courses that web developers should take:

1. You are not always the smartest person
2. Experience is certainly useful.
3. No silver bullet (that is, no technology can solve all problems)
4. A new good thing is not always a good thing (here something refers to technology or Application)
5. Not every battle is worth fighting (do not always think your ideas are correct)

More and more web developers usually ask the same question. For example, which development language is the most important? What is the salary of junior developers? Is the free training provided by the company useful? How to evaluate a new project? Although these questions are important, developers often disagree with others' answers. Generally, they do not know how to find the answer. The following five suggestions may be useful.

You are never the smartest person

Before the Internet bubble came, I worked with a colleague to scan and encode the speech recognition system. Soon we found that using a computer or pda can easily access the Internet without a keyboard. Every time I questioned some of his ideas, I was opposed by him. He thought he could never make a mistake. He once attended technical seminars! In the next few months, many of his designs failed to be implemented.

If one day you find that you are in a similar situation with my colleague, you may realize that you are not always correct. You are not the smartest person in the office, so taking the initiative to accept others' suggestions may show your great wisdom.

Experience is really important

Writers never want to admit this fact, so do our developers. Even so, I found that those who have experience with successful projects will be more likely to succeed in the following similar projects. When there are clear requirements for development, programmers are usually very confident and capable of solving all the problems, regardless of whether the methods used are the best or even reliable.

In fact, experience is always very useful. My advice is to believe in others' experiences and learn from them, rather than making yourself jealous of your infinite expansion. When you make a mistake, you can ask for more reasons, give feedback to others, and respect others' opinions.

No "omnipotent" technology

It is undeniable that any development language, framework, or operating system today has its loyal followers. Of course, there is nothing wrong with their persistent pursuit, but if you think of either of them (technology, framework, or design model) it can solve any problems encountered in all projects. I am opposed to asking the Web developers to master some mainstream development languages. I think it is enough to have a basic understanding of these languages and technologies, because there has never been any omnipotent technology.

Good developers may become advocates of new technologies, but they will not become enthusiastic advocates. Unless he works in a software service company responsible for technology promotion, he must be open-minded and willing to accept changes.

New technologies are not necessarily the best

As a developer, it is not good to focus on a technology for a long time, but it is even worse to advocate the use of the latest and most fashionable technology. Although the new technology is attractive, it is not always the most appropriate. Some technologies that have been successfully practiced can often reduce project errors, shorten the construction period, and satisfy customers. In addition, websites developed in this way are often more accepted.

Of course, I do not advocate abandoning new technologies. We should be sensitive to new web technologies at all times. Once the time is ripe, the conditions allow us to quickly switch to the development practices of new technologies. We can often learn and try to use new technologies to update our existing systems.

Not every battle is worth fighting

As a web developer, my experience proves that many of the principles of websites must be adhered to while maintaining personalization. But others do not think so. In the past, I tried to argue for this problem from beginning to end, because I think it is correct from any angle. Now, I think most of the time you just need to clearly express your thoughts.

Although your ideas may not be accepted, you should learn to tolerate mistakes made by others, and then ask the management to coordinate them. In the long run, your colleagues will find your tolerance and respect you and appreciate you.

From: http://www.yeeyan.com/articles/view/9884/13402