Engineer, if you don't develop from the perspective of engineering or product, how can you be worthy of the word "engineering"...

懒猫爱飞

Engineer, if you don't develop from the perspective of engineering or product, how can you be worthy of the word "engineering"... [Copy link]

 

The older you get, the more things you have to do and the more you think. People say that you are aggressive when you are young because you are young and fearless. You don’t think too much. Think about it. Back then, I once climbed over the wall to the reservoir to swim in the middle of the night without telling my teacher. I am very lucky to be alive today. Later I heard that there were many accidents in that place... Okay, let’s get back to the topic. It’s good for young people to be quick and aggressive. However, as a developer, you still have to consider what you should consider. (I) Cooperating with a developer to develop a product related to a mobile power bank. I wrote the Bluetooth part, and the power processing was handled by another IC. BLE communicated with the MCU of the power bank through the serial port. We all know that mobile power banks, handheld mobile power bank products, must have low power consumption. 1uA is 1uA. This guy wrote the program very quickly and finished it in two days. When I got his module, I tested and found that when his MCU was awakened, it kept sending commands through the serial port. There were a total of 5 commands, which were polled and sent all the time. So, I gave him some suggestions: 1) When the data has not changed, you don’t need to send it, such as battery power, battery status, etc. 2) When the battery is discharging or idle, there may be an error between the actual power value and the sampled battery voltage. However, from a practical point of view, the battery power will become lower and lower, so you cannot send 50% of the power and then send 55% of the power. A simple data processing is required here, that is, recording the lowest value. 3) When the battery power is represented by voltage, there must be at least three power meters, one battery voltage meter when unloaded, two when discharging, and three when charging.... As a result, this guy was not convinced and complained in the project group. He didn’t mention it when discussing the plan, and now he wants to modify it. . . . Well, as an experienced person, I may be reminding you too late. But if you don’t test your product, how can you know the quality of what you develop? Well, accept the comments or not, modify the program or not, as long as you like it (Part 2) There was once an electronic control board. The hardware engineer quickly drew the board and sent it to me to debug the code first. I looked at the PCB and made some small suggestions: 1) The wiring terminals are too close to each other, which is not convenient for plugging in the wires and production line plug-ins. 2) There are no test points. 3) The contact area between the power pad and the surrounding copper foil is too large, which makes it difficult to solder. . . The hardware engineer was also quite dissatisfied with the first point. The reason for rebuttal was that he had always drawn it this way before and there had been no problems. The second point was that the company did not have a mandatory requirement to add test points. The third point was that it had been patched and reflowed. . . Well, after listening to their reasons, I dare not show off my skills in front of others. After all, I am not a professional hardware expert.---------------------------------------------------------------------------------------------------- Before I know it, it is already 23:09. I'll just write this little bit. I'll organize it when I have time. Finally, I just want to say that as an engineer, you should look at things from a global perspective and don't work in isolation. After all, you are designing a product. After the front-end design is completed, there are still a lot of things to do. If one link is not handled well, many people may have to do more things later. As an engineer, you should experience the things you designed yourself and feel it as a user. Engineers, who are also product managers, can go to bed.

freebsder

Yes, that's what I said

qwqwqw2088

Communication within the R&D team is very important. The corporate culture and atmosphere of each company are different, which is directly related to the head of the R&D department. In short, the sense of responsibility is not enough.

btty038

I have tried the experience at the beginning of the article 3 times, and I went swimming secretly every time. It is not easy to live to this day after 3 times. I was a bit suicidal when I was young

懒猫爱飞

qwqwqw2088 Published on 2019-2-28 08:34 Communication within the R&D team is very important. The corporate culture and atmosphere of each company are different and are directly related to the head of the R&D department. In short, responsibility...

