What is the programmer's pursuit?

1. Make software products ------ 2. Excellent colleagues ------ 3. Challenges ------ 4.
Cool technology ------ 5. User ------ 6. Good salary ------ 7. Good tools ------ 8.
Work 40 hours a week ------ 9. Least bureaucracy ------ 11. close to home ------ 10.
Work at home

......

1. Make software products.

I want to writeProgramBecome the company's main business. This eliminates IT maintenance because it only indirectly supports real services (no matter what it is ). I also want to participate in the core part of the system, the more important the better. If something goes wrong, it should immediately become an emergency. Finally, I don't want to be involved in configuring, applying, or integrating software from other companies-I want to implement key functions on my own.

2. Excellent colleagues.

Working with a smart programmer who is passionate about software development is inspiring. Again and again, I talked with my colleagues about some issues or how design came up with better ideas than any of us. This cooperation method is not only betterCodeThe process itself is very enjoyable.

How do you know if someone is a good programmer? A particularly good feature is to see if they continue to learn and improve their skills, such as reading books, reading blogs, attending training courses, and attending technical conferences. This is not a necessary condition. I used to work with many great developers who did not do this. Finally, excellent developers will attract other excellent developers for the above reasons. If an enterprise has many excellent developers, it is easier to recruit more outstanding developers.

3. Challenges and difficulties.

The programmer solves the problem through code. A developed product requires at least some smart ideas, such as low latency, a large number of concurrent requests, or limited hardware resources. However, many software products are made up of common code, and there is nothing difficult to do. Therefore, you cannot just look forward to "difficult problems" and avoid all other requirements. Moreover, organizing code that looks boring makes it easy to understand and maintain, which is a huge challenge.

4. Cool technology.

This is mainly about the use of interestingProgramming Language(Such as clojure, Erlang, or go), but also includes frameworks and applications (such as hadoop Or Cassandra ). This may be a problem for some companies. If their applications are written in a certain language (such as C ++), they won't be changed. So if you want to use a new language, you may need to change your job. For example, if you want to use Erlang in Stockholm, you can submit a resume for klarna or campanja.

5. User.

One of the fun of coding is to make something useful to others. It is boring to do things without being used. Users (the more the better) need to pay attention to your development efforts and give valuable feedback. The only exception may be when you start a business, but in the future, attract as many users as possible as the highest priority.

6. Good salary.

Companies with a large number of outstanding developers know the value of excellent talents. Because there is a huge difference between excellent and general programmers, it is economically reasonable to lean the reward to excellent developers-in fact, the difference in production efficiency is much greater than the difference in compensation. Conversely, companies that are unwilling to give programmers a higher salary often regard programmers as "Resources" that can be changed at will ". You may not be able to see the performance of these companies in other aspects, not just low salaries.

7. Good tools.

The importance of this factor is almost self-evident. A fast computer and several monitors can speed up the development process-who will oppose this? (Well, bald bosses who simply look at the cost without looking at the efficiency may disagree)

8. work 40 hours a week.

If you always need to work overtime to complete the task, it must be a problem in your work unit. In addition, long work is not equal to efficiency.

9. Least bureaucracy.

For the development process, there may be more or less shadows of agile development methods. It seems that everyone has adopted this idea. According to my experience, the daily management tasks in large companies are basically invisible.

10. Work at home.

Sometimes it is effective to work at home, but I do not often do this. I like to communicate with colleagues in the office. I used to work in a remote office through video conferencing, chat tools, and e-mails, but the efficiency is not as high as that of on-site cooperation.

11. close to home. 

Obviously this is not easy to force, but it doesn't take a few hours a day to get on the road.

1. Make software products ------ 2. Excellent colleagues ------ 3. Challenges ------ 4.
Cool technology ------ 5. User ------ 6. Good salary ------ 7. Good tools ------ 8.
Work 40 hours a week ------ 9. Least bureaucracy ------ 11. close to home ------ 10.
Work at home ......

which one do you think is more important? (-d) please comment