But here comes the problem. For about four months, I couldn’t understand what the engineers were saying at all. I couldn’t even write down meeting minutes. I was often asked to hesitate in meetings with guests, and was ridiculed by the guests for my lack of professionalism. not enough. How to do it Start from the most basic, start reading embedded software books, attend RD technical discussion meetings,
write down all the words or concepts you don’t understand, ask the engineers one by one, and finally write out your own project development process, and use Belarus Phone Number List it later Practice and revise each project. It sounds simple, but it takes three years. There are no tricks, just practice it advertise Screen problems and use quick moves to defeat slow moves After nearly three years of training, I have also encountered the biggest bottleneck: how to continue to grow I often jokingly said: "If I can already see where I will be sitting and doing in three or five years,
what motivation will there be for growth" At that time, it seemed that there were two ways to strengthen professionalism in this field. Skills strong enough to help RDs read codes or switching to other roles business seems good, these two choices always conflict in my heart when I dream back at midnight Thanks to my wife for tolerating me talking nonsense all the time^ ^ . By chance, my good friend introduced me to a new Internet of Things company, which aroused my yearning and curiosity for new companies when I was a student. However, it was actually quite difficult to make a choice because of the facts that I would face when joining a new company. Yes: sudden reduction in salary and benefits, and uncertainty about the future. Judging from the PM's professional assessment, the risks are really scary.