Three amazing technical experts I met during my programming career

I have been programming for more than ten years without realizing it. During the programming process, I met many technical experts with different styles. Today I have time to share with you. Due to time constraints, I cannot list them one by one. Now I will just introduce them in three categories:

Knowledgeable type, with a strong foundation

The company I just worked for was an embedded company. I met this person on the first day of work. He was short and slightly fat. He looked nothing special in the crowd. Everyone seemed to respect him at work. Could he be a technical expert? Later, I gradually learned that this person was the company's architect. Although he was a manager in terms of position, he actually did the work of an architect. Later, I heard from colleagues that the company spent a lot of money to recruit him.

On the surface, I don't see anything amazing about him. What impressed me most was that he watched movies during working hours. Why didn't the boss fire such an employee? And the boss was right beside him and acted recklessly. As time went by, some legendary things slowly spread to my ears. He had 4 people under him. I heard that once, someone under him spent a week writing a bunch of code. Suddenly one day, this guy felt that there was a problem with the design of the code and refactored it all overnight. When the four people came to work, they found that all the code they wrote was gone. Who can understand this feeling? There is nothing you can do about it because he is awesome. He rarely compiles the code directly after writing it, and it basically passes in one go. It is rare to see him come back to modify the errors that cannot be solved by programming.

Another thing is that if any of the four people under him didn't complete the task on time, this guy would finish it that day. It was so happy to work as a technician under him. Once, this guy went home for vacation and wrote an upgrade program. It was said that another team hadn't finished it in a week, but he finished it in one night. All the companies that cooperated with us would secretly call him after cooperation and ask him if he wanted to change jobs.

Later, in order to cash out, the company boss sold the company at a high price. It is said that the main reason was that the company was favored by a listed company. The boss asked this guy to discuss technology, and it is said that the company sold for a lot more money. I haven't seen this guy for many years. It is said that he started his own business. I call him to harass him from time to time. I don't know if he is considered a technical expert.

Technology Paranoia

I also met a friend who was obsessed with the Linux kernel. He almost always left the company last every day, and he would talk about the Linux kernel. One day, I saw he was very happy and asked him what was going on. He said, "I finally figured out how to deal with small memory fragments in the Linux kernel." I asked him to tell me about it, but he said no, it would take two days and two nights to prepare. I said forget it.

He subscribed to an email about Linux kernel modifications and studied it whenever he had time. At least in my career, I have never seen anyone who has a better grasp of operating systems than him. For some large and small projects that the company takes on that require systems, they basically ask him to streamline the systems in order to improve performance, which laid a solid foundation for improving the efficiency of the company's products.

When Android first became popular, I found a motherboard and slowly ported the Android system to it and made it run smoothly. You have to know that there was very little information about Android at the time, unlike now when you can just search for information about Android, both at the basic level and at the application level.

He is considered a pioneer in Android low-level porting. Every time we chat at lunch, he tells me how great the Linux kernel designers are, how ingenious the design is, and how it is a blessing to be able to understand it.

The author thinks that he is quite dedicated to technology, but compared with this guy, he is no match.

A real architect

This is a standard architect who has been in the industry for more than 20 years. He has worked in various fields for many years, from router principles to virus security experts to the Internet field. He has mastered programming languages ​​from low-level assembly to high-level Java. He likes to fiddle with various algorithms and set various obstacles during interviews. He built the first dual-core browser in China. I won't list all his achievements here.

Every time a version is released, he can solve all kinds of difficult and complicated problems. His technical ability is really amazing. Whenever he encounters a problem, he will analyze it in the assembly language, and he will definitely find the ultimate cause of the problem. He is also easy-going. After dinner, he always plays table football with a bunch of brothers for half an hour. He has a young heart, and there are a lot of wine bottles on the table. When he encounters a difficult problem, he will drink a few sips.

Once, this guy and I worked together to decompile the Penguin browser kernel. Yiren was responsible for the underlying graphics connection, and one of us was responsible for the browser kernel business logic connection. It took us a month to get it done. However, the company later adjusted its strategy and prepared to move towards the light application route, but it was not used. In fact, the underlying channels were opened. The feeling of working with experts is completely different, and the efficiency is also different. To describe this feeling, I guess you can only experience it yourself.

I always think of the days in Beijing and miss the brothers who fought on the front line with me.

The so-called masters, first of all, are diligent. Others are smarter than you and work harder than you. This is the reason for excellence.