What Electronics Engineers have done over the past year

Reposted from the network. The specific source is unknown.

 

What Electronics Engineers have done over the past year

I am an electronic product technology R & D engineer. I joined the company in February and have been in the company for more than a year. Recently, my mood has experienced great fluctuations. I am a little confused when I make choices for my future career development. I have been confused about subjective and objective factors. Now I will list my work experiences (not experience) over the past year, so that I can sum up the past and have a better understanding of myself.

Because I used to practice in this company, I volunteered to stay when I was about to graduate. After joining the company, you will be responsible for the development of several products in a project. In the early stage, I was not familiar with this project. I checked out what work was required to develop the entire system. Later I found that there were too many tasks to be developed. Fortunately, I got down step by step. Now the products are new and are being pushed to the market, so I am not happy with it. The most important thing is that I am not at ease with the products, and I am worried that many problems will occur during the application, it brings great inconvenience to the customer (I especially care about whether the customer is satisfied ).

The manager of the department told me that the first few years of work have a great impact on your future career development, especially in the first one or two years, it will gradually form a kind of work attitude, work characteristics, behavior habits, etc. Once these habits are formed, it will be difficult to change, so do not form bad work habits and attitudes. Fortunately, I have been stuck for a year, but recently I 've been a little slack. Maybe there are fewer things and people have become a little lazy.

In more than a year, I have learned a lot from students to junior Engineers (self-styled. My project is also an embedded application system, involving hardware and software design, but not operating systems. At the beginning, the Department Manager participated in the project with me for a while. Later, I was responsible for all the projects, including system function design, hardware design, board design, software programming (C language), and component procurement, functional Module debugging, system debugging, to discuss with structural engineers about structural design, external technical cooperation, processing, visiting customers, understanding specific market requirements, etc, I have a profound understanding that in addition to technical capabilities, we need patience and meticulous design, and we need to be an exquisite engineer. In a word, the design and development products should satisfy you very much. If you are not satisfied with yourself, do not count on the customer's satisfaction, of course, the expectation is higher (The above statement is not applicable to those who have low requirements on themselves ).

Let's take a look at my personal feelings based on the product development experience. I hope I can get some criticism and advice.
1. before developing a product, you must fully understand the market requirements and determine the specific customer base. Do not scatter the network too large or take into account the needs of too many customers, otherwise, it will bring a lot of work and more considerations to the subsequent development work (especially when the number of R & D engineers is insufficient ). First, make and try products suitable for one or two applications, and take advantage of the market, then, the performance and functions of the product can be improved and extended based on the usage and other requirements of the customer.

2. in the end, products must be applied, especially industrial outdoor products. These factors must be fully considered in the initial design (including internal electronic components and external structures) due to the harsh application environment, ensure the stability and reliability of future products. You cannot be lucky enough to solve the problem only when the problem occurs. In all aspects of the design, the module can be tested for the moment first, and the problem can be found and solved earlier. Do not wait until the entire system is assembled before testing, otherwise, it is difficult to locate possible problems. This is very important for engineers who are just working on products.

3. Do not escape from problems. If the problem is not solved, it will always exist, and it will be exposed sooner or later. For responsible engineers, this is a heart disease, and it may be upset and heartless, so for the sake of calm, it is better to solve the problem early. When my personal abilities are limited, I can talk about the problem and ask my colleagues around me to help me find a solution. Besides encountering especially difficult technical difficulties, I can solve the problem very quickly, you can also learn other people's ways of thinking.

4. After a certain stage of product design, some people (leaders or customers) may ask for or suggest adding some more features, which may disrupt the product design ideas and processes. At this time, we should carefully consider their requirements. If they are not necessary functions, they should not be added for the time being, but be sure to write them down and take them into consideration when they will be improved in the future.

5. The product design process is also a process of self-improvement. For new users, they should not only think about products, but also think about and summarize the problems and knowledge they encounter, record the problems, solutions, and new knowledge you encounter at any time, and enrich your technical skills and experience. Everyone's life is actually "writing" his/her own history books (whether expressed in words or in their hearts). Some people can publish their history books if they are well written and well written. This is also a kind of capital. There will be more "writing" and more confidence and courage in the future, whether it is job hunting or promotion.

6. work attitude and behavior habits are crucial. Good habits allow you to quickly deal with problems and keep everything involved in product development in your work under control. Bad habits allow you to spend a lot of time doing unnecessary things. This attitude is especially obvious when a team is working with others to complete the task. As long as the ability and time are sufficient, you must do it well early, you cannot let others stare at yourself several times. No one wants to be chased by others to get things behind their own ass, so it is better to finish things earlier to make it easier, because things are always done, late work also affects others' opinions on themselves. It seems that it is not easy to be an engineer.

7. Do what you should do. For things that do not have any meaning, you would rather sit there and enjoy yourself and do not do it. You need to constantly charge yourself at work in your spare time. Because what you do at work may not necessarily improve your skills (it may be done repeatedly, just like a pipeline ), but remember to learn more when you are idle and awake. Remember: you may not be learning at work, but you must be working at work!

8. Be an exquisite Engineer (Seiko ). I want to work in earnest and meticulous ways that any leader will like, and my colleagues will not reject. In the future, careless engineers will cultivate their own exquisite connotation even if they become a powerful tool. Otherwise, they may be planted in their carelessness. The refinement is not formed overnight, so it is time to practice it.

9. the company's interpersonal relationships are simple and good. Don't join forces, but be sure to have people with whom you can say that you are confused at work. In this way, when you are confused about your life and work, someone can give you an idea. Sometimes people really need to be listened. It is inevitable that you may encounter a bad person at work. Do not be deeply trapped in your own emotional traps. Do not forget these feelings at work, enjoy your own life.

Because the development work in the early stage of the product is basically over, and some functions will be modified or added in the future based on the on-site application conditions or market requirements, the development work will not be very large, and no new development tasks will be received for the moment. Nowadays, I am a little idle, and I am also a little confused about the environment (soft environment. I would like to study in depth at a certain technical level in a favorite industry to be a technical expert, because in my opinion, only technical personnel can respect you and admire you, in order to have a higher chance of promotion, of course, other aspects of knowledge should also be more hunting. I have been reading the free magazine "World of Electronic Products" for nearly half a year. I have extended my knowledge and benefited a lot. I like it ~!

If you want to do it, you have to think about it. Otherwise, you may have done half of it and transferred it to another place. If you haven't thought about it before, you can try it more. After four or five years of work, you have to grow steadily in a certain industry.