In July, I was called in by the boss and asked if I was willing to work on a new project. Of course, the boss was not the only one who asked me. He also asked several colleagues with more experience than me in the team before. Considering the current development of the project is quite good, the monthly turnover is nearly 100 million yuan, and the user level is also one million. To a project that has just been approved and its future is uncertain, it must be quite difficult at the early stage, with overtime and pressure. After knowing the direction of the project, I decided to go to the new project after thinking about it for two days. Why do you want to work on a new project? Here are some of my thoughts to share with you.

Agree with the product

First, I decided to join a new project only after I knew the direction of the product. Why emphasize knowing the direction of the product, because development requires a sense of identity with the product. If you’re not the kind of person who outsources projects and calls it quits, ignore your sense of identity. Otherwise, you have to face the development of the project without a sense of identity, to do it well, personally feel very difficult. All sorts of unpleasant things can even happen when you’re talking to the product manager about requirements. In this way, you not only give yourself something to do, but also affect the progress of the team project. When the boss first talked to me, he didn’t give me a clear product direction. So I made it pretty clear that I couldn’t make a decision if I didn’t know the direction of the product. In the second conversation, I knew the direction of the product and the product manager in charge of the product. I recognized the direction to a certain extent and knew the product manager. Based on both of them, I began to have the idea of joining the new project.

Open field of vision

The so-called open vision is not limited to programming technology, but to understand the process of a project from 0 to 1 needs what conditions, rather than all inferior, only high technology ideas. The growth of a project is as much about product and operations as it is about technology, and if you are involved in the early stages of a project, there is more opportunity to see the project go from zero to one. In the early stage of the project, when the team was not very large, there were more opportunities to contact with students of product and operation, and learn some ideas and practices about product and operation. For example: what is the purpose of the overall design of the product? How to acquire our first group of users after the project is finished and launched? What is the purpose of designing such operations? As the project successfully incubates and the team grows, there are often fewer opportunities to reach out again. Of course, developers who weren’t interested in this aspect in the first place didn’t have much impact.

Further business

In the early stage of the project, building the framework structure, encountering various problems and obtaining solutions are all valuable business experience. It’s a much better experience than coming in mid-project and writing code on top of what you already have, and of course, it’s a lot harder.

Ability to exercise

A project starts from zero, and the early participants will be challenged and trained in various aspects. The first is the psychological ability to resist pressure. In the early stage of the project, people often work overtime to meet various needs. If they do not make enough psychological preparation, they will become physically and mentally exhausted and the coding efficiency will decline rapidly. Secondly, it is the ability to control and coordinate. Participants are not alone and need to coordinate various resources. The client needs to coordinate with the back end, and the development needs to coordinate with the product and test, so as to ensure that all resources can be put into operation to maximize the efficiency of the team. In addition, there are many abilities, to name a few, that the success or failure of the project can erase.

Project bonus

If the project can be scaled up, there will be some financial rewards for early participants, in addition to the benefits mentioned above. You know, promotions and raises, big stock options. However, I suggest that the early stage of the project should be relatively indifferent to the returns in the later stage. After all, the probability of the survival of the new project is just like that of a start-up company. In case the actual results are not as good as expected, the loss will be outweighed by the gain.

To be added

Write a little late, temporarily talk about here, above is my some superficial share, have more ideas of friends welcome to add in the comment area. (So late also push the article, it is estimated that no one…)

IOS rewards only

Welcome to the technology horizon