1) It is related to corporate culture, which may be related to training and regulations. . . 1) It is not done well. 2) The leader also has a relationship. The review is not strict or there is no time for review. Of course, it may also be related to the first point. A friend once complained to me that there are regulations in the design, but no one implements them. As the head of a technical department, he is also helpless (why he did not make drastic reforms, this will be discussed another day). 3) What I want to say is still about individuals. People have subjective initiative. In the field of technology, you can't be careless. Since you have entered the technical life, you must strictly demand yourself and constantly improve yourself. There are many channels for learning, such as books, forums, such as New Year exchanges, and watching other people's disassembly. . . And many people, perhaps to meet deadlines, may be out of habit, when making things, they only think about completing the task, and never consider other things, such as PCB routing, they feel that as long as it is connected and the function is normal, they never consider other interferences. For example, when designing a software interface, the artist may design it from the perspective of art, but the program will be ugly when implemented, but some people never use their brains to help the artist from the perspective of program design. . . 4) Of course, my statement may be more idealistic. In reality, people may consider their own interests more. If it does not concern them, they will not care about it. Otherwise, if something goes wrong, they will have to bear the consequences. To put it bluntly, this involves the first point

懒猫爱飞

btty038 Published on 2019-2-28 08:42 I have tried the experience at the beginning of the article three times, and I went swimming secretly every time. It is really not easy to live to this day after three times. When I was a child, I was a bit suicidal...

I was taking tutoring classes at school during the summer vacation. The school dormitory did not have a fan (our place was relatively poor), and it was more than a mile away from the school, so I often climbed over the wall to go swimming secretly after the evening self-study. Thinking about it now, I am still scared

tiankai001

In terms of personal cultivation, engineers should do this. In my personal experience, after a project is completed, I always feel that it is imperfect or even inappropriate and wrong. I want to improve it, but the leader will come out to arrange new tasks and directly say that the product is like that and don't move it anymore. It's very helpless. When I did a project before, I started with the plan, and tried to consider the functions and processes in detail in the plan, and then wrote the program. But the leader would say, why is there no progress, is the plan so difficult?

tiankai001

Lazy Cat Loves Flying published on 2019-2-28 08:52 1) It is related to corporate culture, which may be related to training and regulations. . . . Not being done properly 2) It is also related to the leadership, who may not conduct strict audits or have no time to audit. When...

Many corporate cultures are like this now, but the more this is the case, the more individuals should pay attention to developing good habits.

okhxyyo

So we must develop good habits from the beginning. We must also read more and think more to make corrections.

懒猫爱飞

tiankai001 Posted on 2019-2-28 09:13 In terms of personal quality development, engineers should do this. In my personal experience, after a project is completed, I always feel that it is imperfect or even inappropriate...

1) The first step in doing things is to realize the function, and the second step is to optimize 2) Leaders and salesmen only want to release products early and realize them early 3) But as an engineer, you still have to strictly demand yourself. On the one hand, learn more and improve your ability to respond quickly. On the other hand, think more.

懒猫爱飞

okhxyyo posted on 2019-2-28 09:47 So you have to develop good habits from the beginning. You also have to read more and think more to make corrections.

Real-time learning, real-time summary, at least this time you do better than last time

PowerAnts

2. 3. If the current is relatively large, the power pad cannot be a hot pad. Performance cannot be sacrificed for the convenience of hand soldering in the prototype stage.

零一春风数声

DELAN1234567

It is right to do perfection under limited conditions

懒猫爱飞

PowerAnts posted on 2019-2-28 12:37 2. 3. If the current is relatively large, the power pad really cannot be a hot pad, and performance cannot be sacrificed for the convenience of hand soldering in the prototype stage

1) I also mentioned in the article that I personally prefer software, and hardware is indeed a bit of a layman's play 2) In addition, that project is a small BLE project, the maximum power consumption does not exceed 100mA, the current is not that large, so my husband made that suggestion

zhuyebb

Communication among R&D teams is very important

英尚微电子

Communication is important, habits are important, and we should try our best to improve the attributes of the product.

maoshen

When making a product, you need to consider the overall situation, otherwise there will be a lot of trouble later.

maoshen

When making a product, you need to consider the overall situation, otherwise there will be a lot of trouble later.

懒猫爱飞

yangyueni posted on 2019-3-19 16:47 Engineers can also be considered as management

Different companies may have different attributes. Our company's R&D is only the lowest level of R&D, which is far from the leadership.