The first lesson after becoming a drive engineer

The dream journey of an engineer who pursues embedded technology:

In the first year, the dream was to be a microcontroller development engineer

In the third year, the dream was to become an embedded engineer Linux application engineer

When I was in my fifth year, my dream was to become an embedded Linux driver engineer

After five years, I became a driver, but I lost the drive to pursue technology.

When I first graduated from college, I was looking for a job. I always felt that I was an excellent graduate and would definitely be able to find a good job.

Others can do microcontroller development while sleeping and failing classes every day. I always feel that I can at least do Linux applications and even drivers.

So my resume was only submitted to big companies, and the salary was sky-high.

I firmly believe in my heart: As long as gold shines everywhere, it will be seen by others one day.

But the reality is that if you can’t do it, excellent graduates are useless.

So I gradually lowered my expectations, and it would be fine if I could get a job in microcontroller development.

I thought that there was only one chance to stand out between myself and my ideal job, but later I realized that work would only let people see the less than ideal version of myself.

This is the first lesson society teaches itself.

#After I have some work experience, I want to move towards Linux application development. After all, microcontroller development can be done at a glance.

After actually developing Linux applications, I found that it was more about business needs.

I originally thought that when moving from microcontrollers to Linux applications, I could learn a little more about the technology stack.

But the reality is that in order to meet needs and user experience, various interfaces and packages have been changed. Have you learned any meaningful technology? It seems that you have not. At most, it is called "proficient in C language".

Gradually, I lost my expectations and began to compromise. Just write business logic, just business logic. After all, I still have to eat.

The first lesson after developing Linux applications is to compromise with business code.

When I really achieved the low-level driver development that I dreamed of, I realized that the functions I had done before were too impetuous.

In the past, when working on the application layer, a complete product could be seen in a project cycle of maybe two or three months.

After doing low-level development, I may only have completed one driver in a month. It is still a long way from the final product, and there is no end in sight.

After a lot of low-level development, I found that basically nothing could be done in a month or two, and I could only complete a few drivers. This is very different from application development that takes several months to take shape.

But it has an advantage. Although I have only worked on one or two drivers in a month or two, my understanding of this technology has been very profound. Others can reach your level in a short time. .

I realized how important underlying development and precipitation technology are.

This is the first lesson after becoming a drive engineer: learn to settle.

The above is the detailed content of The first lesson after becoming a drive engineer. For more information, please follow other related articles on the PHP Chinese website!