I was an iOS programmer who wrote code for four years before I made a move to God. During that time, the product remained the same, but there were six product managers. In March 2018, I officially joined Shence. A year and a half into the job, the secretary came to me and asked me if I wanted to transfer to product manager. Although I was very interested in the position of product manager, I never had a chance to try it. As for the transfer opportunity offered by the company, I made the choice without hesitation and came to the “opposite” of programmer — product manager, so that I could get closer to what I wanted to do. If for my transfer trip you are interested, you can refer to previously published an article on the: shence army | breaking the technical thinking: the threshold of the product manager in the door.
In fact, the whole process of post transfer is not smooth sailing. In the words of the secretary, it is “crazy testing on the edge of post transfer failure”. Shortly after the transfer, some customers put forward new requirements for remote control projects, mainly including two points: no collection of specified events; There is an operation interface, you can batch and individually selected events. Doesn’t it look simple? I felt the same way at the time and immediately started writing requirements documents, prototyping, and conducting requirements reviews.
However, in view of this requirement, the secretary put forward two requirements for me: First, configuration differentiation project: the configuration of different projects is separated and does not affect each other; Second, configure differentiated apps: Different apps can configure different controls. Although the customer did not mention the above two points, it does make sense to think about it. I summarized as follows: we should base on the usage scenarios of customers and dig deep into their needs, instead of just being satisfied with the status quo. Although there are setbacks and blows on the way of post transfer, it is more about reflection and growth. Last summer, I had my “deskmate”. Together, we discovered and discussed needs, and worked together towards the direction of “bringing value to customers”. Here, I would like to express my heartfelt thanks to my mentor, who has led me to grow up. (@rabbit)
I remember my secretary once told me during the interview, “You may encounter problems you have never met before, but you can’t bypass them. The only thing you can do is to face them head on.” At that time, after listening to this sentence, I did not have the psychology of fear, but on the contrary to the divine policy of interest: what kind of problems will be encountered? In the future work, I gradually understand the answer to this question.
When I first joined the iOS group, MY task was to solve the remaining bugs on JIRA. Looking through the bug log, it seems that every problem is hard to solve. I wondered why none of these bugs were even slightly simpler. Then I realized that the simple bugs had been solved long ago, and the rest were the hard ones. I went head-on and tried every trick IN the book to solve these problems: simulation of unusual scenarios, theoretical analysis, Internet research, consulting colleagues. It was a tortuous process, but the results were good, and many of the problems on JIRA were solved.
I thought that was all, but the problem turned out to be much more difficult. About three months after joining the company, the team leader arranged me to communicate with the technical consultant and solve the problems feedback from customers. Since then, I have been on the “road of no return” to solve the problem. Some customers give feedback that our database will occasionally crash when inserting data. Although the number is not much, we must solve it by adhering to the principle of “doing things to the utmost”. When I got this problem, I thought it should not be the problem of database insertion, because it is a necessary path, if there is a problem, it would have exploded. In view of this situation, the next thing to do is to investigate the cause of the crash.
When confirming with the customer whether the problem recurs, the customer replied, “This is a crash collected online and cannot recur locally.” When we were in the dark, we started with the vetting process, where we found a key piece of information: All of our customers’ crashes were on iOS 12 models. Armed with this clue, as well as iOS 12 search analysis, we identified the problem and took a big step toward a solution.
In the end, we gave our customers a solution for iOS 12. After online verification, there was no crash. By solving this problem, I learned the following lessons: Try to find patterns in the information you already have; The troubleshooting process can be documented, which helps clarify the thinking and carry out the follow-up work. At the same time, as much as possible to obtain comprehensive information, some key information after the problem is solved, more importantly, must be careful, although the performance of the problem is very similar, but the cause of the problem may be very different. This is just one of the scenarios to solve problems. In our daily work, we will encounter all kinds of problems. For Shenshenshenjun, every problem is a test. (@ Winston)
Through the company’s training, the most direct harvest is to master a lot of new knowledge and skills, which laid a solid foundation for my current duty work. In addition, I have developed some good habits, such as writing the rules of god have been engraved in my head, even to my boyfriend before and after the English space.
In order to successfully pass the training, I combed and consolidated the product knowledge again and again, just like the corporate culture of Shence says — do things to the extreme. No matter what the result is, we have to give it our all. That’s the right attitude. Since I started working, if I have any feeling about work, the first response in my mind is two words: growth. What is growth for me? Give up the factory comfortable work, came to god policy to start again is growth; From two rounds of lectures, however, to now independent duty is growing; From the non-class background, to now achieve the standards of god policy is growth; From the interview in SQL like is what do not know, to the tutor told me that you are zero based on the successful case of employing experiment is growth!
But in the process of growing up, I also clearly know that it is the platform of the company, the help of the team, and the support of everyone. My friends help me sort out the mind map and find ways to learn. My mentor and HR helped me with psychological counseling; When I have a problem and go to everyone for help with my computer, everyone gives me a positive response. These are experiences I’ve never had in my previous job, and I’m glad TO be part of such a great team! (@mango is not yellow)
Have you ever seen two months of orientation? The original intention of joining Shence is mainly because of a sentence, which is very familiar to shence soldiers: “To accomplish one thing, to achieve a group of people”. At that time, IN order to prepare for the interview, I collected a lot of content about the divine policy, and came across this sentence written by Wen Feng. I don’t know what mood Wen Feng was in when he wrote this, but I read two implications: first, pragmatism. Down-to-earth, adhere to things done, including “to bring value to customers” corporate culture is also reflected in this meaning; Second, responsibility. There is a family behind each of us, and it is not easy to be an entrepreneur who not only shoulders the responsibility to an employee, but also involves countless families. Therefore, I am willing to join Shence, and I am very grateful for its acceptance of me. I hope to work together with more Shence troops in the same direction.
In the past, the orientation at a job was usually one or two days, but at Strategy, the orientation lasted two months, including the product, SDK, company culture, etc. At first, I really couldn’t accept this training mode, but as I got deeper into it, I found that no matter the products, SDKS or solutions of Shenze, they all have their own development and evolution process, just like the growth of people. As customer usage scenarios become more and more complex, the types and functions of Shence products and SDK continue to increase, which provides a solid foundation and full preparation for Shence to serve customers.
Through the training, my most direct harvest is the change of thinking. Share two key words: initiative and mutual help. During the training phase I and several other friends formed a study group, I will take the initiative to organize group meeting, in front of the class and construe positively to ask each other, help each other, aiming at training knowledge leak fill a vacancy, fully aroused the enthusiasm of everyone, got everyone’s positive feedback, the behavior of helping each other is for us the small team can assign, All the team members did well in the series. Shence is a team with temperature. For the new students, we will take the initiative to give help in work and life; When I encountered difficulties, people would actively help me correct and give solutions…
In my opinion, cultural transmission should not only be vertical, but also horizontal. When I feel warmth from this team, THEN I will pass it on. Whether it’s meeting new people or taking charge of training, I’m willing to do whatever I can to help others and make our team warmer. In the New Year, I will spread warmth, help others and improve myself. (@Xiaozhou teacher)
In this article, through the personal narration of four shenqi soldiers, we present part of the scene of shence’s work. I hope that through their stories, you can have a further understanding of Shence. If you want to do something fun with such a fun group of people, come and join us!